2025-06-02, 09:57 PM
I would be most grateful if anyone can cast a little light on the reason I can't connect my Cambridge CXN streamer to Jellyfin.
I am running Jellyfin 10.8.13 in a docker installation under Open MediaVault 6.9.16-1 (based on Debian Linux) on HP Microserver hardware.
All devices are on the same subnet of my home LAN. I have tested using both wired and wifi connections.
I can access Jellyfin from browser, from an LG smart TV and from a Roku 4k. These devices are listed in the Devices tab together with some older equipment that I no longer use. Everything works well although I have to use Jellyfin Legacy for the Roku.
The Cambridge CXN is specifically not in the list. The Cambridge app that runs on android does not see the server either. However it and the CXN see an older NAS based Twonky server that is still hanging on by it's fingernails. The copy of the music part of the library is accessible by the streamer and plays well. I just checked and it first ran in 2007, so it's remaining time may be measured in hours.
I take it that the problem may relate to the way that Jellyfin handles client discovery.
I should also say that I searched for other questions relating to the Cambridge CXN. The only other one I found related to problems where that installation caould only see the device if the Jellyfin server was restarted. In my problem it can't ever be seen.
I also tried the solution where the blast alive interval in the DLNA config was suggested to be reduced. I have tried several intervals but no difference has been seen.
As always, I'll be very grateful if anyone has suggestions. I would also be keen to know if there are any happy Cambridge CXN users that are also Jellyfin users out in the wild.
Doug
I am running Jellyfin 10.8.13 in a docker installation under Open MediaVault 6.9.16-1 (based on Debian Linux) on HP Microserver hardware.
All devices are on the same subnet of my home LAN. I have tested using both wired and wifi connections.
I can access Jellyfin from browser, from an LG smart TV and from a Roku 4k. These devices are listed in the Devices tab together with some older equipment that I no longer use. Everything works well although I have to use Jellyfin Legacy for the Roku.
The Cambridge CXN is specifically not in the list. The Cambridge app that runs on android does not see the server either. However it and the CXN see an older NAS based Twonky server that is still hanging on by it's fingernails. The copy of the music part of the library is accessible by the streamer and plays well. I just checked and it first ran in 2007, so it's remaining time may be measured in hours.
I take it that the problem may relate to the way that Jellyfin handles client discovery.
I should also say that I searched for other questions relating to the Cambridge CXN. The only other one I found related to problems where that installation caould only see the device if the Jellyfin server was restarted. In my problem it can't ever be seen.
I also tried the solution where the blast alive interval in the DLNA config was suggested to be reduced. I have tried several intervals but no difference has been seen.
As always, I'll be very grateful if anyone has suggestions. I would also be keen to know if there are any happy Cambridge CXN users that are also Jellyfin users out in the wild.
Doug