How to set up a VPS from start to finish

Key takeaways

• VPS setup includes choosing a configuration, connecting securely, updating the system, setting up a firewall, and installing services.
• Linux servers typically use SSH, while Windows servers use Remote Desktop.
• Test a new administrator account before restricting root access, passwords, or firewall rules.
• Configure backups and monitoring before moving production traffic to the VPS.

A VPS gives you more control than shared hosting, along with greater responsibility for security and maintenance.

Setup typically includes choosing the operating system and resources, connecting remotely, installing updates, securing access, and configuring the required services. This guide covers the Linux and Windows process in six steps.

VPS setup steps at a glance

1. Choose your VPS configuration
2. Provision and connect to the server
3. Update the system and create an administrator
4. Secure remote access and configure the firewall
5. Install services and connect your domain
6. Configure backups, monitoring, and final testing

Learn more: A complete beginner’s guide to virtual private servers →

What you need before you start

Before changing your server settings, make sure you have access to the provider control panel, know the operating system and version, can reach the provider’s console or recovery tools, and have the domain name you plan to use if you intend to host a website.

You will record the server’s IP address, hostname, and connection details in Step 2. Store passwords, SSH keys, and recovery information in a secure password manager.

Also confirm that your provider offers browser-based console or recovery access. This gives you another way to reach the server if an SSH, Remote Desktop, or firewall change blocks the normal connection.

1. Choose your VPS configuration

Compare more than the starting price. Look at the supported operating systems, management options, resources, backup services, support scope, data center locations, and whether you can move to a dedicated server as your needs grow.

Decide whether to manage the VPS yourself

You can set up your own VPS if you’re comfortable using SSH or Remote Desktop and handling updates, security, backups, monitoring, and troubleshooting.

A self-managed VPS gives you direct control over the server, but the provider may limit support to hardware, networking, and platform availability.

With a managed VPS, the provider handles a defined set of administrative tasks. Confirm whether the plan includes operating system updates, security configuration, service monitoring, backups and restoration, control-panel support, and web server troubleshooting.

A control panel can simplify hosting tasks, but it doesn’t turn a self-managed server into a managed one.

Choose Linux or Windows

Select the operating system based on the software you plan to run, licensing requirements, and your team’s experience.

A Linux VPS may work well for WordPress and other open source applications, Apache or NGINX, PHP, Python, Node.js, container workloads, and teams comfortable with command-line administration.

Common server distributions include Ubuntu, Debian, and AlmaLinux. Use instructions written for the distribution installed on your VPS because commands and service names may differ.

A Windows VPS may work better for IIS, ASP.NET or .NET Framework applications, Microsoft SQL Server, Windows-only business software, and Remote Desktop administration.

Windows Server usually includes licensing costs that don’t apply to open source Linux distributions.

Select the server resources

Match the CPU, RAM, storage, and bandwidth to the applications you plan to run.

Leave room for the operating system, updates, security scans, background services, traffic changes, and growth. A configuration that only meets an application’s minimum requirements may need an early upgrade.

2. Provision and connect to the server

After you select the operating system and resources, provision the VPS through the provider’s control panel.

Record the server’s:

• Public IP address
• Hostname
• Initial username
• Temporary password, when applicable
• SSH port or Remote Desktop information
• Provider console link

You don’t normally need to install a hypervisor or create another virtual machine inside a hosted VPS.

How to set up a VPS server on Linux

Most administrators connect to a Linux VPS through Secure Shell, or SSH.

Current macOS, Linux, and Windows systems typically include an OpenSSH client. Open a terminal or PowerShell window and enter:

Replace your_server_ip with the public IP address supplied by your hosting provider.

The server may ask you to confirm its host key fingerprint during the first connection. Compare it with the fingerprint shown in your hosting account before accepting it.

Enter the temporary password when prompted. The terminal won’t display the characters as you type.

After connecting, confirm the server identity:

You can specify a private SSH key when connecting:

How to set up a VPS server on Windows

Windows VPS users commonly connect through Remote Desktop Protocol, or RDP.

To connect from a Windows computer:

