Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dockge disconnects randomly behind reverse proxy and won't respond for a while in same browser #711

Open
2 tasks done
steampoweredtaco opened this issue Jan 14, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@steampoweredtaco
Copy link

⚠️ Please verify that this bug has NOT been reported before.

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

This is a weird one. I use caddy and a reverse proxy for a domain availably locally and provide valid certs to access dockge.

Sometimes when I edit a stack and hit deploy dockge will immediately disconnect from the server with an error and a few seconds shows the following (see screenshot).

image

At this point I cannot refresh or go to another tab and get even a response from dockge, it just sits there and spins.

What is odd, dockge is still running fine. If I go directly to the IP address and port I exposed via docker it will pop up no problem. If I go to a different browser completely it will still work fine using the reverse proxy and dns name. After some long period of time the dns connection via the reverse proxy will work in that browser it was disconnected again.

At this time, I am unsure if the issue happens also without the reverse proxy, I'll use it for a bit and report back if I see it there to. I don't have issues with the reverse proxy for any of the other caddy reverse proxies, so I don't think that is it for the momemnt.

The issue follows in different browsers, it isn't just a chrome issue.

This appears to me like the symptoms I have seen years past where a browser is only limited to X amount of connections per domain and until they are finished. Is there something in dockge UI that will reach out to the backend multiple times, like connecting to the socket multiple times and leaking it somehow? The issue does not clear up when I exit the original tab and open another.

👟 Reproduction steps

Just make edits to stack containers and redeploy them, after a few times I usually get this behavior.

👀 Expected behavior

No freezes

😓 Actual Behavior

See description.

Dockge Version

1.4.2

💻 Operating System and Arch

Ubuntu 20.04 x86_64

🌐 Browser

Chrome 131 (and Edge shows issue)

🐋 Docker Version

20.10.12

🟩 NodeJS Version

Node.js v18.17.1

📝 Relevant log output

No response

@steampoweredtaco steampoweredtaco added the bug Something isn't working label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant