starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #3376] NPM works locally but only for services on the device it's running at #2266

New issue

Closed

opened 2026-02-26 07:34:47 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @Chillsmeit on GitHub (Dec 9, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3376

Describe the bug
NPM is running on my RPi5 and works without any issues with services on the same device.
The issue is that I can't make any entry work for services being hosted on my desktop PC.
I'm using local/lan only, I have PiHole installed (on a different port than 80 and 443) with unbound.
I have my services added on the /etc/pihole/custom.list:

192.168.1.5 nginx.local
192.168.1.5 pihole.local
192.168.1.6 jellyfin.local
192.168.1.6 prowlarr.local

192.168.1.5 = RPi5
192.168.1.6 = My Desktop PC

I can reach any service using their ips:ports directly, I can also reach nginx.local and pihole.local on multiple devices.
But jellyfin.local or prowlarr.local don't work at all.
Though, If I install a second instance of NPM on my desktop PC, it starts working...

My RPi5 is using RaspbianOSLite64bit and my desktop PC is using OpenSUSE Tumbleweed (without firewall)

Nginx Proxy Manager Version

v2.10.4

Originally created by @Chillsmeit on GitHub (Dec 9, 2023). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3376 **Describe the bug** NPM is running on my RPi5 and works without any issues with services on the same device. The issue is that I can't make any entry work for services being hosted on my desktop PC. I'm using local/lan only, I have PiHole installed (on a different port than 80 and 443) with unbound. I have my services added on the /etc/pihole/custom.list: ``` 192.168.1.5 nginx.local 192.168.1.5 pihole.local 192.168.1.6 jellyfin.local 192.168.1.6 prowlarr.local ``` 192.168.1.5 = RPi5 192.168.1.6 = My Desktop PC I can reach any service using their ips:ports directly, I can also reach nginx.local and pihole.local on multiple devices. But jellyfin.local or prowlarr.local don't work at all. Though, If I install a second instance of NPM on my desktop PC, it starts working... My RPi5 is using RaspbianOSLite64bit and my desktop PC is using OpenSUSE Tumbleweed (without firewall) **Nginx Proxy Manager Version**  v2.10.4

kerem

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

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:34:48 +03:00

Author

Owner

@derrge commented on GitHub (Dec 18, 2023):

I'm having very similar issue. Can't proxy to anything on my LAN. Hope this gets fixed soon.

@derrge commented on GitHub (Dec 18, 2023): I'm having very similar issue. Can't proxy to anything on my LAN. Hope this gets fixed soon.

kerem commented

2026-02-26 07:34:48 +03:00

Author

Owner

@L-i-v-y commented on GitHub (Dec 25, 2023):

Are you forwarding to the correct port?
For instance, for me Jellyfin only works by forwarding to the set port for the container Jellyfin is running in
So in NPM I have it set for my Jellyfin subdomain to forward to the Jellyfin container at the containers port (default should be 8096, I think) and doing HTTPS with NPM and not Jellyfin — I am running everything on the same host though, not using hostname resolving; but maybe this could still help in any way

@L-i-v-y commented on GitHub (Dec 25, 2023): Are you forwarding to the correct port? For instance, for me Jellyfin only works by forwarding to the set port for the container Jellyfin is running in So in NPM I have it set for my Jellyfin subdomain to forward to the Jellyfin container at the containers port (default should be 8096, I think) and doing HTTPS with NPM and not Jellyfin — I am running everything on the same host though, not using hostname resolving; but maybe this could still help in any way

kerem commented

2026-02-26 07:34:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 16, 2024):

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

@github-actions[bot] commented on GitHub (Jul 16, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:34:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Aug 7, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Aug 7, 2025): Issue was closed due to inactivity.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#2266

No description provided.

Rows
Columns