Cloudron Forum

Sad to read this, what must the mInIO guys be thinking (oh yeah, doh, money)
Uninstalled Minio and will wait for a suitable open alternative

Update : I noticed that Parse had new versions, so am trying to package those.
However Parse has made some security changes which mean the initial approach of mirroring Parse Server and Parse Dashboard as separate apps doesn’t work.
So I am back to building a “mono-app” with latest versions of Parse Server and Parse Dashboard in one container, which has some advantages.

Focus on using MongoDB but perhaps could do Parse-Mongo and Parse-Postgres as an option after getting the new versions app working. Naively perhaps, but I’m assuming that Cloudron could make alternative db backend easy.

@girish that’s what I thought initially, but I checked both of those and was able to carry on working other prjects while waiting.
I don’t understand it, and can only put it down to a docker weirdness.
After a while I noticed that local docker desktop was asking to update, and after that I cleared the docker environment.
Then all is back to normal (whatever that is).
Phew

@ahummel if you deploy the tailscale client to your Cloudron server, are you also selfhosting your Tailscale control server ?

Weird
Got bored and grasping at straws so did docker system prune -a --volumes -f
Now it’s building again and apt-get succeeds.

Sometimes I doubt my connection with reality

@girish said in Cloudron 8.3 + Base image 5.0.0:

I will update this post with the finalized base image 5.0.0 sha256 when it's tested across a large variety of apps.

Updated base image yet or that one still applicable ?

Asking because I was using it in docker builds fine, but suddenly apt stopped being accessible :

=> ERROR [ 3/14] RUN apt-get update && apt-get install -y --no-install-recommends gosu     && rm -rf /var/lib/apt/lists/*       1.1s
------                                                                                                                                
 > [ 3/14] RUN apt-get update && apt-get install -y --no-install-recommends gosu     && rm -rf /var/lib/apt/lists/*:                  
0.397 Get:1 http://security.ubuntu.com/ubuntu noble-security InRelease [126 kB]                                                       
0.464 Get:2 http://archive.ubuntu.com/ubuntu noble InRelease [256 kB]                                                                 
0.582 Get:3 https://packages.redis.io/deb noble InRelease [3854 B]                                                                    
0.642 Err:3 https://packages.redis.io/deb noble InRelease                                                                             
0.642   At least one invalid signature was encountered.
0.715 Err:1 http://security.ubuntu.com/ubuntu noble-security InRelease
0.715   At least one invalid signature was encountered.
0.887 Err:2 http://archive.ubuntu.com/ubuntu noble InRelease
0.887   At least one invalid signature was encountered.
0.910 Get:4 http://archive.ubuntu.com/ubuntu noble-updates InRelease [126 kB]
0.984 Err:4 http://archive.ubuntu.com/ubuntu noble-updates InRelease
0.984   At least one invalid signature was encountered.
1.020 Get:5 http://archive.ubuntu.com/ubuntu noble-backports InRelease [126 kB]
1.091 Err:5 http://archive.ubuntu.com/ubuntu noble-backports InRelease
1.091   At least one invalid signature was encountered.
1.097 Reading package lists...
1.111 W: GPG error: https://packages.redis.io/deb noble InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'https://packages.redis.io/deb noble InRelease' is not signed.
1.111 W: GPG error: http://security.ubuntu.com/ubuntu noble-security InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'http://security.ubuntu.com/ubuntu noble-security InRelease' is not signed.
1.111 W: GPG error: http://archive.ubuntu.com/ubuntu noble InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'http://archive.ubuntu.com/ubuntu noble InRelease' is not signed.
1.111 W: GPG error: http://archive.ubuntu.com/ubuntu noble-updates InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'http://archive.ubuntu.com/ubuntu noble-updates InRelease' is not signed.
1.111 W: GPG error: http://archive.ubuntu.com/ubuntu noble-backports InRelease: At least one invalid signature was encountered.
1.111 E: The repository 'http://archive.ubuntu.com/ubuntu noble-backports InRelease' is not signed.

Been a problem for couple of hours

Grrrr, I got the same issue now - Cloudron says in blacklist, Spamhaus says not.
Trying to get my head around this long thread.

EDIT : errr, so TL;DR is nothing we can do and Cloudron will fix it “sometime” ?
Maybe I read too fast, but that’s my takeaway at the moment ...

Either going blind or maybe a cached page because I didn’t see that.
Or just rushing too much
Thank you

I checked https://docs.cloudron.io/packaging/manifest/

But I didn't see documentation for adding Admin Notes or Checklist in CloudronManifest.json.

I can hunt for examples but it would be good to have in this page - seems the natural place for it.

I would cut my losses and restore from a backup, especially if time to fix is constrained.

@SansGuidon hi
"using Umami" is an interesting point.
I have umami installed but hardly ever use it (so rarely that I have even forgotten what sites I have configured there).
As far as I recall, it worked fine.
My needs are quite simplistic, and I have lost interest in monitoring traffic to sites.
I should probably take more interest when I have time and motivation !

Anyone had success adding the HACS integration ?
Comment in their docs that access to filesystem is needed, and I baulked at that, assuming that it meant access to read-only areas.
But maybe I am wrong.
Before I invest more effort in it, just checking if anyone has done it.

Wanting to add Frigate but it seems it needs HACS first.

@rmpg generally if you create an account on git.cloudron and let @ staff (without space) know, they will permission you to upload your files, which they can review.
Probably fastest way even though involving a manual step from their side.

Purely for my education, the Cloudron AppStore version is 3.4.2, whereas the GitHub issue says 3.6.0 is working, so is it worth packaging 3.6.0 or there is a problem with that also ?

Not installed Typebot yet but interested to try it, thinking I might wait until later/latest version is packaged.

Cool - the online world needs something like this for sure.

@robi good question, but I don’t recall, I have used rclone for access to different systems, I just didn’t recall how the cloudron was done when setting up a new machine, and didn’t pay attention to what an old connection was telling. User error, pure & simple.

I ‘m trying to use Logseq more as an accessible brain dump, discipline of taking time to log instead of rushing forwards is difficult for me (old dog, new trick).

Thank you !
I did read that but I missed a critical part of it - it’s app-specific !!

Not how my rclone was set up before, so it’s a mystery how I did it before.
But I have got access to the specific app I need for now, so that’s

I know some people here use rclone with their cloudron.
I had a working rclone connection to my cloudron instance.
For some reason. "had" is the key word, and it doesn't work now.
Grey hair means I can't figure it out again.

Here is my config for the connection (done through CLI rclone config) :
[cloudron]
type = sftp
host = my.domain.tld
pass = *** ENCRYPTED ***
md5sum_command = md5sum
sha1sum_command = sha1sum
port = 222
user = ???

Should username be :

• <cloudron username> ?
• <cloudron_username>@my.domain.tld ?
• <cloudron user registered email address ?

I am not clear what rclone is doing in the background to make the connection.

rclone lsd cloudron: as test of connection fails with :
2025/04/25 17:41:52 Failed to create file system for "cloudron:": NewFs: couldn't connect SSH: dial tcp 1.2.3.4:222: connect: operation timed out

Does 2FA screw it up ?
I can use a non-2FA admin user if I know the basic connection config.

I'm assuming that because the connection is SFTP, there's no SSH keys needed. (but hey, assumptions !).

Need to check this out, but def cool addition if it can do what’s promised, so much tedium avoided !

@nichu42 don't worry about thinking out loud here, it's a supportive forum and a good way to get good feedback from those who have 'been there, done that'.

But in this case I personally don't use or know about WSL. Others here will.