1. Open the Remote Desktop Connection application.
2. Enter the VPS IP address.
3. Select Connect.
4. Enter the administrator credentials supplied by the provider.
5. Verify the server information before accepting a certificate warning.

After signing in, check the Windows Server version, computer name, IP configuration, available memory and storage, date and time, and Windows Update status.

Keep Windows Firewall enabled and limit Remote Desktop access to trusted users and networks where possible.

3. Update the system and create an administrator

Install available operating system updates before adding public services or moving a production workload to the VPS.

Update Ubuntu or Debian

Run:

The first command refreshes information about available packages. The second installs the available upgrades.

Restart the server when required:

Reconnect after the restart and check for any remaining updates.

Update AlmaLinux or another RHEL-based distribution

Run:

Restart the server when required, then reconnect and confirm that the services you need have started.

Update Windows Server

Open Settings, select Windows Update, and install the available security and quality updates.

Restart Windows when prompted, then run Windows Update again to check for additional packages.

Create a non-root Linux user

Using root for every administrative task increases the impact of a mistake or compromised login.

Create a new user:

Replace adminuser with the username you want to use.

On Ubuntu or Debian, grant administrative privileges with:

On AlmaLinux and other RHEL-based systems, use the wheel group:

Open a second terminal and test the account:

Then verify administrative access:

The command should return root.

Keep the original root session open until the new account can connect and run administrative commands.

Create a Windows administrator account

Create a named account for routine Windows Server administration instead of sharing one generic administrator login.

Add the account to the appropriate local administrator group, assign a strong password, and test it through a separate Remote Desktop session.

4. Secure remote access and configure the firewall

Secure remote access before opening the server to additional traffic.

Configure SSH key authentication

SSH keys provide stronger protection than password-only access when you protect the private key with a passphrase and store it securely.

Generate an Ed25519 key on your local computer:

Copy the public key to the new Linux user:

When ssh-copy-id is unavailable, add the public key to the user’s ~/.ssh/authorized_keys file manually.

Open another terminal and test the key:

Don’t change the SSH server settings until that login succeeds.

Edit the SSH configuration:

Depending on the distribution, the server may also use files inside /etc/ssh/sshd_config.d/.

Set:

Validate the configuration:

If the command returns no errors, reload or restart the SSH service using the command required by your distribution.

Keep the original connection open while testing the new configuration.

Configure the Ubuntu firewall with UFW

Allow SSH before enabling the firewall:

If the server will host a public website, allow HTTP and HTTPS:

Enable the firewall:

Review the rules:

Only open ports required by the workload.

Configure firewalld

AlmaLinux and other RHEL-based distributions commonly use firewalld.

Check whether it is active:

Allow SSH:

For a public web server, allow HTTP and HTTPS:

Apply the changes:

Review the configuration:

Protect Windows Remote Desktop

For a Windows VPS:

• Use named administrator accounts
• Require strong, unique passwords
• Enable Network Level Authentication
• Restrict RDP to trusted IP addresses when possible
• Use a VPN or Remote Desktop Gateway when appropriate
• Review failed login attempts
• Keep Windows Server current

Changing the default RDP port shouldn’t serve as the primary security control.

Configure Windows Firewall

Open Windows Defender Firewall with Advanced Security and review the inbound rules.

Permit only the services you intend to expose, such as:

• RDP for remote administration
• HTTP for public web traffic
• HTTPS for encrypted web traffic
• Application-specific ports required by the workload

Restrict RDP to trusted source IP addresses where practical.

Your hosting provider may also offer a network firewall through its control panel. Review both the provider-level firewall and the firewall inside the VPS.

5. Install services and connect your domain

What you install next depends on what the VPS will run.

Choose a server stack or control panel

Depending on your project, you may install a web server such as Apache, NGINX, or IIS; a runtime such as PHP, Python, or Node.js; and a database such as MySQL, MariaDB, PostgreSQL, or Microsoft SQL Server. You may also install WordPress, Docker, a VPN service, or a control panel such as cPanel, Plesk, or InterWorx.

A control panel provides a graphical interface for common website, database, email, and domain tasks. It can simplify administration, but it also uses server resources and may carry a licensing cost.

