More > JRiver Media Center 30 for Linux
Docker Images for MC30 (current one + a new image with arm builds)
Afrosheen:
Thank you again Max for continuing to keep the docker image of MC up to date. I just wish to know if there will be the option to authenticate the Last.FM service down the line? For me it's the last remaining feature yet to be implemented in the Docker version of MC. It's a niche request so forgive me for requesting it. Thanks again for the consideration! I hope you have a great start to your new year!
max096:
--- Quote from: Afrosheen on January 01, 2023, 06:00:45 am ---Thank you again Max for continuing to keep the docker image of MC up to date. I just wish to know if there will be the option to authenticate the Last.FM service down the line? For me it's the last remaining feature yet to be implemented in the Docker version of MC. It's a niche request so forgive me for requesting it. Thanks again for the consideration! I hope you have a great start to your new year!
--- End quote ---
I think you can edit this file "~/.jriver/Media Center 30/Settings/User Settings.ini" and fill out "Last.fm - Session Key" "Last.fm - Username" in the container under "/config/.jriver/Media Center 30/Settings/User Settings.ini" with what you got after logging in on another mc instance where it works.
--- Code: ---Last.fm - Session Key="<Your Session Key>"
Last.fm - Subscriber=i:"0"
Last.fm - Username="<Your Username>"
--- End code ---
Installing a standalone browser isnīt quite enough. It works for other stuff like the twitter connect thing and the last fm profile (once there is something configured) but it does not for connecting with last fm. Appears to be working for me by manually editing the file, however it does not work over media network it only works if you actually play files with that docker container (which is probably how that feature is supposed to work though).
Afrosheen:
Thank you max! I'll check it out when I get the chance to dive deep into this!
--- Quote from: res80 on December 31, 2022, 03:41:00 pm ---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.
--- End quote ---
After reading this, I'm intrigued at getting nginx for https support, and am wondering if you could point me at how you got started. Would you know of any good places that would provide a tutorial on setting this up on a NAS?
max096:
--- Quote from: res80 on December 31, 2022, 03:41:00 pm ---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
--- End quote ---
Tried it now using this configuration it works fine.
--- Code: ---upstream mediacenter {
# Docker container running mediacenter
server 127.0.0.1:5800;
}
# Redirect HTTP connections to HTTPS
#server {
# listen 80;
# listen [::]:80;
# return 301 https://$host$request_uri;
#}
server {
listen 443 ssl;
ssl_certificate /path/to/cert;
ssl_certificate_key /path/to/private_key;
location / {
proxy_pass http://mediacenter;
proxy_http_version 1.1;
}
location /api {
proxy_pass http://mediacenter;
proxy_http_version 1.1;
proxy_set_header Upgraded $http_upgrade;
proxy_set_header Connection keep-alive;
proxy_set_header Host $host;
proxy_cache_bypass $http_upgrade;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
location /websockify {
proxy_pass http://mediacenter;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "Upgrade";
proxy_set_header Host $host;
# VNC connection timeout
proxy_read_timeout 61s;
# Disable cache
proxy_buffering off;
}
}
--- End code ---
max096:
--- Quote from: Afrosheen on January 02, 2023, 02:24:28 pm ---After reading this, I'm intrigued at getting nginx for https support, and am wondering if you could point me at how you got started. Would you know of any good places that would provide a tutorial on setting this up on a NAS?
--- End quote ---
If you just want to have SSL for this container itīs enough to set SECURE_CONNECTION to 1. If you want to setup a common reverse proxy to put multiple services behind and manage SSL certs centrally then you gotta setup your own.
There are plenty of guides out there on how to do this in detail. But tldr; you can either, like the container does generate a self signed certificate (works for domain names you made up or IPs) or you can purchase a domain name and then lets encrypt can issue you a trusted certificate for free for said domain. Letsencrypt has made a tool they named certbot that you should run on a schedule as the lifetime of the certificates they give you is only 3 months. Use a similar NGINX config as the one above. If you wanna generate a self signed cert you can use a command such as this.
--- Code: ---openssl req \
-x509 \
-nodes \
-days 365 \
-newkey rsa:2048 \
-subj "/C=CA/O=example.com/OU=Home/CN=noreply.example.com" \
-keyout $CERT_DIR/privkey.pem \
-out $CERT_DIR/fullchain.pem
--- End code ---
Like I said it really should not be hard to find a lot of guides about this everywhere that go into a lot more detail. I donīt have a specific one to recommend though. The digitalocean guides are quite good https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-debian-11. But Iīm not sure they are if you are unfamiliar with the subject since Iīve done this before and I just donīt read any of the guides anymore about this. I do go there sometimes, but just use them as a cheatsheet to copy the commands I know I need. Their DNS servers are also free of charge with great UI, with an API with great documentation. So, if you did not get access to one with your domain purchase, or donīt like it then you can use theirs.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version