More > JRiver Media Center 22 for Linux
[NEW] Docker image - MC headless server
sjhilton:
Hi cassfras21 (and everyone else on this thread),
I'm having an issue with the JRiver docker losing my registration. If I close the container (as opposed to killing JRiver within the container) and restart it then JRiver will come up as being unregistered, which is a bit annoying.
I'm also having trouble registering a media access key - it generates one OK, but if you plug it into JRemote or another client it says it is invalid. A direct local IP connection works fine in JRemote.
I think these issues could be symptomatic of the same network/configuration problem. I'm using the QNAP container station. The container is set up in 'bridge' mode so it has its own IP on the network rather than relying on a private network/port forwarding in the NAS.
I'd be very grateful for any ideas/suggestions. Thanks in advance!
Stuart
cassfras21:
Hi Stuart,
--- Quote from: sjhilton on July 01, 2017, 02:49:42 am ---If I close the container (as opposed to killing JRiver within the container) and restart it then JRiver will come up as being unregistered
--- End quote ---
I am not able to reproduce this issue on demand. In my case, stoping, force stoping or restarting my container doesn't affect the registration key. But I admit already had this behavior by the past and had to register the licence again. But I can't say how this happens.
Do you run data in a dedicated container as I recommend or are you running everything (app and data) in only one container?
About the media access key issue, this is because your container is set up as bridge instead of host. In fact bridge setup hides you container behind NAT in the docker subnet (172.17.0.0/16). For the same reason DLNA won't work in bridge mode too. Give a try in host mode, but your qnap shouldn't use the same tcp/udp port than your container or it will conflict.
Hope it helps a bit!
sjhilton:
Hi cassfras21,
Thanks for your suggestions.
I've tried the host mode and it may have solved the registration issue (I just hard reset the container and restarted it then). There doesn't seem to be any port conflicts so that's all fine.
This doesn't seem to have helped with the media access key issue. I have managed to set up port forwarding so I can connect JRemote from the internet now (via IP) and not just the internal network. It's very strange - JRiver doesn't seem to complete the registration or the testing process for the media access key.
I haven't used a separate data container, because I'm not sure how to do that with the QNAP container station (if you have any ideas on this I'd be happy to try them out!) I have managed to backup the data to my media share using the tar instructions you provided.
thanks again,
Stuart
sjhilton:
Hi cassfras21,
Just thinking perhaps the JRiver registration is linked (in part) to a mac address for the machine? The bridge mode in QNAP container station seems to generate a new mac address every time you stop and start. One of the admins would know if this is likely to be the case.
Stuart
cassfras21:
Hi Stuart,
It's nice the host mode solved your registration issue. I don't know how the JRiver registration process works but when I met this issue I just need to restore my JRiver data container.
For the separated containers setup I don't have specific instructions for QNAP nor for Synology. To proceed I use docker run commands (these from my Docker Hub page) by connecting to my syno with ssh.
For your media access key issue, did you try to generate a new one since you switched to host mode? Maybe it could help.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version