Yeah. I know what you mean. Ok I will start afresh With this information now it will be ok to configure from scratch. Many thanks Jan

Thanks, that solves it!

@dsp76 good point. I have fixed the healthcheck now to not error for non 5xx errors.

In the past I have only seen the angular templates, if the browser has javascript disabled or the javascript files are not loaded. Do you see failing requests in your browser console?

@luckow yes. See this comment - https://forum.cloudron.io/post/83868 https://git.cloudron.io/cloudron/box/-/commit/0dfadc59228978f82ae3aa2ba4be2b421e785e02 was the fix . You can always apply it locally in /home/yellowtent/box/src/dns/digitalocean.js . Then, systemctl restart box and renew all certs.

@girish Perfect, that solved it. Thanks!

Not sure if this got solved but if it didn't please write to support@cloudron.io .

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

Yes, that works, thank you!

@Lanhild I sent a reply to them again. They've finally opened the port.

@girish Cloudron shows IP as present on Sorbs dnsbl blocklist, even though it isn't. [image: 1708555984912-2024-02-21_17-52-31.png] [image: 1708556022108-2024-02-21_17-53-31.png] Turns out I was too impatient, checks all green now.

Having to go through a restore, this was baffling with no hints for me too. I'll make a Feature Request to make this more obvious in the restore dialogue.

I got to the bottom of this. The issue is that mountpoint -q doesn't exit if NFS hangs and because we call execSync in node, the whole dashboard hangs. I have fixed this in https://git.cloudron.io/cloudron/box/-/commit/3da3ccedcbd8962ab309c591f6ae3561e5df4f28 The mount propagation flags like rslave don't apply to us. They only apply for recursive/shared mounts. That's my reading of it anyway. It doesn't seem to matter in my tests.

@humptydumpty I think it was a bug or something as I uninstalled the app and tried to reinstall it and it failed. For reference I have the Vaultwarden and Gitea installed. The 3rd app was Firefly.

Thanks for this.

This is exactly what is happening to me, as well! ![image: 1708451807334-cloudron-login-error.jpg]

To follow up, 11GB worked fine too. [image: 1708449838055-61cb612d-e125-405b-94f1-1b7d6598a349-image-resized.png]

Looks like the DNS resolution is failing. Can you explain your environment and check if you can resolve any host from the system via SSH? Is the unbound service working?

It was indeed a mishap in my provider's area of responsibility. Thanks again for pointing me in the right direction.