To avoid this, you will need an IPv4 address on your client, or an IPv6 address on your server.
This confuses me because I have an IPv4 address on the client, and that IPv4 is what the server is seeing make the connection…
/edit
I think I get it.
The client actually only has IPv6. The IPv4 address I’m seeing in the log and whatismyipaddress.com is the address of my mobile providers NAT.
Thanks. I still haven’t totally wrapped my head around IPv6. Stubbornly happy with IPv4 tbh, but it seems the rest of the world is moving on, understandably.
I use Emby instead of Plex or Jellyfin; mostly because it has an Xbox client, and I’ve already got a lifetime licence. One of my most active users only watches via Xbox.
Really don’t like Plexs centralised user system or the overall direction they’ve been headed for years, so I moved away from that long ago (8+ years ago at least). Jellyfin wasn’t up to par at the time (though they’ve made leaps and bounds of progress in that time), and Emby has always supported more types of devices\clients. Their device limit (the client count limit with premeir) has never come into play for me, but I know there are larger user bases out there where that is a problem.
Embys development is extremely slow though, taking YEARS to implement simple features or even address major concerns. Plus their support sucks without the community stepping in and providing it on behalf of the staff. Luke (the main dev) is better at copy+pasting candid responses than he is at actually interacting with human beings.