-
-
Notifications
You must be signed in to change notification settings - Fork 616
Description
⚠️ Please verify that this bug has NOT been reported before.
- I checked and didn't find similar issue
🛡️ Security Policy
- I agree to have read this project Security Policy
Description
After adding SSL certs and running Dockge as a HTTPS server, I cannot add it as an agent. I had to remove the certs to be able to add an Dockge instance as an agent.
I tried to add it with the following URLs:
Both gave the error: Unable to connect to the Dockge instance
When I removed the following to environment parameters, I could connect it again:
This is the log entries when it all works (no log entries when the instance is HTTPS):
dockge | 2025-10-13T12:03:29Z [AGENT-MANAGER] INFO: This connection is connected as an agent, skip connectAll()
dockge | 2025-10-13T12:03:29Z [AUTH] INFO: Successfully logged in user XXXXX. IP=10.0.0.195
dockge | 2025-10-13T12:03:29Z [SERVER] INFO: Socket disconnected!
dockge | 2025-10-13T12:03:29Z [AUTH] INFO: Origin is not set, IP: ::ffff:10.0.0.195
dockge | 2025-10-13T12:03:29Z [SERVER] INFO: Socket connected (agent), as endpoint dockerpi5.krisn.no:5001
dockge | 2025-10-13T12:03:29Z [AUTH] INFO: Login by username + password. IP=10.0.0.195
dockge | 2025-10-13T12:03:29Z [RATE-LIMIT] INFO: remaining requests: 18.062333333333335
dockge | 2025-10-13T12:03:30Z [AGENT-MANAGER] INFO: This connection is connected as an agent, skip connectAll()
dockge | 2025-10-13T12:03:30Z [AUTH] INFO: Successfully logged in user XXXXX. IP=10.0.0.195
👟 Reproduction steps
Enable HTTPS and try to connect the instance as an agent.
👀 Expected behavior
Being able to connect an HTTPS enabled Dockge instance as an agent
😓 Actual Behavior
was not able to connect an HTTPS enabled Dockge instance as an agent
Dockge Version
1.5.0
💻 Operating System and Arch
Debian GNU/Linux 12 (bookworm)
🌐 Browser
Edge
🐋 Docker Version
Docker version 28.4.0, build d8eb465
🟩 NodeJS Version
unknown