<![CDATA[Unusable application]]>I'm guessing 9.1.3 rendered the application unusable, as the issue appeared later than the latest update of this app.

Pushing/pulling an image from a remote works correctly. However, attempting to pull an image from the same server doesn't work at all.

For instance:

  • I have a registry @ registry.cloudron.local
  • I have an app @ app.cloudron.local, using an image from the registry, on the same cloudron.

Whenever I attempt to update this application with a new image, the pull never works.

Mar 19 18:51:04 box:docker Attempt 1 failed. Will retry: Unable to pull image registry.cloudron.local/app.image:2.0.13. registry error: {"reason":"server error","statusCode":500,"json":null}

In the registry configuration in Cloudron settings, the error Invalid serverAddress: socket hang up appears whenever I attempt to save the private registry settings.

In the registry application logs, there is the following line, appearing intermittently:

Mar 19 20:32:18 time="2026-03-20T00:32:18.895638941Z" level=error msg="traces export: Post \"https://localhost:4318/v1/traces\": dial tcp [::1]:4318: connect: connection refused" go.version=go1.23.7 instance.id=redacted service=registry version=3.0.0

I have multiple Cloudrons, all with a registry application installed and facing the same issue.

As mentioned in the beginning of my topic, pulling from a remote works.

Connecting the private registry registry.cloudron.local in my.other-cloudron.local works perfectly. It seems like there might be a DNS issue.

Feel free to ask for more information.

]]>https://forum.cloudron.io/topic/15265/unusable-applicationRSS for NodeSun, 16 Aug 2026 12:50:12 GMTFri, 20 Mar 2026 00:36:06 GMT60<![CDATA[Reply to Unusable application on Mon, 20 Apr 2026 20:44:11 GMT]]>@james Thanks for the insight. As this is a production server, I'll wait for the update.
Regards.

]]>https://forum.cloudron.io/post/123757https://forum.cloudron.io/post/123757Mon, 20 Apr 2026 20:44:11 GMT<![CDATA[Reply to Unusable application on Mon, 20 Apr 2026 20:41:44 GMT]]>Hello @lanhild

@Lanhild said:

But does the original issue from my topic really come from this? I dare have a doubt about it.

It does.
Since Cloudron asks the docker registry app (localhost or more precise, the docker proxy) it times out.
Same with the cloudron cli issue you send me timing out.
All related to that network issue.
We already have an idea how to fix this, without downgrading the kernel.

If you'd like to try, you could apply this patch manually https://git.cloudron.io/platform/box/-/commit/bffc97ab2fedb06100bc507abd0f8b42d343ea6e and then systemctl restart cloudron-firewall

]]>https://forum.cloudron.io/post/123756https://forum.cloudron.io/post/123756Mon, 20 Apr 2026 20:41:44 GMT<![CDATA[Reply to Unusable application on Mon, 20 Apr 2026 19:21:28 GMT]]>@james Indeed, the second curl times 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.

]]>https://forum.cloudron.io/post/123751https://forum.cloudron.io/post/123751Mon, 20 Apr 2026 19:21:28 GMT<![CDATA[Reply to Unusable application on Mon, 20 Apr 2026 19:11:18 GMT]]>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.1

two 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.

]]>https://forum.cloudron.io/post/123750https://forum.cloudron.io/post/123750Mon, 20 Apr 2026 19:11:18 GMT<![CDATA[Reply to Unusable application on Mon, 20 Apr 2026 18:34:23 GMT]]>@james

6.8.0-110-generic

My server's = 110. The other server, without the issue, has the same kernel.

]]>https://forum.cloudron.io/post/123749https://forum.cloudron.io/post/123749Mon, 20 Apr 2026 18:34:23 GMT<![CDATA[Reply to Unusable application on Mon, 20 Apr 2026 17:46:48 GMT]]>Hello @lanhild
Can you give me the output of:

uname -nar

