I don’t know why you were downvoted for this, you’re right and I figured this out for myself last night when I decided to try figure it out at 1.30am after 3 beers.
I managed to get all my port 80 stuff sorted but my Arr stack for example needs something more, probably the dreaded nginx…
I’m having a look at Caddy now because I’ve never used it before, Nginx I didn’t like when I used it and I’ve recently heard the original developer has left the project and started a new one.
Rehwyn@lemmy.world 8 months ago
Nginx is a lot less painful if you use Nginx Proxy Manager. You get a nice GUI and can easily get SSL certificates with Let’s Encrypt.
7Sea_Sailor@lemmy.dbzer0.com 7 months ago
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 7 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 7 months ago
Caddy and Authentik play very nicely together thanks to caddy
forward_authdirective. 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.