[GH-ISSUE #2699] Does npm not support proxy for the server deployed on port 80 ? #1863

New issue

Closed

opened 2026-02-26 07:32:47 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 07:32:47 +03:00

Owner

Originally created by @chuwza on GitHub (Mar 17, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2699

My docker config is this:
docker run -d
-p 8188:81
-p 8088:80
-p 4438:443
-v c:/docker/npm/data:/data
-v c:/docker/npm/letsencrypt:/etc/letsencrypt
jc21/nginx-proxy-manager

Does npm not support proxy for the server deployed on port 80 ? When I use npm proxies such as 192.168.1.1:80, 192.168.1.2:80, after configuration, I visit the URL , and error "Forbidden Rejected request from RFC1918 IP to public server address"

Even I found that even though I didn't deploy the service on port 80, npm would still report this error when I visited the URL! (In the case of no service, 502 Bad Gateway should be reported, so this is strange)

After my testing, as long as it is not port 80, e.g. emby 192.168.1.2:8096, e.g. calibre-web 192.168.1.2:8083
These internal servers can be successfully proxyed, but once an internal server with port 80 is proxyed, such as 192.168.1.1:80, such as 192.168.1.2:80, the error "Forbidden Rejected request from RFC1918 IP to public server address" will appear

this is OK (192.168.1.2:8096)

this is error (192.168.1.2:80, it seems that as long as it points to port 80, whether the IP of the service is 192.168.1.1 or 192.168.1.2 or 192.168.1.3, this error will be reported, does npm not support pointing to port 80?)

Originally created by @chuwza on GitHub (Mar 17, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2699 My docker config is this: docker run -d -p 8188:81 -p 8088:80 -p 4438:443 -v c:/docker/npm/data:/data -v c:/docker/npm/letsencrypt:/etc/letsencrypt jc21/nginx-proxy-manager Does npm not support proxy for the server deployed on port 80 ? When I use npm proxies such as 192.168.1.1:80, 192.168.1.2:80, after configuration, I visit the URL , and error "Forbidden Rejected request from RFC1918 IP to public server address" Even I found that even though I didn't deploy the service on port 80, npm would still report this error when I visited the URL! (In the case of no service, 502 Bad Gateway should be reported, so this is strange) After my testing, as long as it is not port 80, e.g. emby 192.168.1.2:8096, e.g. calibre-web 192.168.1.2:8083 These internal servers can be successfully proxyed, but once an internal server with port 80 is proxyed, such as 192.168.1.1:80, such as 192.168.1.2:80, the error "Forbidden Rejected request from RFC1918 IP to public server address" will appear this is OK (192.168.1.2:8096) ![屏幕截图(195)](https://user-images.githubusercontent.com/30049891/225890131-09a80861-a7b5-4ed6-8e31-c09152e3971a.png) ![屏幕截图(193)](https://user-images.githubusercontent.com/30049891/225883013-847bcb8b-5c97-4842-9cef-0cb2c4520ee8.png) this is error (192.168.1.2:80, it seems that as long as it points to port 80, whether the IP of the service is 192.168.1.1 or 192.168.1.2 or 192.168.1.3, this error will be reported, does npm not support pointing to port 80?) ![屏幕截图(194)](https://user-images.githubusercontent.com/30049891/225889439-5393261e-2ddc-41e4-a87a-729246d754ba.png) ![屏幕截图(191)](https://user-images.githubusercontent.com/30049891/225883103-f0864409-6afe-4901-b60d-3291b5e0fd16.png)