More > JRiver Media Center 23 for Windows
NEW: HTTPS/SSL support for Library Server, MCWS, WebGizmo and Panel
Hendrik:
Updates for mobile clients will be coming a bit later. Probably Android first, unless someone beats me to it. ;)
Obviously server support had to be the first, and MC client support is just relatively easy (even if a bit wasted for something most people likely only use locally).
hoyt:
This alone is a huge step for MC23. Glad to see it be incorporated, looking forward to seeing the change in JRemote :)
Thanks!
WeeHappyPixie:
Any plans to support LetsEncrypt, this way we get a free SSL certificate that browsers don't moan about.
AndrewFG:
--- Quote from: WeeHappyPixie on June 24, 2017, 02:34:24 pm ---Any plans to support LetsEncrypt, this way we get a free SSL certificate that browsers don't moan about.
--- End quote ---
It's probably not that easy. I have done a few tests on Let's encrypt, and currently it only works with sites that have a registered domain name; but it won't help you at all with sites using an IP address (like 192.168.1.xxx). (And IMHO nor should it).
Basically cert validation depends (at least partly) in proving a binding between a domain and a cert..
mwillems:
--- Quote from: AndrewFG on July 14, 2017, 09:13:55 am ---It's probably not that easy. I have done a few tests on Let's encrypt, and currently it only works with sites that have a registered domain name; but it won't help you at all with sites using an IP address (like 192.168.1.xxx). (And IMHO nor should it).
Basically cert validation depends (at least partly) in proving a binding between a domain and a cert..
--- End quote ---
Assuming you've got a domain name and a letsencrypt cert, the certs can be made to work with no browser complaints with local IPs as well provided you're willing to setup split DNS on your router (and that your router supports it). Basically use your router as your DNS cache (which is often the default configuration, and has a lot of other potential advantages), and then configure your router to resolve the domain name in question to a local address when traffic originates inside the LAN, etc. I've been doing that for about a year with other services and it works great (no browser complaints).
Obviously not trivial to set up even if you've got everything already working with LetsEncrypt, but possible with some elbow grease. Automating letsencrypt for most home users is not likely to be viable; much easier for most people to just to set your self-signed cert to trusted in your and your families browsers.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version