starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #4083] Regex scheme broken since v2.12.0 and still #2656

New issue

Open

opened 2026-02-26 07:36:21 +03:00 by kerem · 8 comments

kerem commented

2026-02-26 07:36:21 +03:00

Owner

Originally created by @wpresident on GitHub (Oct 18, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4083

v2.12.0 and v2.12.1 not allow me to use scheme i use all last years. Works perfect if i go back to 2.11.3, apply it, and upgrade again to latest.
If it is not a bug, how should i correctly convert my aged scheme to new?
Must be allowed as "any_letters_numbers.domain.com"

Originally created by @wpresident on GitHub (Oct 18, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4083 ![image](https://github.com/user-attachments/assets/a581fcff-a1a3-4c23-b48e-87502733297b) v2.12.0 and v2.12.1 not allow me to use scheme i use all last years. Works perfect if i go back to 2.11.3, apply it, and upgrade again to latest. If it is not a bug, how should i correctly convert my aged scheme to new? Must be allowed as **"any_letters_numbers.domain.com"**

kerem added the

bug

label

2026-02-26 07:36:21 +03:00

kerem commented

2026-02-26 07:36:22 +03:00

Author

Owner

@codethought commented on GitHub (Oct 24, 2024):

That looks almost exactly like what I reported.. Clearly the schema was modified but what I want to know is if that's intentional, like you said - how do we handle this now?

https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4090

@codethought commented on GitHub (Oct 24, 2024): That looks almost exactly like what I reported.. Clearly the schema was modified but what I want to know is if that's intentional, like you said - how do we handle this now? https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4090

kerem commented

2026-02-26 07:36:22 +03:00

Author

Owner

@wpresident commented on GitHub (Mar 18, 2025):

what a solution? Forever 2.11.3 ?

@wpresident commented on GitHub (Mar 18, 2025): what a solution? Forever 2.11.3 ?

kerem commented

2026-02-26 07:36:22 +03:00

Author

Owner

@codethought commented on GitHub (Mar 18, 2025):

No the solution is to NOT do what we've been doing.. that's actually not how you configure nginx correctly...

See my post (now closed) here..

https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4090

@codethought commented on GitHub (Mar 18, 2025): No the solution is to NOT do what we've been doing.. that's actually not how you configure nginx correctly... See my post (now closed) here.. https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4090

kerem commented

2026-02-26 07:36:22 +03:00

Author

Owner

@wasdennnoch commented on GitHub (Mar 18, 2025):

This issue isn't about forwarding based on port though, or at least OP didn't mention that.

In my case, I'd like to use regex capture groups to match arbitrary subdomains, and use that captured names as part of the path in the proxy_pass directive. Something like <type>.<name>.my-package-registry.com -> proxy_pass http://nexus:8081/repository/<name>-<type>/.

With stock nginx, this works just fine, and I think it should work equally well in NPM, except the failing input validation prevents the regex from being used.

@wasdennnoch commented on GitHub (Mar 18, 2025): This issue isn't about forwarding based on port though, or at least OP didn't mention that. In my case, I'd like to use regex capture groups to match arbitrary subdomains, and use that captured names as part of the path in the proxy_pass directive. Something like `<type>.<name>.my-package-registry.com` -> `proxy_pass http://nexus:8081/repository/<name>-<type>/`. With stock nginx, this works just fine, and I think it should work equally well in NPM, except the failing input validation prevents the regex from being used.

kerem commented

2026-02-26 07:36:22 +03:00

Author

Owner

@wpresident commented on GitHub (Mar 18, 2025):

No the solution is to NOT do what we've been doing.. that's actually not how you configure nginx correctly...

See my post (now closed) here..

#4090

you talking about different situation and i'm not paste any ports, i need proper regex

@wpresident commented on GitHub (Mar 18, 2025): > No the solution is to NOT do what we've been doing.. that's actually not how you configure nginx correctly... > > See my post (now closed) here.. > > [#4090](https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4090) you talking about different situation and i'm not paste any ports, i need proper regex

kerem commented

2026-02-26 07:36:22 +03:00

Author

Owner

@codethought commented on GitHub (Mar 18, 2025):

Got it .. different reason - same error message.. I'd ask on the nginx groups if what you want is supposed to be possible.. if it is report back here.. if it is NOT (like in my case) then you will no longer be able to do that with NPM.

@codethought commented on GitHub (Mar 18, 2025): Got it .. different reason - same error message.. I'd ask on the nginx groups if what you want is supposed to be possible.. if it is report back here.. if it is NOT (like in my case) then you will no longer be able to do that with NPM.

kerem commented

2026-02-26 07:36:22 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 28, 2025):

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

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

kerem commented

2026-02-26 07:36:22 +03:00

Author

Owner

@wasdennnoch commented on GitHub (Dec 8, 2025):

This is still an issue and not stale; now with the new UI you don't even get the button to add a domain to the list when entering a regex.

In vanilla nginx you can easily accompish this using

server_name ~^(?<repo>[^.]+)\.(?<type>[^.]+)\.my-registry\.com$;

location /v2 {
	proxy_pass http://nexus:8081/repository/$repo-$type$request_uri;
}

@wasdennnoch commented on GitHub (Dec 8, 2025): This is still an issue and not stale; now with the new UI you don't even get the button to add a domain to the list when entering a regex. <img width="537" height="144" alt="Image" src="https://github.com/user-attachments/assets/aa656c0f-fd9e-4c09-99d3-fa923f066ea2" /> --- In vanilla nginx you can easily accompish this using ```nginx server_name ~^(?<repo>[^.]+)\.(?<type>[^.]+)\.my-registry\.com$; location /v2 { proxy_pass http://nexus:8081/repository/$repo-$type$request_uri; } ```

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#2656

No description provided.

Rows
Columns