Unusable application
-
Just tried, that just gives me a telnet: Unable to connect to remote host: Connection refused
-
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 -
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 itI 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 -
So decided to upgrade my server to Ubuntu 24 and its working now again.
-
N nebulon marked this topic as a question on
-
N nebulon has marked this topic as solved on
-
J joseph referenced this topic on
-
R rosano referenced this topic on
-
@nebulon I did the upgrade from Ubuntu 22 to 24 today. I confirm that it fixed the issue for me as well.
-
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
-
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. -
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. -
J james has marked this topic as unsolved on
-
J james referenced this topic on
-
Hello @lanhild
Can you give me the output of:uname -narfrom your system that is failing?
We found systems with kernel version <110are not effected. -
6.8.0-110-genericMy server's =
110. The other server, without the issue, has the same kernel.Hello @Lanhild
On the other server that "does not have the issue".
Can you run:# first run - should work curl 127.0.0.1 # second run - should time out curl 127.0.0.1two times.
If the first time works and the second time fails, this system also has this issue.
The issue only is apparent when connecting to itself. -
Hello @Lanhild
On the other server that "does not have the issue".
Can you run:# first run - should work curl 127.0.0.1 # second run - should time out curl 127.0.0.1two times.
If the first time works and the second time fails, this system also has this issue.
The issue only is apparent when connecting to itself.@james Indeed, the second
curltimes out.But does the original issue from my topic really come from this? I dare have a doubt about it.
As mentioned in a previous reply, the original issue for that other server was solved with the Ubuntu 24 upgrade.
On the other hand, the problem is very much still present on the Cloudron.
Feel free to ask for more debugging cmds.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login