starred/dockge-louislam

Fork 0

mirror of https://github.com/louislam/dockge.git synced 2026-03-03 02:06:55 -05:00

Cannot connect Agent when using HTTPS/SSL #230

New issue

Open

opened 2026-02-20 13:12:24 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 13:12:24 -05:00

Owner

Originally created by @KristianNaess on GitHub (Oct 13, 2025).

⚠️ 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

📝 Relevant log output

Originally created by @KristianNaess on GitHub (Oct 13, 2025). ### ⚠️ Please verify that this bug has NOT been reported before. - [x] I checked and didn't find similar issue ### 🛡️ Security Policy - [x] I agree to have read this project [Security Policy](https://github.com/louislam/dockge/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: - https://servername.domain.no:5001 - http://servername.domain.no:5001 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 ### 📝 Relevant log output ```shell ```

deekerman added the

bug

label

2026-02-20 13:12:24 -05:00

deekerman commented

2026-02-20 13:12:25 -05:00

Author

Owner

@eliasfloreteng commented on GitHub (Nov 19, 2025):

Did you get it to work without https even? I have a similar problem but it does not work over http either

@eliasfloreteng commented on GitHub (Nov 19, 2025): Did you get it to work without https even? I have a similar problem but it does not work over http either

deekerman commented

2026-02-20 13:12:25 -05:00

Author

Owner

@RuntimeError123 commented on GitHub (Nov 24, 2025):

I was having the same issue. I copied over the config I am using for Uptime Kuma:
In compose.yaml:
Under volumes:
- /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt:ro

Under environment:
- NODE_EXTRA_CA_CERTS=/etc/ssl/certs/ca-certificates.crt

Works flawless now

Edit: provided the agent host is using a correct certificate and is trusted through your ca-certificates.crt

@RuntimeError123 commented on GitHub (Nov 24, 2025): I was having the same issue. I copied over the config I am using for Uptime Kuma: In compose.yaml: Under volumes: - /etc/ssl/certs/ca-certificates.crt:/etc/ssl/certs/ca-certificates.crt:ro Under environment: - NODE_EXTRA_CA_CERTS=/etc/ssl/certs/ca-certificates.crt Works flawless now Edit: provided the agent host is using a correct certificate and is trusted through your ca-certificates.crt