ISP Jellyfin causes Plex media servers to stop functioning
ISP Jellyfin causes Plex media servers to stop functioning
Last week I had fiber installed and it performed much better than my previous slow broadband connection. However, I noticed my Jellyfin server isn't working anymore. After trying to fully uninstall and reinstall it, I can't even reach the setup section because I can't connect to it. The error message I receive is unclear. I'm attempting to connect using the same computer I'm trying to host, but the Plex server keeps prompting me to install it again. I suspect my new ISP might be blocking something, though I don’t have much idea about networking. If anyone could assist, maybe they could help resolve this issue on their side.
When linking from the same network with your personal router, the ISP shouldn't interfere. What adjustments occurred in your connection since switching ISPs? Is it possible to access it from a different device?
Are there any devices from an ISP configured in bridge mode? Including a custom gateway during setup might interfere with traffic. (Your server may also struggle with double NAT.)
I installed fibre and received a new router from my ISP. This router is linked to my TP-Link Archer AX50 via Ethernet to the WAN port. I attempted to connect it to the LAN, but I couldn't reach the router settings page. My current internet configuration matches what I had with my previous ISP, though I’m unsure if my own router was set up for LAN or WAN.
What gadget did you receive from the ISP? If it’s a router, it should operate in bridge mode—you don’t typically connect two regular routers for a single network. I still believe your TP-Link can manage local traffic no matter the setup.
I've attempted to run the Jellyfin server directly using just my ISP router, but that also failed. It seems double NAT might be the issue, though I wasn't sure what you meant by it. Honestly, I wouldn't be surprised if the gateway configuration is the problem. The engineer who installed the fiber told me most users can't use their own router because it's set to bridge mode, but some did work. I thought I was one of those lucky ones, and it worked for me too since I could access it via WAN, though it might not be fully functional.
The router needs to operate in bridge mode. You aim for seamless data exchange between your ISP network and the TP-Link device. The cable linking its WAN port matters—depending on your ONT setup, you might skip the ISP’s router altogether. That would be a double NAT situation. Not ideal. Your TP-Link router should receive all external traffic via its WAN port, just like the ISP router does. If you link a LAN port from one device to the other, they both assign IP addresses to connected devices, leaving your TP-Link router without a way to forward traffic outward. Ideally, there should be a firewall rule on the ISP router blocking this path, and it shouldn’t be blocked further up the ISP network.
It seems the device you received is a Nokia ONT XS-2426G-A. You've already attempted to use Jellyfin on an ISP router without success.
Thank you for your effort! A Jellyfin forum member suggested connecting directly via a web browser using the IP address 192.168.0.165:8096. It seems this method now works, unlike before. Someone else's advice likely made a difference.