PenningLabs / lxconsole

LXD Graphical Web Console
GNU Affero General Public License v3.0
161 stars 19 forks source link

Cannot access to lxconsole behing nginx-proxy-manager reverse proxy #32

Closed canob closed 3 days ago

canob commented 3 days ago

Hi,

Is there any special need to serve lxconsole docker behind a reverse proxy like nginx-proxy-manager?

Because I have other docker services perfectly working behind nginx-proxy-manager, but I cannot access lxconsole in this case (ERR_CONNECTION_REFUSED).

nginx-proxy-manager frontend offer a selfsigned certificate to access https://lxconsole.domain, and behind lxconsole is running on default port 5000 on http. I have the same for many other docker services perfectly working.

On lxconsole docker logs, I'm seeing this:

172.20.0.1 - - [13/Nov/2024 15:05:16] "GET /api/servers/list_servers?_=1731509049218 HTTP/1.1" 200 -
172.20.0.1 - - [13/Nov/2024 15:05:27] "GET /api/servers/list_servers?_=1731509049219 HTTP/1.1" 200 -
172.20.0.1 - - [13/Nov/2024 15:05:38] "GET /api/servers/list_servers?_=1731509049220 HTTP/1.1" 200 -
/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py:1099: InsecureRequestWarning: Unverified HTTPS request is being made to host '10.0.2.139'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#tls-warnings
  warnings.warn(
/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py:1099: InsecureRequestWarning: Unverified HTTPS request is being made to host '10.0.2.139'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#tls-warnings
  warnings.warn(
/usr/local/lib/python3.10/site-packages/urllib3/connectionpool.py:1099: InsecureRequestWarning: Unverified HTTPS request is being made to host '10.0.2.139'. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/advanced-usage.html#tls-warnings
  warnings.warn(

Thanks in advance for your help.

canob commented 3 days ago

I tried the same architecture (lxconsole behing nginx-proxy-manager) on another server, and is working, so I think it is not a problem of lxconsole.

Sorry.