Seconding caddy, it’s extremely simple.
Comment on Will this Jellyfin configuration expose me to security risks?
compostgoblin@lemmy.blahaj.zone 4 days agoThank you! What is the most beginner-friendly way to do that?
I’ve been trying to figure this all out for so long, but it feels like every time I overturn one stone I discover there’s another setting or program I need to configure that I didn’t know about
rikudou@lemmings.world 3 days ago
BentiGorlich@gehirneimer.de 3 days ago
Nginx Proxy Manager is the most user friendly way in my opinion :)
rikudou@lemmings.world 3 days ago
Nothing beats caddy for simplicity, IMO.
BentiGorlich@gehirneimer.de 3 days ago
Well I do not have to touch any configuration files with npm and it has a relatively fancy UI
UnpledgedCatnapTipper@lemmy.blahaj.zone 3 days ago
Being able to manage it through a gui web interface is definitely nice. I love how simple it is to work with.
possiblylinux127@lemmy.zip 3 days ago
Caddy is much faster though. I don’t like trying to navigate a UI when you can just write 3 lines in a config.
illusionist@lemmy.zip 4 days ago
Install caddy. Check that it works. Get to know what a firewall is. How it works. Forward your ports from router to the machine. (I use cockpit (preinstalled on fedora) to configure my firewall)
sub.domain.com { reverse_proxy 192.168.178.192:8080 }
Replace 192.168.178.192 with the ip. And 8080 with the port and your domain obviously.
That’s it.