Was installing RoonServer on my ReadyNAS 524X and all was going swimmingly until the install started. The script appears to have failed due to an expired certificate on download.roonlabs.net (see below and advise - THANK YOU!
Do you want to install RoonServer on this machine? [Y/n] Y
Downloading RoonServer_linuxx64.tar.bz2 to /tmp/tmp.KhywIeDSQz/RoonServer_linuxx64.tar.bz2
--2024-02-23 12:01:26-- https://download.roonlabs.net/builds/RoonServer_linuxx64.tar.bz2 Resolving download.roonlabs.net (download.roonlabs.net)... 172.67.14.113, 104.22.14.70, 104.22.15.70, ... Connecting to download.roonlabs.net (download.roonlabs.net)|172.67.14.113|:443... connected. ERROR: The certificate of ‘download.roonlabs.net’ is not trusted. ERROR: The certificate of ‘download.roonlabs.net’ has expired.
Installing RoonServer on a Netgear ReadyNAS 524X (using the excellent doc found here). Everything was going swimmingly - the installer asked if I wanted to install RoonServer on this machine, I replied "Y" and the script failed in the following fashion:
No issue here downloading the file from the link above from my desktop computer with Firefox browser.
No complaints about the certificate (and I had those in the past with Firefox and expired certificates on Roon sites).
Are you sure the current time and time zone are set correctly on your NAS?
If you can download the package from your desktop and move it to the NAS, then you can follow the manual install steps from the guide to finish the installation too.
EDIT: I see the manual install is probably not gonna work for inexperienced users. I’m also unsure how/why a direct install on a NAS Linux should work. For other NAS platforms a package is needed to provide an environment for Roon to run in safely and that ensures everything Roon needs is available and where Roon expects it to be.
I’m getting the same cert error running the easy/quick installer.
I’m having to rebuild an old vortexbox 2.4 build - fedora 23 I think, due to a motherboard failure. I have had roon server running on VB 2.4 for years with no issues, last install would have been ~2 years ago. Yeah the OS is old, but I love the vortexbox backup function, saved my bacon more than once,
The RoonServer installer did not complete successfully.
I have tried the manual install method, check.sh is all green - passed, all dependencies are installed as per the docs, and even ca-certificated is already installed. If I run start.sh things seem to be running, but I can’t query RoonServer with systemctl, also can’t log in from any roon remote. tbh, I am not advanced linux enough to get roon to auto start and stop.
Any ideas to get the auto installer working?
I tried to edit the curl command to add -k which should ignore certs, but I get the same error.
fyi, I did successfully install the OS and data disk in my new Core hardware and it worked, but lots of errors on shutdown and weird hangs, so decided to rebuild from scratch.
I think you should have edited the wget command instead (AFAIK is –no-check-certificate a wget option).
The start/stop script gets generated from the easy installer script so the content is there, inside the script, but you have to replace the variables used with the actual values yourself if you can’t use the script – but maybe you can with the added option for the right command (see above)?
All this different pieces of information do make it impossible (for me at least) to understand how/what you are currently dealing with. So please include a proper system description (including OS/distribution information) in an attempt to help helpers trying to help you if you need further help.
The issue here is that we are using an SSL certificate chain which is reliant on a relatively recent CA (certificate authority). In order for SSL to work your computer needs to have a list of trusted CAs and the lists on these operating systems are woefully out of date.
When the script attempts to fetch the download from our server it fails because the operating system doesn’t have updated CA information. This is usually provided as part of a regular operating system update, but in the world of Linux devices the delivery mechanism and cadence is all over the map.
Long and short is that you need to look to your OS provider for an update. This isn’t an issue with Roon or our install script. It’s a problem with the operating system on your server.
