One VPS to Run It All: Migrating Off Hostinger to OVH
Consolidating a sprawl of projects onto a single, boring, reliable box.
I moved off shared Hostinger plans and onto one OVH VPS. The reasons were noisy-neighbor CPU steal and limited control. This post covers the stack I run now, how to check for steal, and the Let’s Encrypt setup.
What runs on it
One box runs:
- a multi-app product suite
- a media stack
- this blog
- a metrics dashboard
- push notifications
- the FlameNet services
The stack
The stack is Docker, Traefik v3 and Let’s Encrypt. Each container carries labels, and Traefik routes by host from those labels. A new app means a new compose file and a few labels.
Check for steal before blaming containers
CPU steal is time the hypervisor gave to another guest. It shows as %st in top and in the st column of vmstat 1. A container cannot fix steal. If st stays high while your own load is low, the host is oversold.
That was my situation on shared hosting. Tuning containers does nothing for it. I did not log exact figures. I only know the slowness matched high steal.
Let’s Encrypt in Traefik v3
HTTP-01 certificates need a resolver in the static config. The settings, from Traefik’s docs:
--certificatesresolvers.le.acme.email=admin@example.com
--certificatesresolvers.le.acme.storage=/acme/acme.json
--certificatesresolvers.le.acme.httpchallenge.entrypoint=webacme.json must have mode 600. Traefik refuses to use the file otherwise. Create it first with touch acme.json && chmod 600 acme.json.
A container then asks for a certificate with one label, traefik.http.routers.myapp.tls.certresolver=le. That works only because a resolver named le exists in the static config. The next post in this series goes through the full label set.
Three lessons
- Plain Traefik beats a heavier stack. One proxy gave me one place to look.
- Check CPU steal before blaming containers. It cost me time on the old plan.
- Harden early. The box is public from the first hour. The hardening post covers SSH keys, CrowdSec, ModSecurity and egress rules.
What I would check on a new VPS
- Run
vmstat 1for a minute while idle and read thestcolumn. - Turn off password SSH logins before you deploy anything.
- Create
acme.jsonwith mode 600. - Start Traefik with one test container and confirm a certificate arrives.
- Add the other apps one at a time.