Cloudron Forum

never mind, I fixed the issue with the IP. I went into GoDaddy and noticed the IP was different, so I changed it back, restarted unbound service and now my dashboard is loading with my domain. Now to restoring all of the apps with my backups.

Hi @girish,

I did that step and did a server reboot as the systemctl restart unbound did not work and when it came back up, all was good again! Thank you!

This is especially strange since you mentioned that other apps do work, so if you run that curl command from within a webterminal into that other app, it succeeds?

Just in case if this is a hairpin issue maybe, checkout https://docs.cloudron.io/troubleshooting/#hairpin-nat

The issue was that docker got stuck in removing the Cloudron network during the starting after the update. Not clear why and when this happens but stopping docker then running docker network rm -f cloudron manually (which will start docker due to socket activation) makes it work...

Considering Turnkey Linux has a container version of LAMP with MariaDB that works great for our software, it is too much to manually setup SSL and other things, this is why we want to use the LAMP in Cloudron to setup our software, but MariaDB is needed.

@girish I don't think it requires seal encryption.

I believe using seal encryption causes a different code path to be taken that avoids the underlying bug but it is not the presence or absence of seal encryption in and of itself that I believe fixes the issue.

After a kernel upgrade this works fine without seal encryption though I have now enabled it as it seems like a good idea to have anyway so making it the default is probably a good idea but as long as Ubuntu 22.04's default kernel version is 5.15.0-102 this issue will likely still occur.

I had this for a while, with an instance of PeerTube, I think. But then the problem went away.

Edit: nope, it was The Lounge, and possibly it went away because of this.

@skeats said in Typebot with Cloudron login does not work:

curl: (28) Failed to connect to my.example.com port 80 after 130794 ms: Connection timed out

right, so this is the core of the issue. You need to investigate why the server is not able to curl itself. I assume you can curl from another device/laptop in the same network, correct ?

@skeats do you need help patching it?

You are welcome @alphy. Enjoy Cloudron!

@skeats I think https://docs.requarks.io/groups#private-wiki is what you want.