More > JRiver Media Center 26 for Linux
Docker Container for JRiver Media Center 26
Afrosheen:
I’d love to be able to do that as I’ve been wanting to connect to the server remotely outside of JRemote. But I’ve had to install the container through QNAPs Container Station app, so I’m not sure how it handles all of the behind the scenes networking. Most QNAP apps outside of Container Station just need a unique port suffix to connect, but when I last did *hosting* with JRiver as a docked container with its own unique port, I couldn’t connect to my NAS and had to reset the main network configs.
I don’t mind to try it again as I now know what to do if it goes sideways again, but I’m not sure if I could do anything differently to the container without coming back to the same problem.
Maybe someone here with a QNAP NAS could show how they set things up?
Scobie:
I'm running this setup using the QNAP Container Station and can hit my container MC server from outside using JRemote, so I think I can do whatever it is you are looking for...?
Happy to help, what exactly are you looking to achieve?
Afrosheen:
Thanks @Scobie!
Since I'm not well versed with using the command line when installing docker images, I went with using the app's GUI when installing the container for JRiver. But I am willing to learn either way. The end goal is to be able to set the IP address to the container so that I can set a hostname to it and then connect to it remotely. Currently I can only connect to the main client when I am connected to the LAN.
Scobie:
I use the Container Station wizard/UI as it provides all the required options and saves having to putty or SSH into the QNAP and run docker commands.
If you're able to connect internally it sounds like you're just about there, and the only thing left to do is sort networking.
I have my Container Network mode set to Bridge and use a static IP to set a unique address for the MC instance on my network. Once it is in this state, MC is behaving no differently to how it would on a physical host on your internal network. If you use DLNA quite a bit in your setup you might want to use DHCP instead, and reserve the address for MC to use. DLNA often works better that way but I find it makes no difference in my setup so leave it at static. Pretty simple, have attached a screenshot.
Only thing to remember is to also add a Mac Address as noted in this thread, I've scrubbed mine out in the screenshot.
Just remember as well to back your library up before making a change to a container setting, as it will most likely cause the image to generate a new container.
To access MC from outside your network you either need to configure port forwarding on your router, or possibly DDNS from within the QNAP.
I use port forwarding, and configure anything coming in on port 5800 to go to the IP Address I configured in my Container Station setup. Similarly for JRemote I configure port 52199.
Afrosheen:
Ok I’m with you so far. Now this is where I have trouble. When you open ports 5800 and 52199 which IP do you list those ports under? I’ve had to set mine to the IP set for JRiver container and not the IP for QNAP. But this means that I can only locally connect because I have to type the local IP with the port suffix; using the hostname for QNAP with the port for JRiver doesn’t allow me to connect like I would with QNAP apps.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version