Unusable application

[nebulon]

If docker.apehost.de is the actual server, then I am able to contact that app from here at least. Does it correctly resolve on the system where it fails?

[klawitterb]

From the server:
ping -n docker.apehost.de -> works
telnet idontexist.apehost.de -> Name or service not known
telnet docker.apehost.de -> connection refused
docker pull docker.apehost.de/path-to-exisiting-image -> Error response from daemon: Get "https://docker.apehost.de/v2/": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

From my local machine:
docker pull docker.apehost.de/path-to-exisiting-image -> works just fine

[nebulon]

So then telnet docker.apehost.de 443 also times out I assume. Is hairpin correctly working for you? run cloudron-support --troubleshoot to see this

[klawitterb]

Indeed seems like hairpin doesn't work, from troubleshoot:
[FAIL] Could not load dashboard domain.
Hairpin NAT is not working. Please check if your router supports it

I just tried the good old have you tried turning it off and on again, interestingly troubleshoot now errors with:
[FAIL] Could not load dashboard website with loopback check

[klawitterb]

So decided to upgrade my server to Ubuntu 24 and its working now again.

[nebulon]

Strange how that would have affected it, but well glad it works

[Lanhild]

@nebulon I did the upgrade from Ubuntu 22 to 24 today. I confirm that it fixed the issue for me as well.

[Lanhild]

@nebulon

I have another Cloudron server for which I did the upgrade too. Though, it didn't fix it for this one.

No outstanding errors in cloudron-support's output.

I'm pretty much at a dead-end here

[robi]

@Lanhild after the server upgrade, did the app upgrade yet?

[Lanhild]

@robi Yes

Cloudron Container Registry 2.6.0 (registry 3.1.0)

[james]

Hello @lanhild
Can you send me a direct message with some credentials (username + app password for the docker registry) and the URL for your docker registry app?
I would like to attempt a push from my side to validate if it is not some obscure local issue.

[Lanhild]

@james Done.

[james]

@lanhild and I did a debugging session.
Somehow this issue is connected to https://forum.cloudron.io/topic/15408/openid-configuration-url-timeout