starred/acme-dns

Fork 0

mirror of https://github.com/acme-dns/acme-dns.git synced 2026-04-27 04:45:48 +03:00

[GH-ISSUE #286] How do i use acme-dns with already running nginx and dns on the host machine? #146

New issue

Open

opened 2026-03-13 15:56:25 +03:00 by kerem · 7 comments

kerem commented

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

Owner

Originally created by @3x3cut0r on GitHub (Nov 18, 2021).
Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/286

i have an nginx-reverse-proxy on my host machine. do i need to redirect /register and /update to a custom port 80 port on the docker? is this enough?

whats about the port 53? how do i handle this with an already running unbound or another dns-server on the host machine?, which is also not holding the domain. the host dns-servers upstream dns is holding the domain...

i need some help to understand howto configure the acme-dns with an LE wildcard cert.

thank you

Originally created by @3x3cut0r on GitHub (Nov 18, 2021). Original GitHub issue: https://github.com/acme-dns/acme-dns/issues/286 i have an nginx-reverse-proxy on my host machine. do i need to redirect /register and /update to a custom port 80 port on the docker? is this enough? whats about the port 53? how do i handle this with an already running unbound or another dns-server on the host machine?, which is also not holding the domain. the host dns-servers upstream dns is holding the domain... i need some help to understand howto configure the acme-dns with an LE wildcard cert. thank you

kerem commented

2026-03-13 15:56:31 +03:00

Author

Owner

@sobujbd commented on GitHub (Dec 22, 2021):

I would like to know, can I use acme-dns on my existing VPS that is being used for web hosting?

@sobujbd commented on GitHub (Dec 22, 2021): I would like to know, can I use **acme-dns** on my existing VPS that is being used for web hosting?

kerem commented

2026-03-13 15:56:36 +03:00

Author

Owner

@joohoi commented on GitHub (Jan 25, 2022):

You can do reverse proxying for /register and /update as you assumed, that will work.

Your problem does come along with the DNS though. The acme-dns DNS server needs to be running on port 53 in order for it to work. So you'll probably need to host acme-dns instance on some other box instead.

@joohoi commented on GitHub (Jan 25, 2022): You can do reverse proxying for `/register` and `/update` as you assumed, that will work. Your problem does come along with the DNS though. The acme-dns DNS server needs to be running on port 53 in order for it to work. So you'll probably need to host acme-dns instance on some other box instead.

kerem commented

2026-03-13 15:56:41 +03:00

Author

Owner

@joohoi commented on GitHub (Jan 25, 2022):

...or, depending on acme-dns client in use, you can also use a non-standard HTTP(S) port, there's no requirement for hosting the API on port 443 (or 80 in that regard).

@joohoi commented on GitHub (Jan 25, 2022): ...or, depending on acme-dns client in use, you can also use a non-standard HTTP(S) port, there's no requirement for hosting the API on port 443 (or 80 in that regard).

kerem commented

2026-03-13 15:56:46 +03:00

Author

Owner

@lonix1 commented on GitHub (Jun 14, 2022):

Did you guys find a client that doesn't use ports 80/443? (I'm also trying to run it on a server that already has services on those ports.)

@lonix1 commented on GitHub (Jun 14, 2022): Did you guys find a client that doesn't use ports 80/443? (I'm also trying to run it on a server that already has services on those ports.)

kerem commented

2026-03-13 15:56:51 +03:00

Author

Owner

@webprofusion-chrisc commented on GitHub (Jun 14, 2022):

@lonix1 what does your app do if you just specify the port (whatever you need it to be) e.g. https://your-acme-dns:8443/register

@webprofusion-chrisc commented on GitHub (Jun 14, 2022): @lonix1 what does your app do if you just specify the port (whatever you need it to be) e.g. https://your-acme-dns:8443/register

kerem commented

2026-03-13 15:56:56 +03:00

Author

Owner

@lonix1 commented on GitHub (Jun 14, 2022):

No TXT record found at _acme-challenge.auth.foo.com - I suspect my config is wrong. I will look into that.

@lonix1 commented on GitHub (Jun 14, 2022): No TXT record found at _acme-challenge.auth.foo.com - I suspect my config is wrong. I will look into that.

kerem commented

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

Author

Owner

@sobujbd commented on GitHub (Jul 25, 2022):

We can use custom port for HTTP requests.
See this - acmedns.sh

@sobujbd commented on GitHub (Jul 25, 2022): We can use custom port for HTTP requests. See this - [acmedns.sh](https://gist.github.com/sobujbd/0826cf67c56ef82bd354fe6dd91484b6#file-acmedns-sh-L9)