Virtualmin Installation Error ( "slib.sh error")

Submitted by krinz on Fri, 08/31/2018 - 07:46

Hello,

While Installing the standard SCRIPT of virtualmin. We are facing the below issue.

root@vps202774:~# ll

  • total 72
  • drwx------ 6 root root 4096 Aug 31 08:35 ./
  • drwxr-xr-x 23 root root 4096 Aug 31 07:27 ../
  • -rw-r--r-- 1 root root 0 Aug 31 07:28 .bash_history
  • -rw-r--r-- 1 root root 3106 Oct 22 2015 .bashrc
  • drwx------ 2 root root 4096 Aug 31 07:24 .cache/
  • drwx------ 2 root root 4096 Aug 31 07:24 .gnupg/
  • -rw-r--r-- 1 root root 31327 Aug 31 08:37 install.sh
  • drwxr-xr-x 2 root root 4096 Aug 31 08:34 .nano/
  • -rw-r--r-- 1 root root 148 Aug 17 2015 .profile
  • drwx------ 2 root root 4096 Aug 31 07:28 .ssh/
  • -rw------- 1 root root 711 Aug 31 08:34 .viminfo
  • -rw-r--r-- 1 root root 1977 Aug 31 08:37 virtualmin-install.log

root@vps202774:~# sh install.sh

  • chmod: cannot access 'slib.sh': No such file or directory
  • install.sh: 288: .: Can't open ./slib.sh

root@vps202774:~#

Here when i went to the Line number 288 i found the below issue.

Efforts Made : I downloaded the "slib.sh" file in my system uploaded it into another secure host & put that in the script & re-run it but still not able to install Virtualmin.

Suggest the way to fix it.

Warm Regards

Status: 
Closed (fixed)
Files: 
Image icon slib_issue.png

Comments

Submitted by krinz on Fri, 08/31/2018 - 07:59

Suggest the best way to solve it.

Submitted by andreychek on Fri, 08/31/2018 - 08:06

Assigned: Unassigned »

Thanks for the letting us know, and for the good detective work!

I've let Joe know so he can look into this.

As a temporary workaround, you may just want to change that URL from "https" to "http" to get it to work, but Joe should have all that resolved a bit later today.

Submitted by Bilt on Sat, 09/01/2018 - 06:58

Thanks for looking into this. It's giving me a pain in the neck too.

Changing to 'http', or using "--no-check-certificate", is not a temporary workaround, I'm afraid. You still end with the "slib.sh" error.

Submitted by andreychek on Sat, 09/01/2018 - 10:54

Are you still seeing this issue?

Joe had updated the SSL cert, it should no longer be expired.

Submitted by Bilt on Sat, 09/01/2018 - 12:11

Yes, still seeing a problem with the ssl cert. Here's my terminal response just a minute ago.

$ wget https://software.virtualmin.com/gpl/scripts/install.sh --2018-09-01 16:59:43-- https://software.virtualmin.com/gpl/scripts/install.sh Resolving software.virtualmin.com (software.virtualmin.com)... 149.28.242.101, 163.172.162.254 Connecting to software.virtualmin.com (software.virtualmin.com)|149.28.242.101|:443... connected. ERROR: cannot verify software.virtualmin.com's certificate, issued by ‘CN=Let's Encrypt Authority X3,O=Let's Encrypt,C=US’: Unable to locally verify the issuer's authority. To connect to software.virtualmin.com insecurely, use `--no-check-certificate'

But after you use the "--no-check-certificate" workaround or use http in place of https I still end up with the "./slib.sh" error

Joe's picture
Submitted by Joe on Sat, 09/01/2018 - 12:38 Pro Licensee

I can't figure this one out. The certificate on that server is valid for me. It was expired for about a day because I screwed up the mirror setup when I added a new mirror and an old one went offline...but, it should be fixed now.

You could change all of the https links to http in install.sh, which would get past that particular problem, but yum won't be able to install packages either, as long as an invalid certificate is coming your way. But, I'm utterly baffled where it's coming from...when I hit that specific server (forcing the IP in my hosts file), I get a valid certificate.

But, weirdly, that error kinda looks like it doesn't like that it's a Let's Encrypt certificate, rather than that it is expired. That's not something I've seen. I'll have to check on an Ubuntu 16.04 server, maybe the wget there has an old issuer list or something weird. I dunno. Surely they support Let's Encrypt certificates. Maybe try making sure your system is up to date?

Submitted by Bilt on Sat, 09/01/2018 - 13:26

