Installing Virtualmin AFTER webmin installed

8 posts / 0 new
Last post
#1 Sat, 08/10/2019 - 04:42

Installing Virtualmin AFTER webmin installed

Hello all..

I have some simple questions.

I have opened a VPS instance on where there is an opetion to get a pre-installed webmin instance - so for sake of testing and time saving i thought i would try it.

After a short time I have accessed the installed server and then I saw that the instance has only webmin, and not virtualmin,

I then installed the Apache RPM through the interface just for testing and all seems to worked just fine .

Then in order to get the virtualmin I downloaded the # wget and run it.

My questions are as follow :

1 - Is that a correct procedure ? Is there another way to install virtualmin once a server with only webmin is installed ?

2 - If I go now to Virtualmin - > recheck configuration it shows me a message in red " .. your system is not ready for use by Virtualmin." - what does that mean ?

3 - ( slightly unrelated ) How to control the naming ( mainly users ) if I have a, samedomain.gtld ? it seems like the first one I will use will get the samedomain as name, and all the others later will produce one kind of an error....

4- regarding the apache / php installation i mentioned before - virtualmin gave me few options like cgi, su-exe, etc.. which one should I choose ?

Thanks for all the help in advance ..

Sat, 08/10/2019 - 09:15

what's the exact message in red?

Sat, 08/10/2019 - 17:40
RJM Web Design
RJM Web Design's picture

With regard to the same domain names with different TLD's, what are you trying to do exactly? If you're trying to "park" all except one on that one exception (for example, example.tld0, example.tld1, and example.tld2 -> example.tld3), then what you're looking for is in "Create Virtual Server / Alias of [existing server]". Obviously, the virtual server you want all of the domains to open on should be the first one you create.


Sat, 08/10/2019 - 20:21

Thanks all for the replies .

@suskozaver - the exact message in red is exactly what I wrote above : " .. your system is not ready for use by Virtualmin." .

@RJM Web Design - Yes, I understand the workflow, but the problem is with the usernames, because for each domain virtualmin will take the domain name as username and it is the same for all 6-7 domains.. it produces unpredictable random ( for my POV) errors later in the process.

Sat, 08/10/2019 - 21:02 (Reply to #4)
RJM Web Design
RJM Web Design's picture

Ah, okay. I understand what you're saying. If the only difference between the domains are the TLD's, the Administrative Usernames are duplicated. I can see where that could create problems.


Sun, 08/11/2019 - 06:38 (Reply to #5)

Don't ever do if possible having naming default as you have the possibilty to create the ( custom) names yourself.

MUCH MUCH more secure!

Sun, 08/11/2019 - 09:27 (Reply to #6)
RJM Web Design
RJM Web Design's picture

Yes, I agree. But is that option available when creating an alias? I didn't look very hard because I wasn't actually doing it (I was just looking at it in response to the other poster's concern), but I didn't see an option to create a distinct user name in that panel.


Sun, 08/11/2019 - 11:08 (Reply to #7)

I can be wrong but for "domainalias" you mean under in a virtualserver creating a serveralias ,the main adminuser is then i think the one for parent default has

Aa alias server itself has no user on it for administration that alias server only

(Prefix you can have your own for mail and Databases if creating subserver)

And can create own users for alias server but only mail ftp as far i know.

But for the problem default adminuser you select your own custom username at creating virtualserver

Topic locked