Well I already have jellyfin running in a container, just have to figure out how to get mum's TV to work with it I guess
log in on a local IP and not the network name and it's working again. but I'll be moving to jellyfin from now
this post was submitted on 26 Sep 2025
720 points (95.9% liked)
Selfhosted
59973 readers
443 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.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
how is using a FQDN user error when the logs show the access is from a 10.1.1.x address?
You’re using the wrong address, that’s how it’s user error.
If you just use the Plex app you wouldn’t have this issue either. Were you watching media on your Plex server machine through a browser instead of just opening Plex, and you typed in a url in the browser? Plex say to always just use app.plex.tv as it takes care of it all for you so things like this don’t happen.
There isn’t even a debate here though - it’s an issue with the way your network is set up, not with Plex. Plex’s networking is far more advanced and better technically than jellyfins.