INTERACT FORUM

More => Old Versions => JRiver Media Center 28 for Linux => Topic started by: joetiii on November 18, 2021, 06:11:22 am

Title: Quick question on Licensing and configuration
Post by: joetiii on November 18, 2021, 06:11:22 am
I just got a Synology NAS and am interested in setting up the current MC27 running on my PC. Do I have to buy a new version of MC27 for Linux to get it to run? or can I use my current key to download MC27 for the Synology?

Second question pertains to configuring my Library. I was a victim of the WD hack back in June and am currently getting my music, video and photos recovered off that drive. In the mean time, I am adding lossless files to my pc library which is stored on the NAS. I have read that working within windows to manage library playlists, ratings etc. is quicker than using webgui. Not sure this is true, so I am wondering if I should continue on working within windows MC27, and then update and install MC on the NAS once all my data files are back from recovery?
Title: Re: Quick question on Licensing and configuration
Post by: HaWi on November 18, 2021, 08:35:06 am
You'll need a Linux license or, as I would recommend, a universal license. I'd also recommend to set up MC in Docker using the shiomax image. Regarding pre-production, I'd do that in Windows as much as possible because things are going to be significantly slower on the NAS.
Title: Re: Quick question on Licensing and configuration
Post by: joetiii on November 18, 2021, 11:10:16 am
Yes I have setup the shiomax image in docker already and "think" it's set up correctly. I say that because now that it is running, I have tried using the web gui to view the image and I get a message that the ip cannot be reached. Not sure where and when the license gets put in,....and thought that might be one of the problems,
Title: Re: Quick question on Licensing and configuration
Post by: HaWi on November 19, 2021, 01:18:51 pm
You should still be able to get to see MC on the webpage even if it's unlicensed. This sounds more like a permissions/firewall issue.
First, I'd recommend giving your NAS a reserved IP address on your router. Then you also need to make sure that your firewall rules allow access to the specific port on your NAS. Also, make sure you used the correct GUID and UID when you started up the container. I had that wrong initially and couldn't access the container until I corrected it. Max was very helpful in getting all set up correctly.
Finally, when it is all running as expected I'd recommend installing Portainer, if you haven't already done so, which makes it really easy to update containers.