No custom location possible!

[XHyperDEVX]

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 cannot define a custom subpath. Today at noon everything still worked, but not anymore. I have reinstalled NPM, same error. What is the reason? When I put it in like this, the entry goes offline. If I take it out, it works again. It seems to be a syntax problem. I can't explain it any other way the npm container is in the same network as the apache2 container. [-> before it worked the same way. it also does not work if i replace "apache2" with the ip of the container]

Nginx Proxy Manager Version v2.11.1

To Reproduce Steps to reproduce the behavior:

1. Add"Custom Location" Entry

Expected behavior The entry does not go offline

Screenshots see above

Operating System Debian with Docker

Additional context no

[irrwitzer42]

I can second this observation. What worked in 2.10.4 just fine, does not with 2.11.1:

Unfortunately the config file gets deleted / not created, so I could not check it any deeper.

[XHyperDEVX]

i have the same error as you in the picture. we definitely have the same problem. Edit: i have now reset my instance to V2.10.4 and it works fine again. so i can also confirm this statement. it seems to be a bug

[irrwitzer42]

This seems to be a duplicate of https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3484 and https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3474 I rolled back to 2.10.4 on all my NPMs for now. Waiting for the next release.

[RajawatBanna]

I am also facing this issue and done hello lot of googling, changing rule until i found this page.

[Wek-mad]

I also having the same error, some how the add_header cannot write to the conf file and it made the proxy stop. hope this bug fix soon

[jackfalveyiv]

Running NPM on Unraid, ran into this problem on a fresh new install of the docker. Hosts were working fine on the old docker, but the same configuration under the custom location that previously worked immediately makes the proxy host go offline on the new one.

[MiguelTVMS]

The same problem is happening to me.

[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 how I fixed it.

[masterwishx]

Same issue with lasted version using portainer in Oracle Cloud