virtualmin installation seems to get stuck

12 posts / 0 new
Last post
#1 Wed, 05/15/2013 - 20:10

virtualmin installation seems to get stuck

hi - i am trying to do a new installation, and i keep getting stuck:

INFO -  Succeeded.
INFO - Installing dependencies using command: /usr/bin/yum -y -d 2 install bind bind-utils caching-
blah blah blah blah
INFO -  Succeeded.
INFO - Installing Virtualmin and all related packages now using the command:
INFO - yum clean all
Loaded plugins: fastestmirror
Cleaning repos: base epel extras updates virtualmin virtualmin-universal
Cleaning up Everything
Cleaning up list of fastest mirrors
INFO - yum -y -d 2 install virtualmin-base progress, please wait...  

we don't progress past this point. we are stuck!

i could at this point enter a control-C and manually enter:

yum -y -d 2 install virtualmin-base ;

but first i wanted to ask one of you wizards why we might be stuck here.

below are the bash commands i use to install virtualmin/webmin:

###install webmin:
mkdir   ~/webmin  &&  cd  ~/webmin ;
wget  ;
gzip -d  webmin*  &&   tar -xvf  webmin*  &&  cd  webmin* ;
./ ;
##install virtualmin:
curl   > ;
 chmod 755   ./  ;
./  ;
Wed, 05/15/2013 - 22:23

scratch this one... it finally finished after several hours. i don't think i ever saw an install take quite that long !

Wed, 07/22/2015 - 03:23 (Reply to #2)

Nevermind. My problem was not fixed. heh.... sorry

Fri, 07/12/2013 - 10:38

I have the same problem. It is stuck on this for more than 45 min now ...

INFO - yum -y -d 2 install virtualmin-base progress, please wait... 

It is not my first install of virtualmin and all previous installs were very quick ...

I don't know why it's so long now.

Sun, 08/04/2013 - 01:10

Might be a network/internet issue, causing extreme delays when accessing the repository servers?

Wed, 10/23/2013 - 20:52

Hitting the same issue here.

I am using '' as hostname, however wanted to point it to the new server's IP address after I have installed Virtualmin and migrated the website.

Might this be because hostname on the server still points elsewhere?

Edit: The process has completed in about 1 hour. So just wait and do not interrupt it.

Fri, 01/17/2014 - 03:04

I was having this same issue. It was a brand new VPS and I tried rebuilding the server a couple of times to start it again; I waited over 8 hours at one point. I then, purely by chance visited myserver:10000 after rebuilding the server and realise that my hosting provider was pre-installing Webmin. I removed Webmin and then ran the install and it took less than 2 minutes :)

Fri, 01/09/2015 - 11:57

In my case, I've been waiting for 1hr by now. No luck to see that desperate :10000. Guess I won't even since I'm trying to install in a dedicated ip instead of I have not pointed my domain to this vps yet.

Any clues if I will succeed ?

Sun, 01/11/2015 - 00:24
tpnsolutions's picture


Make sure you don't have any extra repos enabled. In the original posters message I can see they had "epel" repo enabled which has been known to cause problems.

Also try pinging and tracerouting "" if the issue is related to Virtualmin's repo. Perhaps the server is under heavy load when you are installing or is having issues which need to be looked into.

Best Regards,
Peter Knowles
TPN Solutions

Phone: 604-782-9342
Skype: tpnsupport
Best Regards,
Peter Knowles | TPN Solutions
Email: | Skype: tpnassist
Mon, 11/16/2015 - 16:45

'lo all,

Same problem on Centos 7 (64bit).

Originally, I halted the setup, and re-ran the script. The installation detected something was not right and I believe 'uninstalled' something. I then re-ran it installed quickly with no problems.

However...I found down the line that many aspects of the install were not finished, including my postfix and procmail services. I'm not sure if this is due to using CentOS 7 but I'll find out now. I have wiped my box fresh and going to wait for the install to complete.

Mon, 11/16/2015 - 17:12


If you continue to have problems, could you attach your /root/virtualmin-install.log file? That may help us determine what's wrong.



Mon, 11/16/2015 - 17:35


Thanks. I think it was a slow network, as this time it took maybe 5-10 minutes finishing up. I would suggest to anyone to not cancel the installation script, even if it takes 24 hours.

I should have got the log before wiping.

Thanks, Changos

Topic locked