[GH-ISSUE #70] raise an error if acme-dns can't listen/bind to a specified port. #25

New issue

Closed

opened 2026-03-13 15:24:26 +03:00 by kerem · 5 comments

kerem commented

2026-03-13 15:24:26 +03:00

Owner

Originally created by @jvanasco on GitHub (Apr 10, 2018).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/70

while doing some debugging of firewall rules, I realized that acme-dns will start up fine as an unprivileged user who can't bind to port 53 (if that is the configured port). I think it should probably raise an error OR print a warning line in these situations.

Originally created by @jvanasco on GitHub (Apr 10, 2018). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/70 while doing some debugging of firewall rules, I realized that acme-dns will start up fine as an unprivileged user who can't bind to port 53 (if that is the configured port). I think it should probably raise an error OR print a warning line in these situations.

kerem

2026-03-13 15:24:26 +03:00

closed this issue
added the
bug
label

kerem commented

2026-03-13 15:24:42 +03:00

Author

Owner

@mearsten commented on GitHub (May 28, 2018):

#85 fixes that

@mearsten commented on GitHub (May 28, 2018): #85 fixes that

kerem commented

2026-03-13 15:24:47 +03:00

Author

Owner

@Ajedi32 commented on GitHub (Oct 31, 2018):

Pretty sure this is a duplicate of #118, and is now fixed in #122

@Ajedi32 commented on GitHub (Oct 31, 2018): Pretty sure this is a duplicate of #118, and is now fixed in #122

kerem commented

2026-03-13 15:24:52 +03:00

Author

Owner

@jvanasco commented on GitHub (Oct 31, 2018):

well, #118 is a duplicate of this - and it looks like printing a warning is handled by #122.

@joohoi does #122 only log a warning, or can it cause a fatal error if unable to bind?

@jvanasco commented on GitHub (Oct 31, 2018): well, #118 is a duplicate of this - and it looks like printing a warning is handled by #122. @joohoi does #122 only log a warning, or can it cause a fatal error if unable to bind?

kerem commented

2026-03-13 15:24:57 +03:00

Author

Owner

@joohoi commented on GitHub (Oct 31, 2018):

does #122 only log a warning, or can it cause a fatal error if unable to bind?

Both, it calls log.Fatal(err) which logs the error, and then exits. :)

@joohoi commented on GitHub (Oct 31, 2018): > does #122 only log a warning, or can it cause a fatal error if unable to bind? Both, it calls `log.Fatal(err)` which logs the error, and then exits. :)

kerem commented

2026-03-13 15:25:02 +03:00

Author

Owner

@jvanasco commented on GitHub (Oct 31, 2018):

Wonderful. Closing this! thanks for the fix, this has bugged me for months!

@jvanasco commented on GitHub (Oct 31, 2018): Wonderful. Closing this! thanks for the fix, this has bugged me for months!

kerem referenced this issue

2026-03-13 16:13:35 +03:00

[PR #25] [MERGED] Make cors messages respect the debug flag #247