Cloudron Forum

I've talked with the support, and we could solve the problem.
However, I would like to provide a brief summary for all who are facing the same issue.
The issue was that cloudron attempted to connect with Let's Encrypt via IPv6, which, of course, didn't work out. Therefore, it couldn't get a new certificate.

You can see this if you run the command:

host acme-v02.api.letsencrypt.org

directly in your server shell.

Then it should print something like:

acme-v02.api.letsencrypt.org is an alias for prod.api.letsencrypt.org.
prod.api.letsencrypt.org is an alias for ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com.
ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com has address 172.65.32.248
ca80a1adb12a4fbdac5ffcbc944e9a61.pacloudflare.com has IPv6 address 2606:4700:60:0:f53d:5624:85c7:3a2c

This was the case, so I knew, that I have to disable IPv6. To do so, run:

sysctl -w net.ipv6.conf.all.disable_ipv6=1

This should disable IPv6 and solve the problem.

I would like to thank Jonas from the support team, who helped me resolve the issues and also wrote all of these commands.

I found an outdated AAAA record and deleted it. But still, after 12 hours (which should be enough for the DNS to update), it prints the same error.

I disabled the IPv6 address because Gmail said the reverse DNS wasn't configured properly. To solve this issue, I deactivated it. But this was months ago, and I'm certain that I got a new certificate in the meantime, without the IPv6 port. So why does this error happen now?

I can't get a new Let's Encrypt certificate.

It gives me the following error:

cron	Certificate install for XXXXX.XX failed
{
  "domain": "XXXXX.XX",
  "errorMessage": "connect EHOSTUNREACH 2606:4700:60:0:f53d:5624:85c7:3a2c:443"
}

Hi, I noticed that I can log in to an email program with a simple password, even though I have two-factor authentication enabled everywhere (i.e. in Cloudron itself and in SnappyMail).
Is this a bug that you can log in just like that? After all, there are also app passwords....

Hi.
I've got a question.
I can activate the "catch-all" in the mail settings, so that all emails are forwarded to a mailbox.
Then I can enter a random address on any page, because everything is forwarded (e.g. cloudronforum@cloudron.com).
If an address is now leaked (cloudronforum@cloudron.com), can I prevent all emails sent to this address from being forwarded? The other mails should of course still be forwarded...
Is there such a black list?