mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #3508] No custom location possible! #2335
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#2335
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @XHyperDEVX on GitHub (Jan 29, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3508
Checklist
jc21/nginx-proxy-manager:latestdocker image?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:
Expected behavior
The entry does not go offline
Screenshots
see above
Operating System
Debian with Docker
Additional context
no
@irrwitzer42 commented on GitHub (Jan 29, 2024):
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 commented on GitHub (Jan 29, 2024):
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 commented on GitHub (Jan 29, 2024):
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 commented on GitHub (Jan 31, 2024):
I am also facing this issue and done hello lot of googling, changing rule until i found this page.
@Wek-mad commented on GitHub (Feb 2, 2024):
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 commented on GitHub (Feb 3, 2024):
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 commented on GitHub (Feb 5, 2024):
The same problem is happening to 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 how I fixed it.
@masterwishx commented on GitHub (Feb 17, 2024):
Same issue with lasted version using portainer in Oracle Cloud
@github-actions[bot] commented on GitHub (Sep 4, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@EDIflyer commented on GitHub (Nov 9, 2024):
custom locations still don't seem seem to work for me on v.2.12.1
@gthvidsten commented on GitHub (Apr 29, 2025):
Same for v2.12.3 :(
@gthvidsten commented on GitHub (Apr 29, 2025):
Okay, I actually got it to work with v2.12.3.
It's really really sensitive about slashes.
Setting up a custom location with
/mypath/pointing to hostnamemyhost/works. Note the trailing slashes everywhere.So:
Having a trailing slash in location but not hostname: Doesn't work.
Having no trailing slashes in neither location nor hostname: Doesn't work.
Having trailing slashes for both location and hostname: Works!
Might be something that should be automatically added.
This link tipped me off:
I edited directly in the
datamount/nginx/proxy_host/<hostnumber>.confand experimented with thelocationdirective. I then disabled/enabled another host to reload the configs, and it started working.I could then recreating the behaviour in the UI.
@github-actions[bot] commented on GitHub (Nov 1, 2025):
Issue is now considered stale. If you want to keep it open, please comment 👍