More > JRiver Media Center 27 for Linux
Docker Image for MC27
NH:
--- Quote from: max096 on February 28, 2021, 12:38:34 pm ---There isnīt really a guide specifically for that. But since you are getting to the panel webui probably you can just instead of :52199 head to :5800 and if you allowed that port too you should get to the noVNC webgui where you can interact with jriver just as you would on a desktop.
--- End quote ---
No luck Max. Cant access any port. Also wrote to QNAP. They said to check the SSH setting which is already checked. Dont know what I am missing. So near yet so far!
Best
NH
max096:
--- Quote from: NH on March 01, 2021, 10:57:23 am ---No luck Max. Cant access any port. Also wrote to QNAP. They said to check the SSH setting which is already checked. Dont know what I am missing. So near yet so far!
Best
NH
--- End quote ---
Did you use host networking or bridge networking when you created the container? Any other details on what it is you did woud help too.
Generally, if you are using host networking you need to allow every single port you want to access from another PC on the firewall of your NAS. If you are using bridge networking you (normally) don't need to do this, but you would have had to pick port forwardings on container creation (normally you'd just forward 5800 to 5800 and so on and so forth, no reason to pick different ports unless one of them is already in use).
Did you already have jriver installed on your NAS before in another way? If yes maybe you already allowed port 52199 in your qnap firewall back then? Hence JRiver ports would be accessible and the others are not.
SSH settings won't get you anywhere. That seems completely unrelated to me. Not sure why qnap support would suggest that.
NH:
Thank you very much Max. Your guidance pointed me in the right direction. I checked the port forwarding on the NAS, on the router, removed one conflict (52199 was forwarded to my Windows PC for the JRiver instance there), checked if my NAS is getting external connectivity. And it worked!! Many many thanks.
I see two links on the container - 52199 which connects to the panel and 5800 which connects to the web GUI of MC. The web GUI and that makes it very easy. I was able to do te library settings and am able to connect to it via Gizmo pretty easily and works without any lag. In fact the connectivity between Gizmo and MC works better than on my PC.
Sharing some learnings and observations:
1. For showing the path on the NAS (volume from host) and connecting it to the mount point, I could connect only one folder. Eg /Media/Music to /data/music. I had one other folder /Media/Music Videos which when I tried to link to the same mount point /data/music it didnt work. I am sure there is a way to connect more than one folder.
2. I have an additional hard disk containing music files connected to the NAS. On windows, I was able to add this as a location in the library by naming it as a network location eg. T: or V:. I am not able to see that in the volume from host. Am I missing something?
3. I could only do bridge networking. With host it wont allow me to. In bridge networking, I chose static IP, didnt choose DHCP because it said that the NAS IP address would have to change. Is that true? I dont know what would have happened if I had chosen DHCP instead.
4. For the static IP to work, I had to use a different IP address than that of the NAS eg. x.x.x.22 when the NAS was x.x.x.21. In fact when I tried to give it the same IP address it hanged (understandably) or for some others it warned me that the IP address was already in use. I presume this is how it is meant to be. Will be good to mention in the instructions. Though I was surprised to know that the container gets a different IP address, like a different machine or network connection. Does this allow me to access my MC from outside the network also? Will try it out. Technically it should since I have a static IP enabled on my router.
5. The size of the web page in the web GUI is smaller in MC 25. I tried it with MC 27 also where it was covering the whole window. I presume there is a setting somewhere to change it. I am using my MC 25 license.
Many thanks Max, Jatzoo, Scobie for your guidance. If you (or any other users) have any reactions to the above will appreciate it.
Many thanks all once again.
Best
NH
max096:
--- Quote from: NH on March 06, 2021, 10:01:50 pm ---1. For showing the path on the NAS (volume from host) and connecting it to the mount point, I could connect only one folder. Eg /Media/Music to /data/music. I had one other folder /Media/Music Videos which when I tried to link to the same mount point /data/music it didnt work. I am sure there is a way to connect more than one folder.
--- End quote ---
You can only mount one thing to /data/music if you need to mount multiple use different mount points. /data/video /data/music2. Does not matter where you mount it to really /data/music was just a suggestion for one of the mounts is all.
--- Quote from: NH on March 06, 2021, 10:01:50 pm ---2. I have an additional hard disk containing music files connected to the NAS. On windows, I was able to add this as a location in the library by naming it as a network location eg. T: or V:. I am not able to see that in the volume from host. Am I missing something?
--- End quote ---
Not sure what you did on Windows in JRiver. You did not mount the drive in windows, but set it up in JRiver? If it did just 'find it' on windows it might not do that when you are using bridge networking. As network discovery is the one thing that's kind of flaky there. But when you manually enter it it should work. It just won't find it by itself.
--- Quote from: NH on March 06, 2021, 10:01:50 pm ---3. I could only do bridge networking. With host it wont allow me to. In bridge networking, I chose static IP, didnt choose DHCP because it said that the NAS IP address would have to change. Is that true? I dont know what would have happened if I had chosen DHCP instead.
--- End quote ---
I don't think it would change the IP of your NAS, but the IP of your docker container won't stay the same after reboots as it will ask your router for an IP address. You can setup what device should get what IP address on your router too. And then you will essentially get a static IP. For the most part you should either setup static IPs outside of the DHCP range your router hands out or manage IPs on your router. Most of the time in small home networks this is not an issue. But if you end up in a situation where your router gives out an IP of lets say 192.168.1.100 and then you startup something that has it's static IP set to exactly that. It just won't work.
--- Quote from: NH on March 06, 2021, 10:01:50 pm ---4. For the static IP to work, I had to use a different IP address than that of the NAS eg. x.x.x.22 when the NAS was x.x.x.21. In fact when I tried to give it the same IP address it hanged (understandably) or for some others it warned me that the IP address was already in use. I presume this is how it is meant to be. Will be good to mention in the instructions. Though I was surprised to know that the container gets a different IP address, like a different machine or network connection. Does this allow me to access my MC from outside the network also? Will try it out. Technically it should since I have a static IP enabled on my router.
--- End quote ---
No it won't make anything accessible outside of your network. You need to do port forwarding on your router with the ports you want to access. The IP changing probably means QNAP created a VM for docker. Could not tell you wether it created one for docker or it created one for this specific container. Technically, yes ofc you can host docker container on your host directly. But most of the time that's not really done. Im running proxmox on my NAS and i also created a seperate VM for docker and some other stuff. Imo, if you have a kind of "do it all" server box like this. You don't really want to install all that much on the host OS. Just because if it breaks that's bad. But if you break the VM it's much less bad. You might even have a snapshot to just go back to a working state. A lot easier to do snapshots with VMs than with an OS that runs on bear metal.
--- Quote from: NH on March 06, 2021, 10:01:50 pm ---5. The size of the web page in the web GUI is smaller in MC 25. I tried it with MC 27 also where it was covering the whole window. I presume there is a setting somewhere to change it. I am using my MC 25 license.
--- End quote ---
You mean the size of :5800 web UI? You can change that with environment variables 'DISPLAY_WIDTH' and 'DISPLAY_HEIGHT' but you have to do this on container creation. It's totally fine to destroy and re-create the container as long as you keep the directory around you mouned to /config you should not even notice it ever disappeared.
NH:
Thanks much Max for your detailed answers!! Very clear.
Best
NH
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version