🧰
Hosting

Managing your own VPS: what you need to know

17.11.2026
← All articles

Moving from shared hosting to a VPS changes responsibility more than capability. On shared hosting the provider runs the server, security updates, web server and mail, and you only deal with site files and the database. On a VPS everything from the operating system up is yours: what to install, how to configure it and how to fix it when something breaks. That freedom is valuable, but it takes knowledge and steady attention.

Managed versus unmanaged

With a managed VPS the provider handles system updates, monitoring and some configuration. With an unmanaged one the provider keeps the virtual machine, network and hardware running, and everything inside the server is up to you. Before buying, be clear which type you are getting; on sayt.uz you can confirm this in the cabinet or with support.

Skills you really need

You do not have to be a sysadmin, but you should be comfortable with the Linux command line, editing config files, file permissions and ownership, installing and updating packages, and starting, stopping and inspecting services. Networking basics matter too: IP addresses, ports, DNS records and how a domain points to a server. You also need to understand how your stack, such as Nginx or Apache, PHP and MySQL, is configured. A few weeks of practice on a test server goes a long way.

Services and logs

sudo systemctl status nginx
sudo systemctl restart php8.3-fpm
sudo journalctl -u mysql --since "1 hour ago"
sudo tail -n 50 /var/log/nginx/error.log

Most errors explain themselves in the logs: missing permissions, a full disk, a wrong path or a failed database connection. Always test configuration before restarting, for example with sudo nginx -t. Reading logs calmly and changing one thing at a time is the single most useful habit for anyone running their own server, because it turns a mysterious outage into a specific, fixable error message.

Disk and resources

df -h
sudo du -sh /var/log/* | sort -h | tail
sudo journalctl --vacuum-size=500M

Logs and old backups fill disks quietly, and a full disk stops the database. Check memory and CPU with free -h, uptime and htop. Glancing at these numbers regularly lets you spot trouble before it becomes an outage.

Backups are your job

Do not rely solely on provider snapshots. A nightly cron job is the simplest start:

30 2 * * * mysqldump --single-transaction misol_db | gzip > /var/backups/misol_db_$(date +\%F).sql.gz

In crontab the % sign must be escaped. Copy backups off the server, prune old ones regularly and rehearse a restore before you actually need one.

SSL and the domain

sudo certbot --nginx -d example.uz -d www.example.uz
sudo certbot renew --dry-run

Let's Encrypt certificates renew automatically, but verify that renewal works. Point the domain's DNS records at your server's IP; sayt.uz customers do this in the DNS section of the cabinet.

Example: a small team's first VPS

A Tashkent delivery service built a Laravel ordering app and deployed it to a VPS with one developer and no sysadmin. One day logs filled the disk and the app went down. The developer then set a routine: every Monday check disk, updates and backups; once a month do a test restore; rotate logs automatically. It takes about half an hour a week, and there have been no surprise outages since.

When a VPS is the wrong choice

For a simple company site, blog or small shop, when you have no time or interest in server work, shared hosting is often better: the provider handles security updates, the web server and mail. A VPS pays off for custom software, Node.js or Python apps, bots, non-standard settings or heavy load. Ask yourself one question first: if the server goes down, who will restore it, and how fast? If the answer is clear, a VPS is a good fit.

Related articles

💾 Swap on a VPS: do you need it, how much, and how to set it up 🗂️ Working with the ISPmanager File Manager: Uploads, Archives, Editing and Permissions ⏱️ 504 Gateway Timeout: what causes it and how to fix it step by step 📜 Hosting SLA Explained: Uptime Guarantees and Compensation
🌐 Language
🇺🇿 O'zbek 🇺🇿 Ўзбек 🇷🇺 Русский 🇬🇧 English ✓