mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #857] support open non standar, low ranges, like 53tcp/udp... #725
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#725
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @doreks on GitHub (Feb 2, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/857
Does anyone know why it is not possible to use the low range ports like 53 or 22...?
@doreks commented on GitHub (Feb 3, 2021):
hi!
I am getting the following error in the log:
nginx: [emerg] bind() to 0.0.0.0.0:53 failed (13: Permission denied)it seems to be caused because these ports belong to the protected port range, but how to do then to be able to have a dns proxy, as indicated here;
https://www.nginx.com/blog/load-balancing-dns-traffic-nginx-plus/
@chaptergy commented on GitHub (May 12, 2021):
Since NPM runs in a docker container you can use any port internally. Just map outside port
53to inside port e.g.5353, then you can use5353in NPM.