Connection to remote aggent with reverse proxy in front does not work about dockge

[pandel]

Ah ok, many thanks! Yes, for some points the documentation here says "go to Kuma wiki", but I would not have thought about that in this special case. Again, many thanks! The dev should really spice up its documentation a little bit though... :D

[crunchiersa]

I had a similar problem - although my setup is a bit different. The problem is most likely that your certifcate used by the reverse proxy is not signed by a "trusted" CA...
I use a self-signed CA to host my services not exposed via a reverse proxy. Dockge actually allows you to enable SSL by mounting the cert and key to the container as a volume and then adding the following two environments:

• DOCKGE_SSL_KEY=/certs/server.key
• DOCKGE_SSL_CERT=/certs/server.crt

After downing and upping the container the exposed port will be reachable via ssl.

After this you need mount the CA-Cert in similar fashion to the "master-Dockge" and add the following environment to the container:

• NODE_EXTRA_CA_CERTS=/HOMELAB.crt

I would assume just adding the NODE-EXTRA_CA_CERTS to the "master-dockge" and leaving your nginx be should also work...

Hope this solves your problem.

[pandel]

@crunchiersa MANY MANY THANKS! Adding the CA to the master dockge container did the job!

But why is there no documentation regarding this here anywhere? I was able to find something about the DOCKGE_SSL_* env vars in the code, but did not find NODE_EXTRA_CA_CERTS anywhere. Where did you get the information about it?

[crunchiersa]

@pandel I also use louislam/uptime-kuma and had a "similar" problem - due to the self-signed CA I had to enable "ignore ssl error/warnings" and found the documentation for louislam/uptime-kuma-environments in the wiki (https://github.com/louislam/uptime-kuma/wiki/Environment-Variables). I figured same dev - similar look ... might be that the envrionment variables are the same too...