Thanks for your work, Joe. I'm using Ubuntu 16.04.5 LTS. I think that the issue has arisen in the last few days because I spun up a Virtualmin instance on the 27th without a problem.

I'll have a go at changing all the httpses.

Submitted by kahs on Sun, 09/02/2018 - 14:33

Downloading RPM-GPG-KEY-virtualmin-6 [ERROR] Failed with error: 60 [ ✘ ]

[ERROR] Something went wrong. Exiting. [ERROR] The last few log entries were: [2018-09-02 19:10:04 UTC] [DEBUG] install.sh version: 6.0.12 [2018-09-02 19:10:04 UTC] [DEBUG] Checking for fully qualified hostname... [2018-09-02 19:10:04 UTC] [DEBUG] Hostname OK: fully qualified as gtwebreports.gtwebreports.co.uk [2018-09-02 19:10:04 UTC] [DEBUG] Installing serial number and license key into /etc/virtualmin-license [2018-09-02 19:10:04 UTC] [DEBUG] Operating system name: Ubuntu [2018-09-02 19:10:04 UTC] [DEBUG] Operating system version: 18.04 [2018-09-02 19:10:04 UTC] [DEBUG] Operating system type: ubuntu [2018-09-02 19:10:04 UTC] [DEBUG] Operating system major: 18 [2018-09-02 19:10:04 UTC] [DEBUG] Configuring package manager for Ubuntu 18.04... [2018-09-02 19:10:04 UTC] [DEBUG] apt-get repos: virtualmin-bionic virtualmin-universal [2018-09-02 19:10:04 UTC] [DEBUG] Installing Webmin and Virtualmin package signing keys... Spin pid is: 1737 Downloading RPM-GPG-KEY-virtualmin-6: [2018-09-02 19:10:05 UTC] [ERROR] Failed with error: 60 [2018-09-02 19:10:05 UTC] [ERROR] Something went wrong. Exiting. [2018-09-02 19:10:05 UTC] [ERROR] The last few log entries were:

ive tried on both ubuntu 16.04 / 18.04 lts and still the same error any help would be appreciated thanks

Joe's picture
Submitted by Joe on Sun, 09/02/2018 - 17:53 Pro Licensee

I was missing an SSLCACertificateFile directive on the new mirror (I can't understand why this didn't trigger any errors for me on any of my clients, but did for some folks installing, though!).

Fixed now.

Submitted by andreychek on Tue, 09/04/2018 - 09:44

Joe just fixed this yesterday (the timestamp on his comment where he said he fixed it is Sunday evening).

I'm going to keep this marked as closed unless anyone is seeing an issue today.

Submitted by Bilt on Tue, 09/04/2018 - 13:08

Yes worked for me now. Thanks for fixing it.

Submitted by lhdyjwxfai on Tue, 01/01/2019 - 12:30

How can I deal with this problem? I have the same problem today.

Submitted by cleronx@gmail.com on Mon, 01/07/2019 - 10:19

Im having the same problem January 7, 2019 is there any other wy to install this. im installing on the newest version of Centos 7

Submitted by ethernutza on Sat, 07/06/2019 - 10:15

I am having the same issue.

Submitted by andreychek on Sat, 07/06/2019 - 10:22

We've seen some strange issues on certain distros with curl... could you temporarily try renaming curl to something else, and then see if the installation works successfully?

With curl renamed, it'll fall back to wget, which has typically worked.

Just try something like this:

mv /usr/bin/curl /usr/bin/curl.orig

And you can rename curl back to the original name once the installation is finished.

Joe's picture
Submitted by Joe on Sat, 07/06/2019 - 18:00 Pro Licensee

It defaults to wget if it's installed. I'm pretty sure I changed it last time this came up. Though I don't understand why it's happening again...I fixed the root cause of the problem, but maybe the cert on one of the mirrors has expired and didn't sync up as it's supposed to (though I would think that would have a different error).

I'm looking into it.

Joe's picture
Submitted by Joe on Sat, 07/06/2019 - 18:08 Pro Licensee

OK, after looking at the certificates and doing some testing, this is a different problem than the one this issue was opened about, and any workarounds we discussed or whatever in the past will not apply to your issue.

Can you open a new ticket with the specific errors you see, ethernutza? Please include the OS/version you're installing on in the ticket.

Joe's picture
Submitted by Joe on Sat, 07/06/2019 - 18:08 Pro Licensee

Closing this ticket again, as the newly reported issue is something different (with maybe similar symptoms).