Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latest docker image?
- Are you sure you're not using someone else's docker image?
- Have you searched for similar issues (both open and closed)?
Describe the bug
When entering a new host on npm, ex. a domain or an ip, should you put a space before or after said host, it wont load at all and throw a 502 which is highly misleading (as its not related to upstream not responding).
The browser will forcefully remove every space on the domain/hostname so the browser guesses right.
It's about following the standard and avoiding confusion as someone would instinctively go check for upstream/docker errors.
A javascript check to remove spaces is presumably enough in my opinion.
Nginx Proxy Manager Version
latest (as per rn)
v2.15.1
To Reproduce
Steps to reproduce the behavior:
As mentioned above.
Expected behavior
502 Error.
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
When entering a new host on npm, ex. a domain or an ip, should you put a space before or after said host, it wont load at all and throw a 502 which is highly misleading (as its not related to upstream not responding).
The browser will forcefully remove every space on the domain/hostname so the browser guesses right.
It's about following the standard and avoiding confusion as someone would instinctively go check for upstream/docker errors.
A javascript check to remove spaces is presumably enough in my opinion.
Nginx Proxy Manager Version
latest (as per rn)
v2.15.1
To Reproduce
Steps to reproduce the behavior:
As mentioned above.
Expected behavior
502 Error.