▲ 120 ▼ How it feels to try and get Plex to import all your torrented media (thelemmy.club) submitted 2 months ago* (last edited 2 months ago) by sad_detective_man@sopuli.xyz to c/piracy@lemmy.dbzer0.com 86 comments fedilink hide all child comments
[–] nibbler@discuss.tchncs.de 9 points 2 months ago (1 child) I put mine behind a reverse proxy, like any sane person would. Configure an original sni and you are basically invisible. (Tls1.3, doh/dot make it even better, depending on your threat model, but most likely overkill) permalink fedilink source parent hideshow 2 child comments replies: [–] oneser@lemmy.zip 8 points 2 months ago (1 child) While you are (probably?) correct, this is significantly beyond what is required to deploy Plex for a standard home server chump like me. I'm using jellyfin and a few others, but am consciously putting off exposing these services to the web until I can learn enough about security to do so. Given life, this will probably take me the better part of a year... permalink fedilink source parent hideshow 2 child comments replies: [–] nibbler@discuss.tchncs.de 7 points 2 months ago you are right to be careful here. But it certainly is also not a "requirement to deploy jellyfin" either. It's just a good practice to minimize attack surface, no matter what you expose. Unless it's meant for the general public and advertised, then this makes little sense :-) Also, most selfhosters have at best one IP to use. This helps with the one-IP-multiple-webservices problem anyway. permalink fedilink source parent
[–] oneser@lemmy.zip 8 points 2 months ago (1 child) While you are (probably?) correct, this is significantly beyond what is required to deploy Plex for a standard home server chump like me. I'm using jellyfin and a few others, but am consciously putting off exposing these services to the web until I can learn enough about security to do so. Given life, this will probably take me the better part of a year... permalink fedilink source parent hideshow 2 child comments replies: [–] nibbler@discuss.tchncs.de 7 points 2 months ago you are right to be careful here. But it certainly is also not a "requirement to deploy jellyfin" either. It's just a good practice to minimize attack surface, no matter what you expose. Unless it's meant for the general public and advertised, then this makes little sense :-) Also, most selfhosters have at best one IP to use. This helps with the one-IP-multiple-webservices problem anyway. permalink fedilink source parent
[–] nibbler@discuss.tchncs.de 7 points 2 months ago you are right to be careful here. But it certainly is also not a "requirement to deploy jellyfin" either. It's just a good practice to minimize attack surface, no matter what you expose. Unless it's meant for the general public and advertised, then this makes little sense :-) Also, most selfhosters have at best one IP to use. This helps with the one-IP-multiple-webservices problem anyway. permalink fedilink source parent
