2024-06-18, 10:31 PM
(This post was last modified: 2024-06-18, 11:16 PM by pcm. Edited 4 times in total.)
I agree with TheDreadPirate with the setup if you plan to host jellyfin on the root of your site...
My strategy is different. I don't have jellyfin on the root (/) of my website. My website's root/index page just shows nginx default-homepage.
I host jellyfin on a specific path on my website and I don't host a sitemap so ... good luck trying to figure that out where on my site is jellyfin hosted.
And if, by brute-force someone does figure out the path to jellyfin on my site, I also don't show any user accounts on the jellyfin landing page...
I don't like the reliability of duckdns .. I prefer getting my own domain. I got mine from cheap at namecheap.
I get my certs from zeroSSL.
I'm curious as to why you think you'd need a VPN. The SSL connection between your client and server will ensure that no one can read any data except for the server and the client...
My strategy is different. I don't have jellyfin on the root (/) of my website. My website's root/index page just shows nginx default-homepage.
I host jellyfin on a specific path on my website and I don't host a sitemap so ... good luck trying to figure that out where on my site is jellyfin hosted.
And if, by brute-force someone does figure out the path to jellyfin on my site, I also don't show any user accounts on the jellyfin landing page...
I don't like the reliability of duckdns .. I prefer getting my own domain. I got mine from cheap at namecheap.
I get my certs from zeroSSL.
I'm curious as to why you think you'd need a VPN. The SSL connection between your client and server will ensure that no one can read any data except for the server and the client...