If you dont fear using a little bit of terminal, caddy imo is the better choice. It makes SSL even more brainless (since its 100% automatic), is very easy to configure yet very powerful if you need it, doesnt require a 200 MB mysql database and does not have issues with path filtering due to UI abstractions. There are many more advantages to caddy over NPM. I have not looked back since I switched.
Rehwyn@lemmy.world 8 months ago
I’ll check it out. I suspect configuration would likely be a little bit more complicated in my case because I’m using Authentik for proxy forward authentication and had also been using access control groups in NPM (both a LAN group and a WAN group containing Cloudflare proxy IP addresses, since currently all my publicly accessible domains proxy through Cloudflare).
7Sea_Sailor@lemmy.dbzer0.com 8 months ago
Caddy and Authentik play very nicely together thanks to caddy
forward_auth
directive. Regarding acls, you’ll have to read some documentation, but it shouldnt be difficult to figure out whatsoever. The documentation and forum are great sources of info.