Unusable application
-
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. -
@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 @lanhild
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 -
Hello @lanhild
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 -
J joseph marked this topic as a regular topic
-
G girish referenced this topic
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