NginxProxyManager / NginxProxyManager/nginx-proxy-manager

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

Open
#4,562 16 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
TypeScript
Stars
34.2k
Forks
3.9k
Avg merge
21h 12m
Merged PRs (30d)
20

Description

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?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the GUI edit failure using the v2.12.3 Docker image and a proxy host such as sub.domain.com:5380. Trace the domain-name validation that produces the reported pattern error, then verify that existing domain-and-port configurations can be edited successfully without breaking the validation rules.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, nginx, typescript
Domain
devops
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.