Logging into Cloudron with OpenID Fails After Update to 7.7.0

[nebulon]

If you open a webterminal into any app, can you curl -v https://my.yourdomain.com/.well-known/openid-configuration if not, does the DNS resolve correctly? If yes, I guess it is also a hairpinning issue then.

[pathab]

Yes, the IP is resolved correctly. But without response. Could it be that this nginx route is no longer working properly?

[girish]

@pathab does curl -4 -v https://my.yourdomain.com/.well-known/openid-configuration work? This forces IPv4. Maybe some caching issue somewhere is causing a IPv6 query.

[pathab]

Unfortunately, it's the same story.

[girish]

@pathab what is the output? also, does the curl not work only on the server or from anywhere?

[pathab]

the output is the same everywhere

*   Trying xxx.xxx.xxx.xxx:443...
* connect to xxx.xxx.xxx.xxx port 443 failed: Connection timed out
* Failed to connect to my.domain.com port 443 after 131026 ms: Connection timed out
* Closing connection 0
curl: (28) Failed to connect to my.domain.com port 443 after 131026 ms: Connection timed out

[girish]

@pathab are you hosting at home? If so, https://docs.cloudron.io/troubleshooting/#hairpin-nat is the most likely issue. Your network has no mechanism to reach itself via public IP.

But, before we go into this, another test. Can you try to curl that URL from another network altogether ? Say via your mobile phone network or equivalent? Does that work ?

[pathab]

It seems like you're right and the new modem is the problem, sorry I forgot to mention that - didn't expect that to be the cause. (Because cloudron has been running very smoothly for over a year now).
Well, I have now moved the server to a VPS. Everything seems to be working there now. I will try to get my cloudron home server up and running again at a later date. Thank you very much for your time and support!

[pathab]

btw. I just love how easy it is to transfer cloudron to a new server!

[girish]

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