@DualOSWinWiz yes, correct. This looks like some kernel related issue or some missing ubuntu package. Can you try to make the NFS mounting work with just the CLI . This will remove Cloudron out of the equation. I think it is possible some missing package or miscompiled kernel.
I found the final solution in an old post: https://forum.cloudron.io/topic/9053/app-stuck-in-restarting-after-upgrade-7-4-1/2
This seems to have fixed everything. Thank you for the help everyone!
# rm /home/yellowtent/platformdata/sftp/ssh/ssh_host_rsa_key
# rm /home/yellowtent/platformdata/sftp/ssh/ssh_host_rsa_key.pub
# systemctl restart box
@girish said in Dynamic DNS and Mail Server Location:
@gerard that's quite brave to run a mail server with dynamic IP
@girish Yeah it's silly and unreliable But not meant for any serious usage.
Thank you for fixing it.
@CRBear said in Mail server: IP address verification?:
Am I correct in understanding that the email server checks from which IP address a connection is established to send an email and by default, it verifies against the Spamhaus blacklist?
The mail server does not make any check for outbound email. The various checks you see in the Email Status tab are purely diagnostic. The idea is if one or more checks are failing there, most likely the email won't be delivered.
The Spamhaus is checked for inbound emails though. The DNSBL zone against which it checks is configurable at https://docs.cloudron.io/email/#dnsbl
Interesting.
I contacted the provider and told about the problem. They wanted screenshots. After another test all works fine again.
Thanks for your help!
Seems like there is something wrong with that installation medium maybe? Have you seen and tried https://askubuntu.com/questions/1500639/update-error-e-the-repository-cdrom-ubuntu-22-04-1-lts-jammy-jellyfish already?
If you mean the webterminal, then this is into the filesystem of the app, not the host system. Cloudron does not have a webterminal into the host system, as it is not advised to tinker with this. However in this case you should use scp (essentially file transfer via ssh) to put the tarball into the /tmp of the server.