2024-12-02, 09:05 PM
Got it !
Since nothing obvious seemed to appear into log file, I went back to NAS firewall setting.
DLNA/UPnP service was allowed (1900 port), but not docker/jellyfin service (port 1900 as well).
I've seen that during previous test I had opened all ports without having Jellyfin server working.
Might be the update to DNLA extension version 5 along with this feature allowed in firewall setting, but it works
!
That's still a mysterty why to different "services" are linked to port 1900 and that allowing one does not work for the other, but well, at least it works. Just to sum up if it can be of any help for anyone:
- Jellyfin server running within container manager on Synology NAS
- No obvious message in log file (on NAS, /config folder)
- Static IP address of player allowed to access both DLNA/UPnP and Docker jellyfin "service" in NAS firewall setting
Thanks a lot TheDreadPirate for your answer, it really helped going to the right direction. BTW: love your avatar !!!
Subjet can be changed to SOLVED.
Since nothing obvious seemed to appear into log file, I went back to NAS firewall setting.
DLNA/UPnP service was allowed (1900 port), but not docker/jellyfin service (port 1900 as well).
I've seen that during previous test I had opened all ports without having Jellyfin server working.
Might be the update to DNLA extension version 5 along with this feature allowed in firewall setting, but it works
!That's still a mysterty why to different "services" are linked to port 1900 and that allowing one does not work for the other, but well, at least it works. Just to sum up if it can be of any help for anyone:
- Jellyfin server running within container manager on Synology NAS
- No obvious message in log file (on NAS, /config folder)
- Static IP address of player allowed to access both DLNA/UPnP and Docker jellyfin "service" in NAS firewall setting
Thanks a lot TheDreadPirate for your answer, it really helped going to the right direction. BTW: love your avatar !!!
Subjet can be changed to SOLVED.