You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
Yes
Are you sure you're not using someone else's docker image?
Yes
Have you searched for similar issues (both open and closed)?
Yes
Describe the bug
No longer possible to use domain with port in Domain Name because of the error data/domain_names/0 must match pattern "^[^&| @!#%^();:/\\}{=+?<>,~'"]+$`
Nginx Proxy Manager Version
v2.12.3
Expected behavior
It had been working flawlessly for years until one of the recent updates disrupted my configuration
Screenshots
Operating System
Docker
Additional context
This change is completely incomprehensible to me. I had 15 services configured on one subdomain with different ports, e.g., sub.domain.com:5380, sub.domain.com:3001, etc., and they all stopped working after one of the recent updates (to be precise, I lost the ability to edit them via the GUI). Who was bothered by this port? Why force users into a single approach using the default 80/443 ports and differentiating services by domain?
The text was updated successfully, but these errors were encountered:
Remove you :8083 from your domain. And add that to port below.
But that's not what we want to do. This was a way to use other ports than 80 and 443 for reverse proxy. Now we can't do that. Target port and source ports are different things.
Uh oh!
There was an error while loading. Please reload this page.
Checklist
jc21/nginx-proxy-manager:latest
docker image?Describe the bug
No longer possible to use domain with port in Domain Name because of the error
data/domain_names/0 must match pattern "^[^&| @!#%^();:/\\}{=+?<>,~
'"]+$`Nginx Proxy Manager Version
v2.12.3
Expected behavior
It had been working flawlessly for years until one of the recent updates disrupted my configuration
Screenshots

Operating System
Docker
Additional context
This change is completely incomprehensible to me. I had 15 services configured on one subdomain with different ports, e.g., sub.domain.com:5380, sub.domain.com:3001, etc., and they all stopped working after one of the recent updates (to be precise, I lost the ability to edit them via the GUI). Who was bothered by this port? Why force users into a single approach using the default 80/443 ports and differentiating services by domain?
The text was updated successfully, but these errors were encountered: