Jellyfin seems to not work after the update to 10.9.11.r01 on asustor - 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: Jellyfin seems to not work after the update to 10.9.11.r01 on asustor (/t-jellyfin-seems-to-not-work-after-the-update-to-10-9-11-r01-on-asustor) |
Jellyfin seems to not work after the update to 10.9.11.r01 on asustor - TheCollectorX TheMrX - 2024-10-28 I doesnt start after the NAS restarts (It has a turn off and turn on date) The port forwarding doesn't work with the new ports even after updating the rule on the router. The settings still reference the port on the dashboard RE: Jellyfin seems to not work after the update to 10.9.11.r01 on asustor - theguymadmax - 2024-10-28 You need to use 28096 to access Jellyfin. "The default web UI mapping port are changed to 28096 (HTTP) and (28920) from 10.9.8.r01, since DLNA is not default supported anymore from Jellyfin 10.9.0, we can use network bridge for this container." https://www.asustor.com/app_central/app_...d=987&type RE: Jellyfin seems to not work after the update to 10.9.11.r01 on asustor - TheCollectorX TheMrX - 2024-10-29 I know it just doesnt start . Not even after reinstalling and deleting the jellyfin folder in docker folder. (2024-10-28, 05:04 PM)theguymadmax Wrote: You need to use 28096 to access Jellyfin. RE: Jellyfin seems to not work after the update to 10.9.11.r01 on asustor - TheDreadPirate - 2024-10-29 Are there any docker or other system logs available from your NAS? Are you able to tell if another app is binding to the same ports? Or if there is a zombie Jellyfin container? RE: Jellyfin seems to not work after the update to 10.9.11.r01 on asustor - TheCollectorX TheMrX - 2024-10-29 nothing uses those ports 28096 if it did it wouldn't let me install it. during the last 2 times it did this it started working randomly after a install |