In their comments to a recent post that I made, asking people to share their torrenting ratios, some folks were talking about how they have setup media servers for their parents. This sounded really cool and I would like to do the same thing for my family.
I simply mount my torrenting drives with sshfs and consume media with mpv, because I don’t need anything else. But for my technologically less inclined family members, I guess setting up something with a GUI would be kind and nice.
I am torrenting on a VPN router, behind which there is a switch that only switches a specific port - which I rotate regularly for safety - to a public facing router, so that I can ssh into my home network.
Questions:
- I have no experience with or knowledge of these to me fancy sounding GUI projects. For instance, do my family members create accounts that I then approve? Do I need to install and setup something on their endpoints (for instance, to configure which port to use, etc.) or is it simple enough for the layperson to do this themselves?
- Will the fancy stuff accept and be accessible with port forwarding from my public facing router to my VPN router and then into my torrenting rig just like my ssh server does or am I going to have to set this up directly connected to the public facing router?
Please give me your most straightforward recommendations! 🥰
Youre welcome. I assume there should be a way to stop nginx logs getting generated, or at least make a script to automatically delete them
I may have misunderstood how you had your ports open, do you have them open locally and accessed through your wireguard private network? if so, and you dont mind having others connect to your wireguard server, then youre good to go.
Nginx explained:
let me clarify what nginx and nginx proxy manager are, nginx is the proxy service, nginx proxy manager is nginx with a web dashboard for configuration
as I understand proxy services, they open ports 80 and 443 i think, which are for http and https respectively
from that you can redirect traffic to any local service nginx has access to
you need to host nginx proxy manager on a server and forward http/s and certificate ports (or maybe just http/s) to the server, the server needs local access to jellyfin
you also need a domain to easily get https encryption with letsencrypt, i recommend duckdns
open port:
client > ip:port > your open router > your vpn router > jellyfin
direct access, no filters, no encryption (unless you make your own certs which you need to trust on each client or have all connections from client to server go through wireguard)
nginx/nginx proxy manager:
(subdomain is how nginx knows where or which local ip:port to send incoming traffic)
client > https://subdomain.domain.duckdns.org/ > public network nginx > local network jellyfin
no direct access, nginx filters, encryption
so only a few open ports, lead to as many local services as you want