More > JRiver Media Center 30 for Linux

Docker Images for MC30 (current one + a new image with arm builds)

<< < (2/4) > >>

Scobie:
Yep understood thanks Max. Appreciate your work on the Container version.

Richard Martin:
I couldn't find it searching from the docker app on my Synology NAS, but that also allows you to enter the URL.  Doing that worked and I have 30 up and running.

Scobie:
Looks as if this is resolved Max, your MC30 image now showing up in searches.

res80:
Thanks for those excellent docker images, makes running MC even easier than before (running bare metal).
But I ran into one problem:
I am using nginx as reverse proxy for all my browser-based applications.
E.g. JRiver panel is accessible via https://music.mydomain.com, using letsencrypt certificates.
Nginx and letsencrypt are running directly on the host server, no docker involved. Docker is running in network host mode, so no port rules have to be defined.
However, when I tried to the WebGUI to https://music.mydomain.com/admin/, webgui is not working.
I can see the novnc status bar on top, but next to the title it shows loading for a while and then failed.
Internal access with machine.local:5800 works ok, even from different machines within the same LAN, so no firewall issue?
Any ideas?
Thanks a lot,
Ruediger

max096:
Websockify runs over a websocket connection not http so you need a seperate block for that with different settings to have novnc work.

This is the nginx http config the new images are using.

https://gitlab.com/shiomax/jrivermc-docker-next/-/blob/main/rootfs/etc/nginx/sites-available/http_config

Hope that helps. i think replacing the / block with the contents of /api (you should be able to merge the two) and replacing the urls with the container ip should give you a working base config you can add your cert to.

Not sure about the other image right off the bat. Gotta dig up where jlesage put websockify in the base image. Can try to get it working when I get home tomorrow but I think you can probably figure that out too since it sounds like you otherwise already know your way around nginx. You should also see the url pop up in your browsers debug window in the networking tab. Might very well also be /websockify but im not sure right now.

Navigation

[0] Message Index

[#] Next page

[*] Previous page