from your system that is failing?
We found systems with kernel version <110 are not effected.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1130336

]]>https://forum.cloudron.io/post/123746https://forum.cloudron.io/post/123746Mon, 20 Apr 2026 17:46:48 GMT<![CDATA[Reply to Unusable application on Fri, 17 Apr 2026 18:23:39 GMT]]>@lanhild and I did a debugging session.
Somehow this issue is connected to https://forum.cloudron.io/topic/15408/openid-configuration-url-timeout

]]>https://forum.cloudron.io/post/123611https://forum.cloudron.io/post/123611Fri, 17 Apr 2026 18:23:39 GMT<![CDATA[Reply to Unusable application on Fri, 17 Apr 2026 15:06:46 GMT]]>@james Done.

]]>https://forum.cloudron.io/post/123598https://forum.cloudron.io/post/123598Fri, 17 Apr 2026 15:06:46 GMT<![CDATA[Reply to Unusable application on Fri, 17 Apr 2026 15:00:06 GMT]]>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.

]]>https://forum.cloudron.io/post/123596https://forum.cloudron.io/post/123596Fri, 17 Apr 2026 15:00:06 GMT<![CDATA[Reply to Unusable application on Fri, 17 Apr 2026 14:52:38 GMT]]>@robi Yes

Cloudron Container Registry 2.6.0 (registry 3.1.0)

]]>https://forum.cloudron.io/post/123595https://forum.cloudron.io/post/123595Fri, 17 Apr 2026 14:52:38 GMT<![CDATA[Reply to Unusable application on Fri, 17 Apr 2026 14:51:28 GMT]]>@Lanhild after the server upgrade, did the app upgrade yet?

]]>https://forum.cloudron.io/post/123594https://forum.cloudron.io/post/123594Fri, 17 Apr 2026 14:51:28 GMT<![CDATA[Reply to Unusable application on Fri, 17 Apr 2026 14:48:57 GMT]]>@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 😬

]]>https://forum.cloudron.io/post/123593https://forum.cloudron.io/post/123593Fri, 17 Apr 2026 14:48:57 GMT<![CDATA[Reply to Unusable application on Mon, 06 Apr 2026 20:08:24 GMT]]>@nebulon I did the upgrade from Ubuntu 22 to 24 today. I confirm that it fixed the issue for me as well.

]]>https://forum.cloudron.io/post/122974https://forum.cloudron.io/post/122974Mon, 06 Apr 2026 20:08:24 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 18:49:08 GMT]]>Strange how that would have affected it, but well glad it works 🙂

]]>https://forum.cloudron.io/post/122897https://forum.cloudron.io/post/122897Fri, 03 Apr 2026 18:49:08 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 18:38:56 GMT]]>So decided to upgrade my server to Ubuntu 24 and its working now again.

]]>https://forum.cloudron.io/post/122896https://forum.cloudron.io/post/122896Fri, 03 Apr 2026 18:38:56 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 13:44:51 GMT]]>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

]]>https://forum.cloudron.io/post/122887https://forum.cloudron.io/post/122887Fri, 03 Apr 2026 13:44:51 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 13:22:54 GMT]]>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

]]>https://forum.cloudron.io/post/122886https://forum.cloudron.io/post/122886Fri, 03 Apr 2026 13:22:54 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 10:29:46 GMT]]>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

]]>https://forum.cloudron.io/post/122882https://forum.cloudron.io/post/122882Fri, 03 Apr 2026 10:29:46 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 10:15:13 GMT]]>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?

]]>https://forum.cloudron.io/post/122881https://forum.cloudron.io/post/122881Fri, 03 Apr 2026 10:15:13 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 10:05:23 GMT]]>Just tried, that just gives me a telnet: Unable to connect to remote host: Connection refused

]]>https://forum.cloudron.io/post/122879https://forum.cloudron.io/post/122879Fri, 03 Apr 2026 10:05:23 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 08:18:19 GMT]]>So it should work without https:// there so the socket hang up is the issue somehow. Can you telnet via ssh to the registry from that server?

]]>https://forum.cloudron.io/post/122873https://forum.cloudron.io/post/122873Fri, 03 Apr 2026 08:18:19 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 07:44:01 GMT]]>You got a typo in there maybe, or a firewall?

]]>https://forum.cloudron.io/post/122872https://forum.cloudron.io/post/122872Fri, 03 Apr 2026 07:44:01 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 06:54:44 GMT]]>Without https:// I'm getting: Invalid serverAddress: socket hang up

]]>https://forum.cloudron.io/post/122865https://forum.cloudron.io/post/122865Fri, 03 Apr 2026 06:54:44 GMT<![CDATA[Reply to Unusable application on Fri, 03 Apr 2026 06:48:45 GMT]]>@klawitterb try without https://

]]>https://forum.cloudron.io/post/122864https://forum.cloudron.io/post/122864Fri, 03 Apr 2026 06:48:45 GMT