Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Scobie]

Certainly not a restart of the container, that works fine and does not require License entry

Actually made a liar out of myself...just restarted the container after updating to the latest MC24 release and on restart I get the "Trial Period has Expired..." splashscreen and forced to enter my license again.

Must be something up with my volume setup?

[Jatzoo]

Scobie, what do You mean "after updating to the latest MC24 release"?

[Awesome Donkey]

If the MC24 Docker image uses an older MC build (like before 24.0.40) there was changes during that time to how registration works to fix issues with the registration being lost, e.g. after kernel updates. If you're using a recent build, you shouldn't encounter that issue anymore. But if you're upgrading from an older build, you might need to add the registration again.

[Scobie]

If the MC24 Docker image uses an older MC build (like before 24.0.40) there was changes during that time to how registration works to fix issues with the registration being lost, e.g. after kernel updates. If you're using a recent build, you shouldn't encounter that issue anymore. But if you're upgrading from an older build, you might need to add the registration again.

Thanks Awesome Donkey, I remember that thread but I was going from .72 to .74 so shouldn't be the cause, unless the issue has resurfaced?

Scobie, what do You mean "after updating to the latest MC24 release"?

Hi Jatzoo, when I see there is a new MC24 Linux version available I restart the container to install the update. This is what causes the license to need reinstalling.

However I did test yesterday by restarting the container when there was no available update, and it expired the license again.

Is there a way to upgrade without restarting? Sorry still finding my way around Docker.

Scobie

[Jatzoo]

Scobie, if You want to test, please delete current container with JRiverMC and create again with my step-by-step instructions from previous page with small change - in step 6 for "Mount Point": "/home/jriver/.jriver" please enter in "New volume": "jrivermc_data" - this will create a persistent volume for JRiverMC data (You will be able to see it in menu Volume in Container Station).

[Scobie]

Thanks Jatzoo, I will give that a try when I get a moment.

Appreciate your ongoing support.

[NH]

Dear Jatzoo, other knowledgeable folks on the topic

Many thanks for your detailed instructions on installing JRiver in docker. I have managed to install.

However I am not able to get inside JRiver to complete the settings. I have tried realvnc viewer, tightvnc and putty.

I had pointed it to port 32769 on the IP address of the QNAP NAS which was the port assigned during set up. I get a message "connection closed unexpectedly" or "connection gracefully closed" (tightVNC!).

Is it some settings in QNAP that is preventing this access?

Best

NH

Best

Will be grateful for your advice

[NH]

Dear Jatzoo, other knowledgeable folks on the topic

Many thanks for your detailed instructions on installing JRiver in docker. I have managed to install.

However I am not able to get inside JRiver to complete the settings. I have tried realvnc viewer, tightvnc and putty.

I had pointed it to port 32769 on the IP address of the QNAP NAS which was the port assigned during set up. I get a message "connection closed unexpectedly" or "connection gracefully closed" (tightVNC!).

Is it some settings in QNAP that is preventing this access?

Best

NH

Best

Will be grateful for your advice

Further, wanted to check what is the reason that when you access the port you are led to the MC panel, not the standard MC interfacet that you see on Windows. If one were to land there, there is no need for a VNC server to do the settings. For example, I have seen the way SongKong has created their docker image, which when I followed the step by step instructions and you go to port number 4567, you see exactly the same screens as you would see on a Windows desktop. It was done in 5 mins! There was no need for any VNC etc to do the settings and didnt need any other knowledge. Any of you can check it out here. http://www.jthink.net/songkong/install_docker_qnap.jsp

If this is possible at all (and you are the expert!) this would make it very simple.  And all QNAP users would be very grateful.

The option of keeping a PC running all the time with MC on is not working out for me and since the NAS runs all the time, this way I would be able to access it as a player also. Else I am only able to use it for editing, music management etc but not really for playng. I end up using minimserver and bubbleupnp to stream it to my ethernet DAC.

Best

NH

[Jatzoo]

@NH, what is Your configuration for point 5 from this instruction:
https://yabb.jriver.com/interact/index.php/topic,115841.msg821370.html#msg821370

PS. You must use VNC to log-in to MC and configure it on the server side (Qnap). If You don't want to do it in this way, there are some other docker images where GUI MC can be accessed via web browser.

[NH]

@NH, what is Your configuration for point 5 from this instruction:
https://yabb.jriver.com/interact/index.php/topic,115841.msg821370.html#msg821370

Thanks Jatzoo. The configuration I have is what you have shown under NAT. It doesnt allow me to use Host networking.

What I see on the overview screen as URL is http://10.X.X.X:32787/ -> 52199. Still cant access through VNC.

Tried Bridge networking also - same result.

On the access via web gui, if that's easier, will be grateful if you tell me which ones I can use. Will check them out.

Best

NH

[Jatzoo]

In Host networking - it doesn't allow or only warning about possible of mapping conflicts? If I set host, I see warning but all works great.

For web GUI try for example Shiomax images: https://hub.docker.com/u/shiomax.