@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...

@shrey we have a global lock in Cloudron which blocks app actions when backup is running. This was reported earlier already and it's in our task list to fix.

Note that when you hit this, just go to Backups view and stop the backup. That will allow you to continue your work. I agree this is not nice.

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 ?

@THI_Staff it's not too uncommon an oversight. I made an internal note for dev. Maybe we can notify Cloudron admins if the Domain API keys are not working anymore. We do this check when adding the domain, but maybe we can do this check periodically. This will also catch API key change etc.

Works! Thanks a lot! 🙂

@girish Thanks for the complete and thorough explanation. I guess I was fooled by the apt update I saw in one of your docker image definitions (thinking that others would be following your best practice). If you are comfortable with the risk/reward balance then I am comfortable:)

@luckow good catch. In fact, the sort function usage was entirely wrong.

Fixed in https://git.cloudron.io/cloudron/cloudron-cli/-/commit/87dcb5f8cc8ae29f877a6f5b96c865ec48dd8846

I published a new CLI 5.5.0

@girish Thanks, that was it.

Interesting. So, from @necrevistonnezr's like the hosts.allow/hosts.deny may not work in the future. "Note: this might not be an option on modern distributions, as support for tcpwrappers was removed from OpenSSH 6.7"

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