▲ 230 ▼ I don't know who needs to hear this, but DO NOT EVER expose Jellyfin to the internet (github.com) submitted 1 year ago by Scary_le_Poo@beehaw.org to c/technology@beehaw.org 155 comments fedilink hide all child comments Collection of potential security issues in Jellyfin This is a non exhaustive list of potential security issues found in Jellyfin. Some of these might cause controversy. Some of these are design fla...
[–] Flax_vert@feddit.uk 1 point 1 year ago (1 child) Possibly some ISP interference with the OpenVPN protocol. Apparently that can happen sometimes permalink fedilink source parent hideshow 2 child comments replies: [–] natch@lemmy.today 1 point 1 year ago You can always funnel all your VPN traffic through a more typical port, like 80, and there's very little anyone can do to distinguish between your traffic and typical web traffic. If your ISP causes issues with inbound traffic to your home network, just add another link to the chain to include a cloud-hosted server, or host it all entirely in the cloud (if you find a trustworthy one with a reasonable cost). permalink fedilink source parent
[–] natch@lemmy.today 1 point 1 year ago You can always funnel all your VPN traffic through a more typical port, like 80, and there's very little anyone can do to distinguish between your traffic and typical web traffic. If your ISP causes issues with inbound traffic to your home network, just add another link to the chain to include a cloud-hosted server, or host it all entirely in the cloud (if you find a trustworthy one with a reasonable cost). permalink fedilink source parent