▲ 36 ▼ Will this Jellyfin configuration expose me to security risks? (lemmy.blahaj.zone) submitted 1 year ago by compostgoblin@lemmy.blahaj.zone to c/selfhosted@lemmy.world 21 comments fedilink hide all child comments Here’s my proposed configuration: OrangePi Zero 3 running DietPi Jellyfin with media libraries on an external hard drive Dynamic DNS from DuckDNS to access server remotely via Finamp Is there anything I’m missing? Do I need Lets Encrypt or fail2ban?
[–] illusionist@lemmy.zip 16 points 1 year ago (1 child) Yes, you need TLS permalink fedilink source hideshow 2 child comments replies: [–] compostgoblin@lemmy.blahaj.zone [S] 5 points 1 year ago (3 children) Thank 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 permalink fedilink source parent hideshow 6 child comments replies: [–] illusionist@lemmy.zip 9 points 1 year ago* (last edited 1 year 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) Use a caddyfile with the content 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. permalink fedilink source parent [–] rikudou@lemmings.world 6 points 1 year ago Seconding caddy, it's extremely simple. permalink fedilink source parent [–] BentiGorlich@gehirneimer.de 4 points 1 year ago (1 child) Nginx Proxy Manager is the most user friendly way in my opinion :) permalink fedilink source parent hideshow 2 child comments replies: [–] rikudou@lemmings.world 7 points 1 year ago (1 child) Nothing beats caddy for simplicity, IMO. permalink fedilink source parent hideshow 2 child comments replies: [–] BentiGorlich@gehirneimer.de 5 points 1 year ago (2 children) Well I do not have to touch any configuration files with npm and it has a relatively fancy UI permalink fedilink source parent hideshow 4 child comments replies: [–] UnpledgedCatnapTipper@lemmy.blahaj.zone 4 points 1 year ago Being able to manage it through a gui web interface is definitely nice. I love how simple it is to work with. permalink fedilink source parent [–] possiblylinux127@lemmy.zip 1 point 1 year 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. permalink fedilink source parent
[–] compostgoblin@lemmy.blahaj.zone [S] 5 points 1 year ago (3 children) Thank 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 permalink fedilink source parent hideshow 6 child comments replies: [–] illusionist@lemmy.zip 9 points 1 year ago* (last edited 1 year 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) Use a caddyfile with the content 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. permalink fedilink source parent [–] rikudou@lemmings.world 6 points 1 year ago Seconding caddy, it's extremely simple. permalink fedilink source parent [–] BentiGorlich@gehirneimer.de 4 points 1 year ago (1 child) Nginx Proxy Manager is the most user friendly way in my opinion :) permalink fedilink source parent hideshow 2 child comments replies: [–] rikudou@lemmings.world 7 points 1 year ago (1 child) Nothing beats caddy for simplicity, IMO. permalink fedilink source parent hideshow 2 child comments replies: [–] BentiGorlich@gehirneimer.de 5 points 1 year ago (2 children) Well I do not have to touch any configuration files with npm and it has a relatively fancy UI permalink fedilink source parent hideshow 4 child comments replies: [–] UnpledgedCatnapTipper@lemmy.blahaj.zone 4 points 1 year ago Being able to manage it through a gui web interface is definitely nice. I love how simple it is to work with. permalink fedilink source parent [–] possiblylinux127@lemmy.zip 1 point 1 year 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. permalink fedilink source parent
[–] illusionist@lemmy.zip 9 points 1 year ago* (last edited 1 year 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) Use a caddyfile with the content 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. permalink fedilink source parent
[–] rikudou@lemmings.world 6 points 1 year ago Seconding caddy, it's extremely simple. permalink fedilink source parent
[–] BentiGorlich@gehirneimer.de 4 points 1 year ago (1 child) Nginx Proxy Manager is the most user friendly way in my opinion :) permalink fedilink source parent hideshow 2 child comments replies: [–] rikudou@lemmings.world 7 points 1 year ago (1 child) Nothing beats caddy for simplicity, IMO. permalink fedilink source parent hideshow 2 child comments replies: [–] BentiGorlich@gehirneimer.de 5 points 1 year ago (2 children) Well I do not have to touch any configuration files with npm and it has a relatively fancy UI permalink fedilink source parent hideshow 4 child comments replies: [–] UnpledgedCatnapTipper@lemmy.blahaj.zone 4 points 1 year ago Being able to manage it through a gui web interface is definitely nice. I love how simple it is to work with. permalink fedilink source parent [–] possiblylinux127@lemmy.zip 1 point 1 year 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. permalink fedilink source parent
[–] rikudou@lemmings.world 7 points 1 year ago (1 child) Nothing beats caddy for simplicity, IMO. permalink fedilink source parent hideshow 2 child comments replies: [–] BentiGorlich@gehirneimer.de 5 points 1 year ago (2 children) Well I do not have to touch any configuration files with npm and it has a relatively fancy UI permalink fedilink source parent hideshow 4 child comments replies: [–] UnpledgedCatnapTipper@lemmy.blahaj.zone 4 points 1 year ago Being able to manage it through a gui web interface is definitely nice. I love how simple it is to work with. permalink fedilink source parent [–] possiblylinux127@lemmy.zip 1 point 1 year 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. permalink fedilink source parent
[–] BentiGorlich@gehirneimer.de 5 points 1 year ago (2 children) Well I do not have to touch any configuration files with npm and it has a relatively fancy UI permalink fedilink source parent hideshow 4 child comments replies: [–] UnpledgedCatnapTipper@lemmy.blahaj.zone 4 points 1 year ago Being able to manage it through a gui web interface is definitely nice. I love how simple it is to work with. permalink fedilink source parent [–] possiblylinux127@lemmy.zip 1 point 1 year 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. permalink fedilink source parent
[–] UnpledgedCatnapTipper@lemmy.blahaj.zone 4 points 1 year ago Being able to manage it through a gui web interface is definitely nice. I love how simple it is to work with. permalink fedilink source parent
[–] possiblylinux127@lemmy.zip 1 point 1 year 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. permalink fedilink source parent