So for those who finally got the Linux VPS of their dreams and do not know how to get in since they’re used to Windows, here is a summary of the steps to get into a VPS:
1. Choose your Operating Software (OS)
When you get your VPS you’ll be provided with a VPS Control Panel like Virtualizor or SolusVM. First thing to do is to choose the OS. Most popular presently seem to be Ubuntu or Debian, also CentOS, there is a wide variety, but most hosts have the latest templates available. So do a fresh install once you’ve selected your OS. Keep the password handy as that will now be your ROOT password and super key to communicate with your server.
2. SSH Client – PuTTY
Best way to get into the VPS from a Windows environment is through an SSH Client that will connect your computer with your VPS on a remote server. For that you need to set yourself up with PuTTY first and here’s a tutorial how to do it:
https://dhnexus.com/getting-in/
3. Root log-in
Once you’re in PUTTY it will ask you for a User Name and Password. The User Name is always “root” (without the commas) and the Password is the one you set up when you load your Operating Software for your VPS.
4. Change Password
Most important next step is to change your password. I cannot emphasize more how important a VERY SECURE password is. I get my passwords from a 16-digit password generator at the link below:
https://passwordsgenerator.net/
Then type the following command in PuTTy:
passw
And change your password.
5. Control Panels
Most of us who are used to a Windows environment and shared hosting with a cPanel or DirectAdmin Control Panel will be quite daunted by all of the Linux commands. You could take some time of course to master all of the commands, but for those who wish to work with a Control Panel instead, cPanel may be too much to pay. I’ve done research and found some free control panels that seem to be popular and reliable (although most come with challenges that can be overcome).
https://dhnexus.com/free-control-panels/
My choice for a cheap control panel for now is MyVesta, a Debian fork of VestaCP. VestaCP had an issue in 2019 of an owner that was no longer interested enough to keep the script up to date. This was followed by the exit of most of its Admin. Some created a new free panel called Hestia Control Panel. There was also a CentOS fork that was developed in Belgium, and a Debian fork with MyVesta. I was very happy to change from CentOS to Debian in order to have access to MyVesta panel. CentOS 8 had become much too large and complicated to manage and Debian just feels more streamlined and less complicated to work with.