58
Round Two: Can I manage to set up Jellyfin correctly this time?
(self.selfhosted)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Aug 2025
58 points (100.0% liked)
Selfhosted
50550 readers
366 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 2 years ago
MODERATORS
I use Nginx Proxy Manager and whitelist my remote users. They all have static IPs though, so its a workable solution for me.
Before I used a whitelist I would go through the access logs, and could never find any attempts to exploit the endpoints - only some random bots trying to find some admin page assuming it was another service. Not saying you shouldn't take it seriously, but you are likely not subject to these attacks the moment you expose it.
That said, there is a discussion about these endpoints on their repo. At some point they will be fixed (my impression is that they are hampered by legacy Emby code). When they do, you could do this more securely.