Help getting started with Virtualmin

3 posts / 0 new
Last post
#1 Mon, 05/06/2019 - 10:03
oguruma

Help getting started with Virtualmin

I just installed Virtualmin in a small CentOS. I have a few websites that are about to outgrow their shared hosting, and I am considering Virtualmin or Plesk on CentOS as a solution.

  1. What is the difference between Virtualmin and Webmin? I really don't understand the distinction between the two pieces of software...

  2. If you need to create an account for a client/customer, you would use a "Virtual Server" for that, correct?

  3. Virtual Servers do what exactly? Create a separate directory for customer's stuff?

  4. I created a virtual server with everything default, then used the Wordpress installer to install Wordpress on that virtual server, but I get a 403 error. Is there something else I have to do? Or is the Wordpress installer supposed to take care of everything?

Mon, 05/06/2019 - 16:20
andreychek

Howdy,

What is the difference between Virtualmin and Webmin? I really don't understand the distinction between the two pieces of software...

Webmin is the service that runs on port 10000, and is largely a tool providing sysadmins a GUI to manage their servers.

Virtualmin is a Webmin module, that adds the functionality to handle web/email/DNS hosting.

If you need to create an account for a client/customer, you would use a "Virtual Server" for that, correct?

Yup! That's just a fancy name for a "domain". Virtualmin started using that terminology before "Virtual Server" started being used to describe Virtual Machines... but now it's just confusing :-)

Virtual Servers do what exactly? Create a separate directory for customer's stuff?

Yeah, it's what other control panels call a "domain". When you create a Virtual Server in Virtualmin, that sets up a new user, along with the ability to host a website, DNS, email, and such.

I created a virtual server with everything default, then used the Wordpress installer to install Wordpress on that virtual server, but I get a 403 error. Is there something else I have to do? Or is the Wordpress installer supposed to take care of everything?

A 403 error typically means that the directory that was requested doesn't have an index file in it, such as an index.html or index.php.

You'd want to ensure that the public_html folder has an index file.

When installing WordPress using the Install Script, by default it's put into a sub-directory, not in the root public_html folder. If that's where it was installed, you'd need to ensure that you're accessing the sub-directory where WordPress was installed

-Eric

Mon, 05/06/2019 - 21:06 (Reply to #2)
oguruma

Thanks for the input. I just copied and pasted the Wordpress stuff into public_html and we're off to the races.