Follow installation instructions written for your operating system and software version.

Set the hostname and system time

Set a descriptive hostname so logs and monitoring tools identify the server correctly.

Also verify the time zone, current date and time, network time synchronization, and fully qualified domain name when required.

Incorrect system time can affect logs, scheduled tasks, authentication, and certificate validation.

Point a domain to the VPS

Open the DNS manager provided by your registrar or DNS host.

Create an A record that points the domain to the VPS IPv4 address. A common configuration uses:

• Host: @
• Value: Your VPS IPv4 address

Add a separate record for www if the website should respond to that hostname.

Confirm that the domain resolves to the correct address before directing production traffic to the server.

Configure HTTPS

Install an SSL or TLS certificate after the domain points to the VPS.

The process depends on the operating system, web server, control panel, and certificate provider. Let’s Encrypt offers free certificates, while many control panels include automated certificate tools.

Verify that the certificate matches the domain, the browser trusts it, HTTP redirects to HTTPS, automatic renewal works, and all page resources load through HTTPS.

6. Configure backups, monitoring, and final testing

Before launch, configure a way to detect problems and restore the server.

Configure backups

Create a backup plan that covers:

• Website and application files
• Databases
• Server configuration
• Certificates and encryption keys
• User-generated content
• Full-server recovery, when available

Store at least one backup outside the VPS. A server failure, security incident, or accidental deletion can also affect files stored on the same server.

Set the backup schedule and retention period based on how often the data changes and how much data the business can afford to lose.

Snapshots can help restore a VPS to an earlier state, but they don’t always replace independent backups.

Test a restoration before relying on the backup process.

Establish a monitoring baseline

Monitor:

• CPU use
• RAM use
• Available disk space
• Network traffic
• Application and web server status
• Failed login attempts
• Operating system errors
• Backup failures

Linux users can check basic resource use with:

Windows users can use Task Manager, Resource Monitor, Performance Monitor, and Event Viewer.

Record normal resource use after setup so you can identify unusual activity or gradual performance changes later.

Test the VPS setup

Before moving production traffic, confirm that:

• The new administrator account can connect
• SSH keys or RDP work after a restart
• The firewall allows only required ports
• Operating system updates are complete
• Required services start automatically
• The application responds correctly
• The domain resolves to the VPS
• HTTPS works without certificate warnings
• Backups complete successfully
• A restore test works
• Monitoring reports normally
• The provider console remains available

Restart the VPS one final time and repeat the most important checks. This confirms that services, firewall rules, network settings, and scheduled tasks persist after reboot.

Common VPS setup mistakes

Locking yourself out. Test every new account, SSH key, and firewall rule in a second session before restricting the original access method.

Opening unnecessary ports. Each publicly accessible service increases the server’s exposure. Open only the ports required by the workload.

Using commands for the wrong operating system. Ubuntu, Debian, AlmaLinux, and other distributions can use different package managers, file locations, service names, and defaults.

Relying on untested backups. A completed backup job does not guarantee that you can recover the data. Test the restoration process before launch.

Skipping the post-reboot test. A service may work after installation but fail to start automatically when the VPS restarts.

VPS setup FAQs

VPS setup next steps

A complete VPS setup includes secure remote access, current software, firewall rules, the required application services, working backups, monitoring, and final testing.

Start by collecting the server IP address, login credentials, operating system details, and provider console information. Then follow the Linux or Windows instructions that match your VPS.

Liquid Web by Nexcess offers VPS hosting with multiple management options for businesses that need more control than shared hosting can provide. Explore Liquid Web VPS hosting to compare plans and choose a configuration that fits your workload.

Related Resources

Managed VPS vs Unmanaged VPS: What’s the Difference?

Caching Options for Optimizing Your VPS

5 Simple VPS Management Tools You Need

Why VMware performance monitoring is a must for your enterprise

Top 10 bare metal cloud hosting providers in 2024

Comparing hosts and servers: Key differences explained

Gilbert Hernandez is a Software Engineer at Liquid Web with experience in web development, WordPress, and JavaScript. He focuses on building and supporting web solutions that help improve performance and functionality.