Nginx Proxy Manager VS acme-dns

I ended up using the NGINX Proxy Manager [the projects home site] and added certificates but I'm seeing a fair number of installs going with https://traefik.io on YouTube.

Nginx Proxy Manager is a very easy and popular reverse proxy with a GUI.

Otherwise is the Nginx Proxy Manager a nice looking Reverse Proxy based on nginx with a GUI. I've been using it myself for a few years and experienced a few times some stability problems after updating with docker compose. Otherwise rock solid for me.

My reverse proxy does it automatically, NginxProxyManager.

Put on Debian or Ubuntu, using docker/docker-compose install Plex, Nextcloud (nice way to store your files), and some sort of reverse proxy like NPM.

Yes, after a long while, it was updated, on an update with no new features, that broke the software software for many people, including myself. (Check out the numerous bug reports for version 2.10.x and the recommended fix is to rollback to 2.9.22. They have been announcing and promising version 3 for over 2 years.

How about dockerising your application then using Nginx proxy manager as your proxy it's so easy to get ssl certificate and to install and setup that's how I'd serve it https://nginxproxymanager.com/... check it out

I run a t4g.nano ec2 ($5/month) instance as a Nebula lighthouse with Nginx Proxy Manager (NPM). My lab hosts run a nebula instance, and I reverse proxy to them over Nebula.

As someone else said, it’s a huge pain to run your own dns services. However, if you want some separation, I recently saw https://github.com/joohoi/acme-dns

v0.9.1 is out and natively supports both https://github.com/joohoi/acme-dns and any dns provider available in https://github.com/acmesh-official/acme.sh

What DNS challenge providers are supported? Specifically, is acme-dns (https://github.com/joohoi/acme-dns) supported?

I have set up an acme-dns server to answer ACME DNS Challenges: https://github.com/joohoi/acme-dns

Wanting to set up acme-dns for acquiring wildcard certificates. I have a decent understanding of DNS and Let's Encrypt (at least HTTP validation), but there are a few things I don't quite understand after having read the instructions. Can't really find any sort of support channel.

The DNS challenge can be easily automated using https://github.com/joohoi/acme-dns - you do need an IP you can run a DNS server on though.

b) If you have a fairly static IP, you can setup an acme-dns instance

It's a bit more involved, but you can set up wildcard certificates to update automatically. Certbot has some pre-made plugins for this for several DNS providers. If yours is not on that list, there's a tool called acme-dns which is a minimal DNS server you can run on your server and delegate _acme-challenge.yourdomain.com to. If you don't want to run that on your own, you can also use the publicly hosted server/API for it.

In case you're not already familiar with it: one thing I'd recommend is using https://github.com/joohoi/acme-dns to obtain the certificates. You basically just point the subdomain you need wildcard certs for at that DNS server (a one time thing, ie you don't have to do this every three months), and the related tool https://github.com/acme-dns/acme-dns-client can get the certificates in a nice, automated, way without you ever having to expose the private reverse proxy to the Internet.