Running Virtualmin install script fails

Yes, it’s possible. For example, a user might right-click and copy an installation link where & is escaped as \&. If that link is opened in a browser, the script could end up with serial written as SERIAL=123456\, which is wrong. That link was meant for the Terminal use with wget or curl.

This is the most likely reason it didn’t work.

@jaldeguer, please open install.sh and check line 11—if the serial ends with a backslash, that explains it.


No worries, I’ve updated install.cgi on our server to always return clean serial and key values.

What is in your /etc/netplan?

That shouldn’t matter for installation? We don’t touch the network configuration during installation (or ever, generally).

The simplest solution might be for y’all to treat both as valid :blush:

The better approach is to always write the correct key and serial in the installation script.

Success!

Indeed, It turns out that copying and pasting the script into Hostinger’s terminal browser was introducing some strange hidden characters, which caused the installation to fail, even after I tried pasting it into TextEdit on my Mac as plain text.

To avoid that issue, I uploaded the updated virtualmin-install.sh file directly to a fresh Hostinger VPS using scp and ran the script there. This time, it ran perfectly without a hitch!

Thank you, everyone, for your help!

1 Like

That’s a weird one. I find those terminals so obnoxious the first thing I do is set up my ssh keys and go to a terminal window. Isn’t this an option on Macs? I know Windows is a separate program like Putty.

I also never really liked those browser SSL terminals either, but Hostinger made it work really smoothly.

Anyway, the original problem is fixed now.

Yeah, just one of those little trouble shooting things that may never come up again, but… :wink:

@ID10T
Windows 10 1809 > have SSH Client And Server :+1:

This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.