@girish Thank you, Girish! After I updated the node, this error went away.

@susankhanal said in cloudron not accessible using domain name outside the network: doing curl my.domain.com gives HTML lines from inside the network but doing curl outside the network it says unable to connect Before debugging further, I would double check the HTML output. Can you check if that looks like Cloudron dashboard code? Also, is my.domain.com resolving to an internal IP or an external IP? If it is resolving to an external IP, then most likely port forwarding is not working properly in the router.

Ah great you managed to get this going!

Glad it worked out in the end, and thanks for sharing the insights here!

Seems to fine here atleast. And we are not seeing any outages at https://status.cloudron.io/ either . Please re-open this if this is still a problem.

Hi, I just wanted to follow up on this. We found the relating issue in this case which resulted in several different problems. In that case, it was bug in a firmware update on a firewall and not related to Cloudron and can be marked as resolved. Thank you anyway for your help.

@pathab ah nice, great you found the root cause!

@jdaviescoates Good catch! This is a UI bug that it doesn't show deleted apps. The backups are there but the UI is unable to find an app to create a link to and decides to remove it entirely. Fixed in https://git.cloudron.io/cloudron/box/-/commit/49941a34b935c28570514c59598bbf58b93d41a1 . With this, clicking on deleted app will just put you in the eventlog (hopefully that gives some information what that app was).

@girish Thanks for the quick reply, . In case anyone else needs this on 22.04, I followed these steps and was able to get the system to boot with full disk encrypted drive with the private key coming from the tpm and no password needing to be typed. I don't think this uses the same libraries as the new option in 23.10 so I expect that when 24.04 comes out I will do a fresh OS install to use the better supported FDE TPM integration from that version going forward but as a stop gap I am happy with this for now.

@scooke right Also, 'wildcard' provider is just a convenient approach over the 'manual' provider. When you use, 'manual' provider, Cloudron will remind you set up these DNS entries manually (each time you add app or relocate app). With a wildcard, you don't get this reminder since a wildcard was set up.

Hi @girish that has fixed it thank you for your support Regards Chloe Edmondson They/Them (why pronouns matter)

@contactlight11 this is fixed now. 7.7.1 coming.

@jdaviescoates ah ok, this might be some issue on the VPS side. On a side note our dedi in Hetzner has many networking issues. Not sure what is going on...

Thanks, it went away after ~10 mins...

@girish Thanks! I hadn't thought of checking the certificate in the browser - yes, all is good.

@girish Thanks I wasn't aware of netplan. A quick read of your links and editing the yaml file has sorted the problem for me. As for the other comment I'm aware its a ubuntu problem, but as I only use Ubuntu for my cloudron server, I wasn't aware of netplan, or if changes to ethernet adapters would damage the configuration of all those veth for the cloudron apps. So I wanted to proceed cautiously in case something I was doing would break cloudron. It would be pretty weird to require a platform, and refuse any assistance on the platform when issues arise. Especially so when (as per your link about systemd networking) there is so much useless information regarding generic linux help.

Hi @girish, thank you for the quick answer and explanation. We can deal with it. Have a nice weekend.

@henry000 the problem is already fixed in 7.6. Are you on Cloudron 7.6 ?