bug about custom locations for subdirectory of hosts

[respota]

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

Operating System

armv8 linux (docker in openwrtOS)

Additional context

docker version: 3.8 broswer: edge, chrome etc.

[AkshayRao27]

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.

[github-actions[bot]]

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