![]() |
Server Address Connection Refusal - 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: Server Address Connection Refusal (/t-server-address-connection-refusal) |
Server Address Connection Refusal - Henwy.mp4 - 2025-09-14 As the description says, any device that I attempt to connect to my Jellyfin Server is met with a constant "Could not connect to server" message without any elaboration or error message besides simply that. I have forwarded all of the Jellyfin Server ports on my default gateway to my desktops static IP address, (where I'm running the server) and all seems to running fine as I have loaded up my folders and they have ported over onto the server. The problem arises when I simply try to access this server remotely on another device such as my phone or TV. I input the address as follows "http://192.168.x.xxx:8096" -The phone and desktop share the same WiFi network, I would like to connect remotely so that I can stream my music anywhere even on mobile data but I must pass this hurdle firstly -I have disabled mobile data -I've forwarded all Jellyfin ports on my gateway that being the two TCP ports and single UDP port, both of which are set to forward directly to my computers IP address (The server) -I've created new inbound rules on my desktop's firewall for the specified ports allowing Domain, Public, and Private -I've set Jellyfin as an exception in my Firewall allowing Domain, Public, and Private -I've tried forwarding the ports to my public IP and entering my public IP into the Server Address box All my attempts at troubleshooting have been met with this one vague error message. Granted I've only been using Jellyfin for a day now and alas I'm just a lowly novice, surely the help of the great Jellyfin forum members would be able to assist me in this endeavor 😥. Any help would be greatly appreciated as I want to break free from streaming but have hit this massive roadblock sadly. |