Regex scheme broken since v2.12.0 and still

[Nuke142]

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"

[codethought]

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

[Nuke142]

what a solution? Forever 2.11.3 ?

[codethought]

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

[wasdennnoch]

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.

[Nuke142]

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

[codethought]

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.

[github-actions[bot]]

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

[wasdennnoch]

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;
}