In addition, existing install.sh copies return 500 errors when they are used to install - the stuff they are downloading from virtualmin repo return 500 error.
I can confirm this. When I couldn’t download the install script, I thought I’d get around it by just copying it over from another server I had, but once I ran install.sh, I got …
http://software.virtualmin.com/lib/spinner:
2016-02-16 23:31:48 ERROR 500: Internal Server Error.
chmod: cannot access ‘spinner’: No such file or directory
Loading log4sh logging library… http://software.virtualmin.com/lib/log4sh:
2016-02-16 23:31:48 ERROR 500: Internal Server Error.
Could not load logging library from software.virtualmin.com. Cannot continue.
We’re not just stopping because we don’t have a logging library–this probably
indicates a serious problem that will prevent successful installation anyway.
Check network connectivity, name resolution and disk space and try again.
Oh well, I look forward to it being fixed tomorrow and continuing with another Virtualmin install.
Exactly the same issue at this time on a freshly installed server with Debian 8.3 (internet connectivity and DNS resolving is OK) :
Checking for HTTP client…found /usr/bin/wget -nv
Checking for perl…found /usr/bin/perl http://software.virtualmin.com/lib/spinner:
2016-03-14 10:57:13 ERROR 500: Internal Server Error.
chmod: cannot access ‘spinner’: No such file or directory
Loading log4sh logging library… http://software.virtualmin.com/lib/log4sh:
2016-03-14 10:57:13 ERROR 500: Internal Server Error.
Could not load logging library from software.virtualmin.com. Cannot continue.
We’re not just stopping because we don’t have a logging library–this probably
indicates a serious problem that will prevent successful installation anyway.
Check network connectivity, name resolution and disk space and try again.