Skip to content

domain name must match pattern "^[^&| @!#%^();:/\\}{=+?<>,~`'"]+$" #4562

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
grzywek opened this issue Jun 2, 2025 · 3 comments
Open

domain name must match pattern "^[^&| @!#%^();:/\\}{=+?<>,~`'"]+$" #4562

grzywek opened this issue Jun 2, 2025 · 3 comments
Labels

Comments

@grzywek
Copy link

grzywek commented Jun 2, 2025

Checklist

  • 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
Image

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?

@grzywek grzywek added the bug label Jun 2, 2025
@AlperShal
Copy link

AlperShal commented Jun 4, 2025

I have just came across this problem. Came here and last created issue is the same. Interesting you (and I) are the only ones reporting this.

@jaycedk
Copy link

jaycedk commented Jun 8, 2025

Remove you :8083 from your domain.
And add that to port below.

@AlperShal
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants