Unable to correctly serve sub-paths using Nginx Proxy Manager

[mcc311]

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 am trying to set up services under sub-paths (e.g., https://mydomain.com/service1) using Nginx Proxy Manager (NPM). While subdomains work fine (e.g., service1.mydomain.com), sub-paths don’t seem to function correctly.

For example, I have configured https://mydomain.com/proxy to forward requests to http://nginx-proxy-manager:81, but when trying to access the service, the resources (CSS, JS, etc.) are still being requested from the root path (https://mydomain.com/) instead of https://mydomain.com/proxy/.

I have tried using custom locations, sub_filter, and proxy_redirect configurations, but the resources are not loading properly from the sub-path.

This issue seems to be similar to what others have experienced in discussion #1288 and this Reddit post, where sub-path forwarding doesn’t work as expected in NPM.

Nginx Proxy Manager Version
v2.11.3

To Reproduce
Steps to reproduce the behavior:

1. Create a proxy host for https://mydomain.com/proxy.
2. Set it to forward to http://nginx-proxy-manager:81.
3. Access https://mydomain.com/proxy in the browser.
4. Check the console for resource loading errors (404 Not Found).

Expected behavior
Resources (CSS, JS, etc.) should load from https://mydomain.com/proxy/ and not from the root path.

Screenshots

This works.

But this doesn't work.

Operating System
Docker on Linux

Additional context

• I have tested this with custom locations in NPM.
• Also tried adding sub_filter rules in Nginx to rewrite resource URLs and using proxy_redirect to ensure any backend redirects retain the /proxy prefix.
• Subdomains work fine, but sub-paths present this issue.
• Docker version 24.0.5, build ced0996

[mitossoft-rd]

I'm having the same problem.

[mitossoft-rd]

The fix in PR #4118 solved my problem.

[bpsbits-org]

I have the same issue

Using release: v2.12.1

[bpsbits-org]

Older configuration for same subpath

  location /app {
    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto  $scheme;
    proxy_set_header X-Forwarded-For    $remote_addr;
    proxy_set_header X-Real-IP		$remote_addr;
    proxy_pass       http://10.88.0.1:8088/app;

    

    
    
  # Block Exploits
  include conf.d/include/block-exploits.conf;

    
    # Force SSL
    include conf.d/include/force-ssl.conf;


    

  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security $hsts_header always;





    
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    


    
  }

New configuration for same subpath

  location /app {
    

    proxy_set_header Host $host;
    proxy_set_header X-Forwarded-Scheme $scheme;
    proxy_set_header X-Forwarded-Proto  $scheme;
    proxy_set_header X-Forwarded-For    $remote_addr;
    proxy_set_header X-Real-IP		$remote_addr;

    set $proxy_forward_scheme http;
    set $proxy_server         "10.88.0.1";
    set $proxy_port           8088;

    proxy_pass       $proxy_forward_scheme://$proxy_server:$proxy_port/app;

    

    
    
  # Block Exploits
  include conf.d/include/block-exploits.conf;

    
    # Force SSL
    include conf.d/include/force-ssl.conf;


    

  # HSTS (ngx_http_headers_module is required) (63072000 seconds = 2 years)
  add_header Strict-Transport-Security $hsts_header always;





    
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection $http_connection;
    proxy_http_version 1.1;
    
  }

[Mainfrezzer]

I have the same issue, for some things, not all funnily enough. For some reason, the "new" proxy_pass malforms requests.
Newest settings saved with 2.12.1

that results in absolut brokenness

if i use the old proxy_pass way, it just works

[miao17game]

using 'rewrite xxx yyy break;' before 'set xxx yyy;' will alse meet this problem.

[bpsbits-org]

I have the same issue, for some things, not all funnily enough. For some reason, the "new" proxy_pass malforms requests. Newest settings saved with 2.12.1

that results in absolut brokenness

if i use the old proxy_pass way, it just works

It’s broken for sure

[kvchoi]

Nginx proxy_pass directives when exist args, should write all args. like this:

location ~* /auth0/(.) {
proxy_pass https://$arg_host/$1$is_args$args;
# $1 mean (.); $is_args mean "?"; $args mean all query parameters.
}

[bpsbits-org]

Nginx proxy_pass directives when exist args, should write all args. like this:

location ~* /auth0/(.) { proxy_pass https://$arg_host/$1$is_args$args; # $1 mean (.); $is_args mean "?"; $args mean all query parameters. }

Please could you explain and provide properly formatted code?

[bpsbits-org]

Proxy pass fails if variables are used

Works

proxy_pass       http://10.88.0.1:8088/app;

Fails

proxy_pass       $proxy_forward_scheme://$proxy_server:$proxy_port/app;

[mitossoft-rd]

As far as I can see, the release has not been published yet. Temporarily, you can use:
nginxproxymanager/nginx-proxy-manager-dev:pr-4118.

[PooruTorie]

Its fixed now with new 2.12.2 release

[bpsbits-org]

Its fixed now with new 2.12.2 release

Yes, seems to work now.