VPS

Your responsibilities

A VPS is a Linux server with its own allocated resources. It gives you more control than a hosted website, and you manage the operating system, applications, updates, access and backups unless your agreement includes additional management.

Choose a plan for your application’s CPU, memory and disk needs. Review the operating systems and current availability at checkout. A larger server does not automatically configure your website, mail or database.

Choose your setup

1. Choose a plan on the VPS plans page and add it to your basket.
2. In the configuration dialog, choose an offered Linux operating system and the login method.
3. If using an SSH key, paste your public key. Keep the private key on your device; never paste it into checkout or send it to support.
4. Save the configuration. Reopen the basket item if you need to check or change it before payment.
5. Complete checkout, then open Sites → Your servers and wait for provisioning to complete.

First login

Use the IP address, login username and access instructions supplied for your machine. Do not guess the username or reuse another server’s details. With an SSH client, the command has the form ssh username@server-address; replace both placeholders with your actual details.

If you supplied a key, use its matching private key on your own computer. Keep a password manager copy of any generated credentials. Check the server identity through the supplied access information where available. If your SSH client reports a changed host key on a machine you have not rebuilt, investigate before accepting it.

Once connected, verify that the hostname, operating system and disk capacity are what you ordered before installing applications.

Security

1. Apply the operating system’s updates and arrange regular maintenance.
2. Create appropriate user accounts and restrict administrative access. Check a second login works before disabling an existing access method.
3. Configure the firewall to permit only the traffic your application needs, preserving your management connection.
4. Install and configure your software, then test it before pointing a production domain at it.
5. Set up application monitoring and independent backups, including database dumps and the configuration needed to restore.

Use your operating system’s documentation for its exact commands. The correct package manager and firewall configuration depend on the image you chose.

Restart or reinstall

The server card offers Start, Shut down, Restart and Force stop when applicable. Use Shut down for a normal stop. Force stop can lose unsaved data and is intended for a machine that will not shut down normally.

Reinstall wipes the server. Download and verify any files, databases and configuration you need before using it. To rebuild, choose Reinstall…, select the new system, review the optional hostname and public SSH key, then type the server address to confirm. Use Wipe and reinstall only when you intend to erase the current installation. Wait for the new access details, then restore and test your application. Reinstalling is not a way to recover deleted files.

Limits and backups

Use the controls shown on the server’s workspace card. A restart interrupts applications and active connections, so save work and schedule it when disruption is acceptable. Stopping a machine is not the same as cancelling its subscription; manage billing separately.

Do not assume snapshots or backups are included just because hosting has a Backups tab. Confirm what is available for your VPS and test your own recovery process. Outgoing mail ports are restricted on new servers under the acceptable use policy; contact support if you need them reviewed for a legitimate mail setup.

Can’t connect

Check that provisioning has completed, the machine is running and you are using its current IP and login details. If SSH times out, check the network and firewall rules. If login is rejected, check the username and whether you are using the correct password or key.

If only the application fails, check its service status, logs, free disk space and memory before restarting the whole server. Avoid repeated forced restarts. Give support the server identifier, time, affected connection and error, plus recent changes. Never send private keys or server passwords in a ticket.