mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #1580] Specific Location is working, General Location is giving 404 for same URI #1190
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#1190
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 @zane-shus on GitHub (Nov 10, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1580
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
I have created a working Host. When I added a very specific location (down to the PHP page level e.g. /subfolder/page.php ) for a sub URI to go to a different backend container I am able to get locations to work, but when I create a generic location (at the /subfolder/ level), it is not able to work. As I am only making a small change, I am assuming its a bug.
Nginx Proxy Manager Version
To Reproduce
Steps to reproduce the behavior:
4. Hit your site.com/othercontainer/test.php and it works
5. Then, Change the location to be generic
6.
7. Now I can no longer get to site.com/othercontainer/test.php
8. I am getting a 404 Not Found which I believe is coming from site.com
Expected behavior
I would have expected them to hit the same content
Screenshots
As attached in description
Operating System
Using NPM within Portainer on Docker Swarm, on CentOS hosts. All are latest versions.
Additional context
None
@chaptergy commented on GitHub (Nov 10, 2021):
Unfortunately locations have been a little broken for a few versions, unfortunately all attempts to mitigate the problem have resulted in other issues. https://github.com/jc21/nginx-proxy-manager/pull/1578 reverted all the changes related to that hopefully resulting in locations working properly again. But you'll have to wait until a new release is published.
@zane-shus commented on GitHub (Nov 10, 2021):
thanks for this. Would it be possible to manually do it in this area instead?

(I come from HAProxy, this is my first dip into NGINX, so a little green)
@chaptergy commented on GitHub (Nov 10, 2021):
Yes you can, by adding something like this:
@zane-shus commented on GitHub (Nov 10, 2021):
your a champion, thank you! Worked perfect.
@chaptergy commented on GitHub (Nov 10, 2021):
Great to hear! Then I'll close this for now. Be on the lookout for new releases, so you could potentially change back to the built in locations. Or leave it in the advanced config. Your choice ;)