when reading through the jellyfin with chromecast guide i realized that it would probably be less effort to just let the casting api be public, with the added bonus that i could then cast my library to any device that supports it. but that seems like it would paint a giant target on the server.
what’s the recommended way of doing stuff like this? ideally i want to be able to go to someone’s house and just play some of my media on their tv.
not that any of this is doable in the near future, since i’m behind cgnat and won’t get my colocated bounce server up until spring.
No problemo.
Thanks for pointing out the reverse proxy comment. I think I was wrong to say simply putting jellyfin behind a reverse proxy will increase your security.
The benefits may only be minute or non-existent if you don’t use the reverse proxy for handling other stuff like HTTPS (and redirects to https, etc), restricting access or adding extra authentication requirements (mainly https).
It may also be good to note that Jellyfins docs explicitly do not recommend directly exposing jellyfin ports to the internet (a reverse proxy or using a vpn are recommended instead).
Still I will continue to feel safer always using a reverse proxy when I expose to the internet (maybe my misconceptions).
Thanks again, mate. So basically, if I’m exposing my junk to the world, and by junk I mean service(s), and by world I mean the open internet, I should do it using a reverse proxy and enable HTTPS, otherwise it’s not really very secure? Would that be a reasonable takeaway?
Yet again, thanks. Especially for pointing out the things you (may) be not so sure about. That’s admirable. 🫡
Hehe yep, that’s a good takeaway and the same as what I think.
Thank you too, i enjoyed this discussion.
Awesome, same 😊 All the best to you buddy!