finder39

I checked and I haven't, the latest version of the repo the unraid template points to is only running v2.12.3

I was able to find a solution to this as well. Previously my x.conf files looked like this: server { set $forward_scheme https; set $server “cool_name.local"; set $port 1234; listen 8080; listen [::]:8080; listen 4443 ssl http2; listen [::]:4443 ssl http2; ... location / { proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Real-IP $remote_addr; proxy_pass http://cool_name.local:1234; ... I modified them like as follows and the container was able to start up right away and everything worked! server { set $forward_scheme https; set $server “192.168.xxx.xxx“; // change this to the IP address instead of the .local name set $port 1234; listen 8080; listen [::]:8080; // these change as well, handling the new way we need to use http2 listen 4443 ssl; listen [::]:4443 ssl; http2 on; ... location / { proxy_set_header Host $host; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header X-Real-IP $remote_addr; proxy_pass http://$server:$port; // this is to make use of what is in the server section

So I dug into this and it turns out the container is out of date. It is currently running v2.12.3 while the current version is v2.12.6 (which includes a fix). See this issue on the Nginx Proxy Manager repo: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4606 And I created this issue on jlesage's docker-nginx-proxy-manager repo: https://github.com/jlesage/docker-nginx-proxy-manager/issues/345. Hopefully it is seen and fixed soon :)