More > JRiver Media Center 32 for Linux
Docker Images for MC32
HaWi:
I installed MC32 on the Pi5 (running 64 bit Bookworm/Xfce) in bridge mode but I must have a permission problem because when I try to VNC into the container I get "The connection was refused by the computer" error.
I'll do some research to see if I can fix that.
max096:
--- Quote from: HaWi on February 12, 2024, 12:25:11 pm ---I installed MC32 on the Pi5 (running 64 bit Bookworm/Xfce) in bridge mode but I must have a permission problem because when I try to VNC into the container I get "The connection was refused by the computer" error.
I'll do some research to see if I can fix that.
--- End quote ---
If you´re using bridge networking you need to set it to ALLOW_ALL. Because the container has its own localhost then, so restricting connections to localhost will make it so you can only connect from inside the container. Which isn´t all that straight forward to accomplish.
HaWi:
--- Quote from: max096 on February 12, 2024, 06:17:22 pm ---If you´re using bridge networking you need to set it to ALLOW_ALL. Because the container has its own localhost then, so restricting connections to localhost will make it so you can only connect from inside the container. Which isn´t all that straight forward to accomplish.
--- End quote ---
Thanks Max, I have ALLOW_ALL in my yaml but can't get into the container with VNC. No problem, though, I got native MC32 running rather quickly so I will probably not use the docker container on the pi5.
HaWi:
I have tried to update to MC 32.0.23 on my Synology DS1918+ using docker-compose pulling this image
shiomax/jrivermc:latest-32.0.23-v0.4.4
the container runs, according to the container manager and Portainer but when I try to access via VNC I get this error
The connection closed unexpectedly.
It's probably a Synology problem but I am stumped.
Would very much appreciate any ideas/hints on how to solve this.
max096:
--- Quote from: HaWi on March 09, 2024, 12:27:20 pm ---I have tried to update to MC 32.0.23 on my Synology DS1918+ using docker-compose pulling this image
shiomax/jrivermc:latest-32.0.23-v0.4.4
the container runs, according to the container manager and Portainer but when I try to access via VNC I get this error
The connection closed unexpectedly.
It's probably a Synology problem but I am stumped.
Would very much appreciate any ideas/hints on how to solve this.
--- End quote ---
Not sure, just tried. This works with the latest image. Both web and vnc. It worked before? Try to restart the system if you did not yet. Might just fix it.
Otherwise, there are logs for tigervnc in /log/tigervnc. The file 'current' contains the latest logs.
The following will follow the logs live in your terminal
--- Code: ---docker exec -it <container_name or id> /bin/bash
root@stuffs:/tmp# cd /log/tigervnc/
root@stuffs:/log/tigervnc# tail -f current
--- End code ---
Then you can try to connect to it and see if any errors pop up. If nothing comes up at all you´ve got some networking issue and don´t even make it to the container. Port 5900 has to be accessable and you have to have ALLOW_ALL set to be able to connect from other systems.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version