SOLVED: Can't connect to server on local network after fresh Windows install - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +--- Thread: SOLVED: Can't connect to server on local network after fresh Windows install (/t-solved-can-t-connect-to-server-on-local-network-after-fresh-windows-install) |
Can't connect to server on local network after fresh Windows install - h0bgoblin - 2024-04-30 Hi all, This morning I completed a clean reinstall of Windows 10 as I had suspicions of malware. I have since gone about reinstalling all my software and I am struggling to get Jellyfin back up and running. I have reinstalled the server and media player programs and the server is set up correctly - I am able to access perfectly on http://localhost:8096/ - however, I cannot get access via the media player or via the WebOS app on my TV. I only use Jellyfin over the local network and nothing about the network or set up has changed in the couple of hours since I reinstalled Windows. My Windows firewall settings look like this: https://ibb.co/R4yZqYT Log file is here: https://pastebin.com/19FuQDgM I do not have port forwarding set up on my router. I did not have it set up before Windows was reinstalled and my understanding is that this is only relevant when trying to access the server remotely. My IP is static. Everything on the Jellyfin dashboard settings is currently set to default. I'm at a bit of loss after trawling through various forum and reddit posts, everything I have tried hasn't worked (reinstalling everything again, binding local network to 0.0.0.0, setting up a firewall rule to allow anything over 8096) Any advice would be greatly appreciated! Thank you very much! EDIT: I have managed to resolve this - upon looking at my logs more closely I noticed 127.0.0.1 popping up, rather than my actual IP. I thought I'd try 127.0.0.1:8096 instead of my IP:8096 and I've got straight in on both the desktop media player and on the TV. I have no idea what has happened there, so if anyone can explain this, feel free - otherwise, I'm setting to "solved". |