Cloudron Forum

same issue here. Moving to 8gb worked. subsequently resizing back to 2gb or 4gb does not work.

8gb is pretty big!

After being dissatisfied with existing time tracking solutions, we built our own. It is now available for others to try, and we'd love to get your feedback. We have been using it in production for ~6 months. Features include:

• Unlimited users, projects, clients
• Nostr only (everyone needs a nostr signer to access). We have designs to enable cloudron email (with hosted nostr account), plus many more features, if anyone would like to collaborate or invest in it.
• Optional desktop app for activity / screenshot capture

The first user to log in becomes the admin. You can set roles by project (eg owner, manager etc) to allow scoped visibility into hours tracked, and you can configure usage alerts by project or customer using a matrix API key.

https://git.nostrdev.com/trakstr/cloudron-trakstr/raw/branch/master/CloudronVersions.json

We've bumped strfry to the latest version (1.1.0) and made it a community app

You can try it out here: https://git.nostrdev.com/stuff/cloudron-strfry/src/branch/main/CloudronVersions.json

Didn't get this notification. The blossom cloudron is an old version of blossom now. Will look at auth when we bump it up.

This app is great! So fast!

Hi Joseph - yes you can - we use these apps ourselves and plan to maintain them (until such time as someone else ever does)

I notice that BTC Pay link points to btc-core - there are actually two apps (some features in BTC Pay depend on BTC Core):

• Bitcoin Core: https://git.nostrdev.com/stuff/cloudron-bitcoin-core/raw/branch/main/CloudronVersions.json
• BTC Pay Server: https://git.nostrdev.com/stuff/cloudron-btcpay/raw/branch/main/CloudronVersions.json

One instance of BTC Core can serve all instances of BTC Pay. You can also run BTC Pay without core, or using another instance of core.

Also updated to v2.3.6

aah looks like it was due to changelog not being updated properly. Working now!

Are there any tools to help validate a cloudronversions.json file? Put this together: https://git.nostrdev.com/stuff/cloudron-btcpay/raw/branch/main/CloudronVersions.json

But can't seem to figure out why it always says "Could not resolve CloudronVersions.json from URL"

ok - the versions.json is ready for btc core: https://git.nostrdev.com/stuff/cloudron-bitcoin-core/raw/branch/main/CloudronVersions.json

had to move it back to our own repo so that it could update the json as part of the pipeline (cloudron uses gitlab vs the runners being in gitea)

will do btcpay server next, in the coming days

@timconsidine - didn't realise this was ready, thanks for the docs pointer, it looks straightforward enough. Will get onto it asap! Which realistically will be this weekend or early next week.

Hi @timconsidine

BTC Core is v29 and it should not be updated. There were contentious changes added in v30, and to be pragmatic, it would be best to stick with v29 for the foreseeable future. This does not affect BTCPay Server.

About the community app release, can you give more details? What would need to happen?

BTC Pay Server should run independently of BTC Core (the core part is only needed when you set up the wallet within a shop). So if it is not responding, it is not due to Core.

using gosu does the trick, thank you

root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama pull qwen3.5:35b
pulling manifest 
pulling 900dde62fb7e: 100% ▕████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  23 GB                         
pulling 7339fa418c9a: 100% ▕████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  11 KB                         
pulling 9371364b27a5: 100% ▕████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏   65 B                         
pulling 606ad9f1ecbc: 100% ▕████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████▏  482 B                         
verifying sha256 digest 
writing manifest 
success 
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama ps
NAME    ID    SIZE    PROCESSOR    CONTEXT    UNTIL 
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama ls
NAME                       ID              SIZE     MODIFIED       
qwen3.5:35b                3460ffeede54    23 GB    50 seconds ago    
nemotron-3-super:latest    95acc78b3ffd    86 GB    19 hours ago      
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama serve
Couldn't find '/root/.ollama/id_ed25519'. Generating new private key.
Error: could not create directory mkdir /root/.ollama: read-only file system
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# gosu cloudron:cloudron bash -c 'HOME=/app/data/ollama-home ollama serve'
Error: listen tcp 127.0.0.1:11434: bind: address already in use
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# gosu cloudron:cloudron bash -c 'HOME=/app/data/ollama-home ollama ps'
NAME           ID              SIZE     PROCESSOR    CONTEXT    UNTIL              
qwen3.5:35b    3460ffeede54    25 GB    100% CPU     4096       4 minutes from now    
root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# 

Getting the following in a fresh install after downloading the model:

Setting the HOME variable does not help.

root@4772c55c-cc53-4e23-b90e-d3d8b5687bab:/app/code# ollama run qwen3.5:35b
Error: mkdir /root/.ollama: read-only file system

We installed HPBE on a dedicated VPS and Nextcloud Talk is mostly ok for us now.

Simplex Chat is the best private messenger out there, that we have found. We'd love to run our own Simplex Server.

Another app we are keeping our eye on is White Noise, which uses the Marmot protocol.

@james

Using Bitwarden means keeping your secret on a potentially compromised device. Better to use a hardware key.

The problem with both Yubikey and Nitrokey is that if you lose the device, you lose the key. Big problem.

The fact you cannot recover a passkey, make those devices a pass, from us. Or at least, they must be used in a far more careful and limited fashion - ie, fallback to email recovery - than what would otherwise be the case (sovereign recovery).

With Trezor - and other hardware wallets that use deterministic webAuthN - you can recover from a seed. This means that the loss of a device is not catastrophic.

EDIT: Am reading the Trezor forums and apparently they do support Passkeys, it's just that the Resident Key is encrypted with the seed, and not deterministically generated. So for recovery, you just back up the file using regular cloud storage.

Looking forward to testing it on cloudron, and letting you all know the results.

https://trezor.io/guides/bonus-tools/what-is-fido2

so long as we can use an external signing device (like Trezor), and not trust some foreign spyware company like Google or Microsoft or Apple, that would be great.

@nebulon what about FIDO2 or WebAuthN?

BTCPayServer has now been updated to v2.3.3 (from 2.1.6)

Tested on our instance and it's running fine

https://git.cloudron.io/playground/btcpayserver/