Nginx Proxy Manager Issues

[mikenye]

Reported via Discord:

hi guys, installed picard via docker compose and running behind nginx proxy manager. i probably overlooked something since i only get the top bar when accessing the web gui. it's loading for a few seconds and then a red X appears and nothing else. logs seem OK to me. any ideas?

server disconnected: error 1006

picard:
#    build: ~/picard
    container_name: picard
    image: mikenye/picard
    ports:
      - "5800:5800"
    environment:
      - PUID=1000
      - PGID=1001
    volumes:
      - "~/picard/config:/config:rw"
      - "/mnt/BX/Music:/storage:rw"

[ajquick]

Same issue here.

A few things of note. This is listed in the log. Do we need to forward this port as well?

SSLPORT=5900

A few errors popping up:

2021.05.14 22:34:55 LOG5[9]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket 2021.05.14 22:34:56 LOG5[10]: Service [x11vnc_stunnel] accepted connection from 192.168.0.15:65127 2021.05.14 22:34:56 LOG3[10]: SSL_accept: 1408F09C: error:1408F09C:SSL routines:ssl3_get_record:http request 2021.05.14 22:34:56 LOG5[10]: Connection reset: 0 byte(s) sent to TLS, 0 byte(s) sent to socket

Appears to be because the certificates are not present:

/config/certs/vnc-server.pem /config/certs/web-privkey.pem /config/certs/web-fullchain.pem

Nginx Proxy Manager handles the certificates by itself, so there is going to be an issue here.

[ajquick]

I mapped my certs from Nginx to the paths required and the errors went away, but the problem remains.

volumes:
   - "/mnt/cache/appdata/NginxProxyManager/letsencrypt/live/npm-11/fullchain.pem:/config/certs/web-fullchain.pem:rw"
   - "/mnt/cache/appdata/NginxProxyManager/letsencrypt/live/npm-11/privkey.pem:/config/certs/web-privkey.pem:rw"

[ajquick]

I got it working by following details located here:

https://github.com/jlesage/docker-firefox#reverse-proxy

Basically:

-Enable Websocket Support -Add custom location "upstream" with your IP and Port (5800) -Add custom timeout in advanced:

proxy_read_timeout 86400;

You may also need to map your keys like I did above, but I think just having the upstream connection is what you need.

[mikenye]

Thanks so much @ajquick.