![]() |
ports fowarded but cant access remotely - Printable Version +- Jellyfin Forum (https://forum.jellyfin.org) +-- Forum: Support (https://forum.jellyfin.org/f-support) +--- Forum: Troubleshooting (https://forum.jellyfin.org/f-troubleshooting) +---- Forum: Networking & Access (https://forum.jellyfin.org/f-networking-access) +---- Thread: ports fowarded but cant access remotely (/t-ports-fowarded-but-cant-access-remotely) |
ports fowarded but cant access remotely - Jack - 2024-03-13 hey guys setting up my jellyfin server and so far everything works okay inside my network- of course i want to enable them outside of my network as well via remote access- any suggestions guys? this is the error i get when trying to connect via cell service outside of network Connection timed out G5.e: Connection timed out at F5.g.d(Unknown Source:62 ![]() ![]() RE: ports fowarded but cant access remotely - TheDreadPirate - 2024-03-13 You don't need to port forward 1900 and 7359. Those are LAN only protocols for DLNA and service discovery, respectively. That looks like a Verizon FIOS router, correct? What OS is your server running? Can you share your jellyfin logs via https://sourceb.in/ ? RE: ports fowarded but cant access remotely - Jack - 2024-03-13 (2024-03-13, 10:48 PM)TheDreadPirate Wrote: You don't need to port forward 1900 and 7359. Those are LAN only protocols for DLNA and service discovery, respectively. this is my log from droidfin on my phone https://srcb.in/pvW2vGpqcu jellyfin server logs https://srcb.in/9rlZDlwlzT Should i get rid of 1900 and 7359? does it really matter thanks you so much! hope ill be getting it running its currently running on windows 11 and is a fios g3100 (2024-03-13, 10:57 PM)Jack Wrote:(2024-03-13, 10:48 PM)TheDreadPirate Wrote: You don't need to port forward 1900 and 7359. Those are LAN only protocols for DLNA and service discovery, respectively. i also have automatic port fowarding on- i turned that on and the problem persisted LMK if i should disable it RE: ports fowarded but cant access remotely - TheDreadPirate - 2024-03-13 You definitely should get rid of the port 1900 and 7359 port forwarding rules. A) It doesn't work externally anyway and B) exposing them to the Internet is a security risk. Definitely turn off automatic port mapping. It is not needed if you manually setup port forwarding. Are you able to access your Jellyfin locally? Did you enable "Allow remote connections" in the Jellyfin networking dashboard? RE: ports fowarded but cant access remotely - Jack - 2024-03-13 yes i can acess locally on network with phone and laptop- should i disable IPv6 Aswell? i enabled that too remote connections is on. i i turned off IPv6 to get back to defaults. i removed those ports from my verizon router and turned off automatic port mapping and turned off and turned on sever (2024-03-13, 11:04 PM)TheDreadPirate Wrote: You definitely should get rid of the port 1900 and 7359 port forwarding rules. A) It doesn't work externally anyway and B) exposing them to the Internet is a security risk. here is screenshot RE: ports fowarded but cant access remotely - TheDreadPirate - 2024-03-13 IPv6, when all components support it, is fine. I use IPv6 for my setup. But you need to enable it in your router, server OS, client OS, and Jellyfin. Linux and Android should get an IPv6 address automatically if your router is configured to issue them. Same if your mobile ISP provides them. For simplicity, turn off IPv6 support in Jellyfin and your router (if it is currently on) and try again. You will need to restart Jellyfin for that change to apply. RE: ports fowarded but cant access remotely - Jack - 2024-03-13 (2024-03-13, 11:20 PM)Jack Wrote: yes i can acess locally on network with phone and laptop- should i disable IPv6 Aswell? i enabled that too remote connections is on. i i turned off IPv6 to get back to defaults. i removed those ports from my verizon router and turned off automatic port mapping and turned off and turned on sever also after doing this i still fail to connect on my phone off cell service RE: ports fowarded but cant access remotely - TheDreadPirate - 2024-03-13 You are typing your Verizon WAN IP into your phone, correct? Not your LAN IP? 192.168.1.XXX RE: ports fowarded but cant access remotely - Jack - 2024-03-13 (2024-03-13, 11:25 PM)TheDreadPirate Wrote: You are typing your Verizon WAN IP into your phone, correct? Not your LAN IP? 192.168.1.XXX im really sorry but what is my verizon WAN IP? is it G3100 IP? i have turned off ipv6 and turned off autoamtic port forwarding i tried that . Dude your awesome i was PUTTING IN THE WRONG IP! im a moron.... dude your awesome thanks! |