NginxProxyManager
domain name must match pattern "^[^&| @!#%^();:/\\}{=+?<>,~`'"]+$"
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker 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?
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.
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.
Can you use Stream for this instead?
I guess that would work but in the need of custom Nginx conf it still is not enough.
I have this problem also. Its needed for Plex as the IOS app sends the header as domain.com:443 rather than domain.com so a stream isnt going to work on 443.
I have this problem also. Its needed for Plex as the IOS app sends the header as domain.com:443 rather than domain.com so a stream isnt going to work on 443.
I don't think this issue is relevant to that problem. Port 443 is already being handled by Nginx Proxy Manager (Stream included). You just need to setup SSL.
I have this problem also. Its needed for Plex as the IOS app sends the header as domain.com:443 rather than domain.com so a stream isnt going to work on 443.
I don't think this issue is relevant to that problem. Port 443 is already being handled by Nginx Proxy Manager (Stream included). You just need to setup SSL.
Its releveant to the error and changes made to NPN because if i use domain.com and not domain.com:443 it doesnt pass the traffic via nginx it sends it via the plex relay service saying behind nginx is offline as its passing a host header of domain.com:443 and with the new changes I cant add this to the gui like I could in previous versions.
I used this to fix plex in an older version of NPN but now trying to do a new install it wont let me add.
Source: https://www.reddit.com/r/PleX/comments/guwy9a/plex_behind_a_proxy_web_works_fine_ios_apps_say/
" EDIT: Solved. For some reason the Plex iOS apps send “plex.domain.com:443” as the text of the Host header. Most systems will leave off the port if it’s 80 or 443. That was causing my HAProxy “match” rule to return false. When I changed my HAProxy rule to be a begins-with search, all is working. " - This applies for Nginx also.
Same problem, the network operator closed port 80 and 443 in my network and I had to try other ports.
Pulled current version (2.13.4) and this issue still persists. We are also using this extensively at work in some reverse-proxied environments... Currently we fix this via database + config files if we need to make changes.
same problem when trying to input https://mydomain.com as domain, when i do mydomain.com it works but not what i want
same problem when trying to input https://mydomain.com as domain, when i do mydomain.com it works but not what i want
why would you need to enter a domain with https:// ?