Thank you @james I could not get it to work. After several attempts, I ultimately deleted the backup files and started with a new configuration. As advised, I also set the retention period to "unlimited" (it was previously set to two days). Everything is working well now, and I was able to back up and clone the app without any issues. Thanks again, and keep up the good work!

Hello @sebastienserre App Archives are not the same as backups. App Archives is when you go to an app, to the uninstallation section and archive the app. This uninstalls the app but keeps the latest backup as an archive so it can be restored. This archive is stored and kept outside the backup retention policy. See https://docs.cloudron.io/apps#archive [image: 3ca46733-ecad-4ae3-8980-65d96397645c-image.png] [image: f592674b-3485-4155-b11d-048fd845ac60-image.png] Your system backups are viewable under Backups> Sites.

@oskarardolo 9.0.16 will be out possibly end of this week or early next week.

@tecbox I sent a reply from support. I debugged this further . The 502 is returned from deSEC . I have added some logs on your server to see if we can get the full error to report to deSEC. So far, it's been running for the last one hour without reporting any error from deSEC .

Hello @canadaduane Thanks for the report, this will be fixed with the next Cloudron update. https://git.cloudron.io/platform/box/-/merge_requests/26

Closed in favor of https://forum.cloudron.io/topic/14871/failed-to-open-stream-permission-denied

Fixed in support. Not clear what the issue is, but it could be possibly because spamcop dnsbl was not responding. I removed it from the mail acl - https://docs.cloudron.io/email/#dnsbl.

Link to feature request . Thanks @crazybrad

Good catch. nc is not part of the base image it seems (not explicitly). I have replaced that code with bash logic.

thank you for all your explanations

@nebulon could you please also approve me? I'd like to cast a vote for GlitchTip

@paradoxbound if I enable Dane, should I enable MTA-STS?

I've tripled checked (created new key and secret) and it works...

@james said in Cloudron App Install Update Error Bug: Hello @dualoswinwiz Please use registry.docker.com as the docker hub server address. This should resolve the issue. i was using like this registry.hub.docker.com --- changing this to registry.docker.com solved the problem

Can you run cloudron-support --unbound-forward-dns 1.1.1.1 ? This will forward all DNS requests to cloudflare public DNS.

Fixed in https://git.cloudron.io/platform/box/-/commit/b537d73a5585662605176346ffb31db4ebbb6a02

The AWS module changed between v8 and v9 and maybe some discrepancy between the versions is causing this. I will close this because testing and accommodating minio issues is a dead end unfortunately given that the project has gone into maintenance mode. We are looking into Gargage as an alternative.

Maybe you can open a new thread with the log? The previous issue is probably not relevant since it was many versions ago. Did you also restore Cloudron to a new server and hit this issue?

Hello @potemkin_ai You could also check the Cloudron event log to see if and when the password was changed. Have you checked that?

@james said in Private docker registry in Cloudron: Hello @dualoswinwiz I have just created a personal access token with the Read-only permission. Configured Cloudron: [image: 8248133a-0064-4fa0-a724-828faf826879-image.png] and was able to install my custom app from a private repo. Did you use registry.hub.docker.com as the Server address? Nope i was using docker.io once i changed to registry.hub.docker.com its working thank you.