starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-26 01:45:54 +03:00

[GH-ISSUE #1789] "proxy_pass" cannot have URI part in location given by regular expression #1321

New issue

Closed

opened 2026-02-26 07:30:29 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 07:30:29 +03:00

Owner

Originally created by @binsentsu on GitHub (Jan 22, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1789

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes / No
Are you sure you're not using someone else's docker image?
- Yes / No
Have you searched for similar issues (both open and closed)?
- Yes / No

Describe the bug

Within version 2.9.11 regular expressions were supported with custom location configurations.
Example: ~ ^(/~[^/]+)?(?:/|/path)?$
Now upgraded to 2.9.15 and this functionality is not working anymore.
Nginx shows error when bringing up the proxy:
"proxy_pass" cannot have URI part in location given by regular expression

It seems to me that commit github.com/NginxProxyManager/nginx-proxy-manager@1f879f67a9 (diff-d59b1035c5) introduced in 2.9.13 has changed this behavior.

Within 2.9.11 the proxy_pass referenced variable $upstream which is likely to work together with regular expression locations.

Don't know why code stepped away from using a variable, but would it be possible to re-enable this 'feature'?

Nginx Proxy Manager Version

v2.9.15

To Reproduce
Steps to reproduce the behavior:

Create a custom location config containing regular expression.

Expected behavior

Working as in 2.9.11

Screenshots

Operating System

Additional context

Originally created by @binsentsu on GitHub (Jan 22, 2022). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1789  **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - **Yes** / No - Are you sure you're not using someone else's docker image? - **Yes** / No - Have you searched for similar issues (both open and closed)? - **Yes** / No **Describe the bug**  Within version 2.9.11 regular expressions were supported with custom location configurations. Example: `~ ^(/~[^/]+)?(?:/|/path)?$` Now upgraded to 2.9.15 and this functionality is not working anymore. Nginx shows error when bringing up the proxy: `"proxy_pass" cannot have URI part in location given by regular expression` It seems to me that commit https://github.com/NginxProxyManager/nginx-proxy-manager/commit/1f879f67a9bed8f5eb444d00ad47c353b8a75db8#diff-d59b1035c588d4d81d509bb6c436f753aa5256a9cada91f28b6afc55b26d2c6b introduced in 2.9.13 has changed this behavior. Within 2.9.11 the proxy_pass referenced variable $upstream which is likely to work together with regular expression locations. Don't know why code stepped away from using a variable, but would it be possible to re-enable this 'feature'? **Nginx Proxy Manager Version**  v2.9.15 **To Reproduce** Steps to reproduce the behavior: 1) Create a custom location config containing regular expression. **Expected behavior**  Working as in 2.9.11 **Screenshots**  **Operating System**  **Additional context**

kerem

2026-02-26 07:30:29 +03:00

closed this issue
added the
stale

bug
labels

kerem commented

2026-02-26 07:30:30 +03:00

Author

Owner

@bytebone commented on GitHub (Mar 7, 2023):

It's a little crazy to me that this has gone completely unanswered and unseen for over a year. I am stuck with NPM not wanting to use RegEx, and find it infuriating. I can see that the expressions are being applied into the config file, yet they simply don't work. And other times, when I try to apply the config, the host just gets disabled.

What reason can there be to not have this working? Is there a switch somewhere I can toggle, a module I should install, or anything else I can do to get this working? If there's simply no option to use RegEx, and no change in sight, I might have to drop NPM alltogether, which would be a shame really.

I am experiencing this on NPM v2.9.18.

@bytebone commented on GitHub (Mar 7, 2023): It's a little crazy to me that this has gone completely unanswered and unseen for over a year. I am stuck with NPM not wanting to use RegEx, and find it infuriating. I can see that the expressions are being applied into the config file, yet they simply don't work. And other times, when I try to apply the config, the host just gets disabled. What reason can there be to not have this working? Is there a switch somewhere I can toggle, a module I should install, or anything else I can do to get this working? If there's simply no option to use RegEx, and no change in sight, I might have to drop NPM alltogether, which would be a shame really. I am experiencing this on NPM v2.9.18.

kerem commented

2026-02-26 07:30:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 26, 2024):

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

@github-actions[bot] commented on GitHub (Feb 26, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:30:30 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 11, 2025):

Issue was closed due to inactivity.

@github-actions[bot] commented on GitHub (Apr 11, 2025): Issue was closed due to inactivity.

kerem commented

2026-02-26 07:30:30 +03:00

Author

Owner

@7heMech commented on GitHub (Nov 13, 2025):

Is it still the case?

@7heMech commented on GitHub (Nov 13, 2025): Is it still the case?

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#1321

No description provided.

Rows
Columns