More > JRiver Media Center 26 for Linux
Docker Container for JRiver Media Center 26
Robad:
Yes I have read it. But I still can't get it to work.
I have tried port-forwarding on port 52199 to the Container IP (192.168.1.236) and to the QNAP IP (192.168.1.250). (Though not at the same time...) Both allow me to access the MC26 UI from my PC's browser at http://192.168.1.236:5800/.
I'm obviously using an "Access Key", so why would I care what my external IP address is??
"This key is automatically generated by JRiver's servers. It is associated with two IP addresses. One is for your server, as seen from inside your network (local), and the other is your outside address (Internet)."
Mind you, I'm intrigued as to how MC26 tells me what the Access Key is if the access test fails, presumably meaning JRiver's servers can't access MC26...
BryanC:
Use host networking mode until you can get that sorted out. You've got too many variables in play right now for people to help you without just shooting in the dark.
To re-state:
1. You need to enable port forwarding on your gateway device (router) from port 52199 to port 52199 to...
* In network host mode, you would forward to your device IP
* In network bridge mode, you would forward to the container IP
Host mode is easier to diagnose because bridge mode requires a bunch of security contexts that are OS-dependent (e.g.):
--- Quote ---By default, traffic from containers connected to the default bridge network is not forwarded to the outside world. To enable forwarding, you need to change two settings. These are not Docker commands and they affect the Docker host’s kernel.
Configure the Linux kernel to allow IP forwarding.
$ sysctl net.ipv4.conf.all.forwarding=1
Change the policy for the iptables FORWARD policy from DROP to ACCEPT.
$ sudo iptables -P FORWARD ACCEPT
--- End quote ---
I'm not familiar with QNAP software, so I don't know how they handle this.
Either way, you will need to assign a manual IP address to the appropriate container/device by MAC so that port forwarding will work.
2. In host mode you will need to use the software firewall port on your device to allow port TCP/52199. Again, I don't know if QNAP handles this automatically or not.
Robad:
Thanks for the reply.
When I change the container network mode to "Host" I get the following:
"The port may conflict with the NAS port when selecting Host mode.
Use local host network (command: --net=host)
Note：This option allows containers to have full access to the host network interface."
I have no idea what this bit means: "Use local host network (command: --net=host)"
The operation fails with this:
"Failed to apply container settings.
Error Code: 500
Message: 400 Client Error: Bad Request ("conflicting options: mac-address and the network mode")"
BryanC:
--- Quote from: Robad on July 04, 2020, 08:30:53 am ---Thanks for the reply.
When I change the container network mode to "Host" I get the following:
"The port may conflict with the NAS port when selecting Host mode.
Use local host network (command: --net=host)
Note：This option allows containers to have full access to the host network interface."
I have no idea what this bit means: "Use local host network (command: --net=host)"
The operation fails with this:
"Failed to apply container settings.
Error Code: 500
Message: 400 Client Error: Bad Request ("conflicting options: mac-address and the network mode")"
--- End quote ---
This is sounding a lot like a question for QNAP. --net=host is just a docker command line option to enable host networking mode for the container. Presumably QNAP would stop and restart the container with the new settings, but maybe it needs it to be configured at runtime.
Perhaps try disabling the container before changing these settings, or you may need to recreate the container with fresh settings. It sounds like the functionality to dynamically change the network mode exposed by the QNAP software is broken (or maybe this is featured in their docs).
Robad:
I think I'm going to give up. I've tried everything I can think of, including:
- Changing network mode to 'Host'
- Changing back to NAT (as I had to create the container as 'NAT', this being the only way to specify a MAC address).
- Changing back to 'Bridge' with same IP as QNAP.
- I even searched for a container configuration file (and failed to find it)... It would be so much easier to edit such a file, if it exists.
Everything either has no effect or makes it worse, leaving me to work out how to recover.
:'(
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version