How do i use acme-dns with already running nginx and dns on the host machine?

[3x3cut0r]

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

[sobujbd]

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

[joohoi]

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]

...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).

[lonix1]

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.)

[webprofusion-chrisc]

@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

[lonix1]

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

[sobujbd]

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