1Choose the Operating System
Most websites and applications run on Linux. Ubuntu LTS and Debian are the most common choices, because they are widely documented, receive long security support and are easy to find help for. AlmaLinux and Rocky Linux suit people who prefer the Red Hat family. Choose Windows only when you need Windows software, such as .NET applications or trading terminals.
Pick the system you or your developer already know. A familiar system is easier to secure and to fix when something goes wrong.
2Log In and Update the Server
After your Poland VPS is delivered, you receive its IP address and login details. Connect from a terminal with SSH, using the root login first, then update the system straight away so that known security fixes are installed.
- Connect with
ssh root@your-server-ip and change the root password if you are asked to - Update the package list and installed software with the system's package manager, such as
apt update && apt upgrade on Ubuntu or Debian - Restart the server if the update installs a new kernel
- Set the server's time zone and hostname so that logs are easy to read
3Secure Access Before Anything Else
A public server is probed within minutes of going online, so secure access first. Create a normal user with sudo rights, add an SSH key for it, and then disable password logins and direct root login in the SSH settings. Keys are far harder to guess than passwords.
- Create a new user and give it sudo rights
- Generate a key pair on your computer with
ssh-keygen -t ed25519 and copy the public key to the server - Turn off password authentication and root login in the SSH configuration, then test a new session before closing the old one
- Turn on a firewall such as UFW, and allow only the ports you need (SSH, and 80 and 443 for web)
- Install Fail2ban to block repeated failed logins
Always keep one working SSH session open while you change SSH or firewall settings, so that a mistake does not lock you out.
4Install Your Web Stack
Install only what you need. A typical website uses a web server (Nginx or Apache), PHP or another runtime, and a database such as MySQL, MariaDB or PostgreSQL. A Node.js application usually runs behind Nginx as a reverse proxy, managed with a process manager.
Add HTTPS with a free certificate from Let's Encrypt, using Certbot, and set it to renew automatically. Point your domain's A record at the server's IP address, and give DNS a little time to spread. If you need a domain, you can register one with us.
5Backups and Monitoring
A server without backups is a risk waiting to happen. Schedule daily backups of your files and databases and keep copies in a different place from the server, then test restoring one. Monitor disk space, memory and CPU, and set up an uptime check that emails you when the site stops responding.
Updates matter too. Turn on automatic security updates where suitable, and review the server once a month.
6When to Upgrade or Add Servers
Watch your resource use over a few weeks. If memory, CPU or disk are regularly near their limit, move to a larger plan. If you need to serve users in another part of the world, add a second server in that region rather than overloading one location. Our guide to choosing a VPS location explains how to decide.
You can also see all VPS locations and plans, or ask our team for help with setup.
