We were able to resolve this. The root cause was the missing unbound-anchor ubuntu package. After intstalling this it worked. More info on that issue is at https://forum.cloudron.io/topic/12496/unbound-anchor-not-found-in-ubuntu-24-04?_=1727881329798

@daixiwen ah ok. I would ignore the errors. It's normal for upstream services to go down once in a while... I just checked https://status.backblaze.com/ and unfortunately no history of uptime here. But it says "Backblaze performs regular maintenance every Thursday from 11:30 am to 1:30 p.m. Pacific Time with the aim to consistently improve our systems and services. "

@nebulon said in All Offline adter update or db can't restart.: by avoiding disabling by avoiding disabling at least I think that's what you mean?

Hi @girish, I did that step and did a server reboot as the systemctl restart unbound did not work and when it came back up, all was good again! Thank you!

@girish said in Cert renewing failing: @visuex are you the same as @cpa ? Nope, not me!

Yeah, I guessed the same after reading the debianforum wiki Results after running it a couple of times: sudo hdparm -t /dev/sdb1 /dev/sdb1: Timing buffered disk reads: 192 MB in 3.00 seconds = 63.92 MB/sec Timing buffered disk reads: 200 MB in 3.00 seconds = 66.58 MB/sec Timing buffered disk reads: 224 MB in 3.01 seconds = 74.44 MB/sec Timing buffered disk reads: 236 MB in 3.01 seconds = 78.31 MB/sec Timing buffered disk reads: 248 MB in 3.01 seconds = 82.33 MB/sec Timing buffered disk reads: 234 MB in 3.01 seconds = 77.69 MB/sec

I think @nebulon means host -t NS vysvr.org . This should resolve to your nameservers.

I think we have to go back to the original question. What's the original issue? Using tools like df in /var/lib/docker/overlay2 won't work.

@joseph , Running 'cloudron-support --recreate-containers' fixed the issue. Thank you.

Great! Thank you! BTW, it seems in retrospect that the start of the DNS problems coincided with me beginning to use the OpenVPN app. Take that for whatever it's worth.

@andreasdueren said in Cloudron can't uninstall apps after access to domain got denied: Sep 26 10:49:40 box:dns unregisterLocation: Error unregistering location A. retryable: false. message: Invalid access token statusCode: 403 code:9109 The directory message is just a warning can be ignored. The above message is the real error. Are you sure you are not using any other domain in the app which in turn uses some DNS provider? Are all the DNS providers manual ?

Yes, you’re correct! If you’ve configured Mailgun as a relay on Cloudron, you should use port 587 with STARTTLS for secure email sending. If you're looking for alternatives, I recommend SMTPget and iDealSMTP. Both offer reliable services and can also be easily configured for your email needs.

Ok weird, this worked, I backed up apps and updated to Cloudron 8 but it's not working again. that file didn't change. I set it to google's public DNS and it was fine - I reinstalled tailscale and set override DNS to true which I think should fix it and let me keep using TS

@bennyv53 I recommend using ssh then (SSL support for internal postgres will break Cloudron's setup). Is the concern security related?

@b2breporter you can contact us on support@cloudron.io and we can fix it up

The apps itself run with minimal permissions but the Web Terminal gives you "root" access (this is a limited root and not server root) so that you can creates files as any user since some apps use multiple users. It's also required in situations where you restore/import the app and those files have different permissions than the one app uses. But tl;dr this is intended. Use su like @murgero said or you can use gosu <username> <cmd> as well

Good catch, we have to fixup the docs here. The OpenID provider session logout, triggered by the app used to be there, but we found that no app supports this properly so it got removed. For nextcloud, we have some changes to soon enable OIDC login by default in the package, so may not be worth it to investigate just now in your case.

@d43m0n1k_sek yes, let us know

Thanks guys - I did see that other thread but wasn't sure if it was the same thing. Appreciate the workaround and the fix, and all your hard work always!

Ah, thanks! I was already running 8.0.5, but the upgrade to 8.0.6 got stuck. /home/yellowtent/box/setup/start.sh came up with an unbound error. I was able to start box manually and start all apps, but the backup volume did not mount. After installing unbound-anchor, I was able to run /home/yellowtent/box/setup/start.sh without errors, and now the backup is working again.