SOLVED: Connection troubles

[Euphuzade]

Hello!,

I have hit a brick wall on my quest for resolution of my local connection issues after updating to 10.9.8 of Jellyfin and hoping I can find some pointers/help on this case. The more I delve into troubleshooting this, the more I'm starting to suspect it is something with Docker and not Jellyfin but I thought I might as well try posting here if anyone possibly knows. This may be something simple and quick to fix and i am just overlooking things but I am still a novice when it comes to this kind of stuff ( please forgive me I say something silly or not important ).

Current Setup/Details:
- Asustor NAS with IP address of 192.168.1.134 which is hosting Jellyfin
- All devices are connected to the same network/switch in my home ( unmanaged switch )
- Have not done any complex extras to try connecting remotely. Just locally.

I have been using this setup for roughly a year now with no connection issues on any of my local devices ( hard wired or wireless ) but after updating to 10.9.8, I haven't been able to manually connect on any device ( mobile/Shield/computer ). Nor does it show on the available server list like it once did. This update was provided from the Asustor app page which may be a factor or not but just wanted to point that out. I make sure to use 192.168.1.134:8096 when connecting but it just acts like it doesn't exist.

Troubleshooting:
- Restarted Jellyfin multiple times
- Deleted the application and the folders associated with on the NAS
- Installed the DNLA plugin to see if that did anything
- Clean install
- Uninstalled Docker, removed associated folders on NAS, restarted NAS. Clean install of Docker as well

Had some problems at first initiating the setup process again after deleting Jellyfin but thankfully read someone else post here about clearing cache and that worked. Completed the setup process again but no dice when it came finding and connecting my device.

I downloaded Portainer to get some more details on the setup and currently this is what I have ( this is something I've never touched before since the setup from a year ago was quick and painless)

- Local environment
- Connected via Bridge mode with network 172.17.0.0/16 which seems to be the default created network if I'm reading things correctly. 172.17.0.1 being the gateway address
- Jellyfin was assigned the network 172.17.0.2 ( since it's installed on Docker )
- I didn't really mess with any other settings and just left everything as it installed

I did some ping tests from from main computer 192.168.1.171 and I can ping my NAS just fine and i was able to Ping the gateway Docker created 172.17.0.1 but I wasn't able to ping the associated address for Jellyfin

I've attached my Jellyfin log and you'll see the IP address mentioned previously

Hopefully this information is adequate and if you need additional details or if the log is missing information, please let me know.

Thanks in advance

[TheDreadPirate]

You could switch to host networking and not deal with bridge networking.

[Euphuzade]

Finally figured it and it was right in front of my face. Was reading more on the difference of host/bridge modes and the section about allowing ports caught my eye.

https://www.asustor.com/app_central/app_...d=987&type=

Looks like the owner of the container changed the default port from 8096 to 28096 on this latest version and that worked like a charm

This can be marked as solved or closed out

Thank you for the quick response. Greatly appreciate it.