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 #3534] bug about custom locations for subdirectory of hosts #2348

New issue

Closed

opened 2026-02-26 07:35:12 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 07:35:12 +03:00

Owner

Originally created by @respota on GitHub (Feb 8, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3534

Checklist

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

Describe the bug

I installed npm in docker on the local device (hereinafter referred to as the host, which local ip is 192.168.0.2 ). I want to reverse proxy services on different ports of the host in different paths under the same domain name, for example:
My domain name is main.exmaple.com, and the agency relationship I want to achieve is

main.exmaple.com/login proxy 192.168.0.2:88;
main.exmaple.com/down proxy 192.168.0.2:8080;
main.exmaple.com/upload proxy 192.168.0.2:8088;

I found that the custom locations are set to the following correspondence:

/login -> 192.168.0.2/ 88;
/down -> 192.168.0.2/ 8080;
/upload -> 192.168.0.2/ 8088;

It can be displayed online normally, but when I access the subpath of the domain name, a blank page is loaded and I cannot access it normally. However, it can work normally when I proxy a non-host IP service according to the above rules. How can I fix it? Thanks.

Nginx Proxy Manager Version
2.10.4 2.11.1 2.11.2

To Reproduce
Refer to [Describe the bug] above.

Expected behavior

can be work correctly.

Screenshots

Operating System

armv8 linux (docker in openwrtOS)

Additional context

docker version: 3.8
broswer: edge, chrome etc.

Originally created by @respota on GitHub (Feb 8, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3534  **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug**  I installed npm in docker on the local device (hereinafter referred to as the host, which local ip is **192.168.0.2** ). I want to reverse proxy services on different ports of the host in different paths under the same domain name, for example: My domain name is main.exmaple.com, and the agency relationship I want to achieve is 1. `main.exmaple.com/login` proxy `192.168.0.2:88`; 2. `main.exmaple.com/down` proxy `192.168.0.2:8080`; 3. `main.exmaple.com/upload` proxy `192.168.0.2:8088`; I found that the `custom locations` are set to the following correspondence: 1. `/login` -> `192.168.0.2/ ` `88`; 2. `/down` -> `192.168.0.2/ ` `8080`; 3. `/upload` -> `192.168.0.2/ ` `8088`; It can be displayed online normally, but when I access the subpath of the domain name, a blank page is loaded and I cannot access it normally. However, it can work normally when I proxy a non-host IP service according to the above rules. How can I fix it? Thanks. **Nginx Proxy Manager Version** `2.10.4` `2.11.1` `2.11.2` **To Reproduce** Refer to [Describe the bug] above. **Expected behavior**  can be work correctly. **Screenshots**  ![image](https://github.com/NginxProxyManager/nginx-proxy-manager/assets/128489984/39886e63-7235-4861-a8d9-0c22cc21a5e1) **Operating System**  armv8 linux (docker in openwrtOS) **Additional context**  docker version: 3.8 broswer: edge, chrome etc.

kerem

2026-02-26 07:35:12 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:35:12 +03:00

Author

Owner

@AkshayRao27 commented on GitHub (Feb 13, 2024):

I had a similar issue where teslamate-local.mydomain.com was working but teslamate-local.mydomain.com/grafana was showing a blank page that said "Not Found". https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3512#issuecomment-1940868886 is what worked for me.

@AkshayRao27 commented on GitHub (Feb 13, 2024): I had a similar issue where `teslamate-local.mydomain.com` was working but `teslamate-local.mydomain.com/grafana` was showing a blank page that said "Not Found". https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3512#issuecomment-1940868886 is what worked for me.

kerem commented

2026-02-26 07:35:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 4, 2024):

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

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

kerem commented

2026-02-26 07:35:12 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 6, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Sep 6, 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#2348

No description provided.

Rows
Columns