The EuroVPS blog
Field notes.
From the engine room.
Decisions, investigations and lessons from running production infrastructure. Written by the people who look after it.
The archive
More from the team.
How to read a Galera cluster's health in five status variables
The wsrep status variables that tell you whether a Percona XtraDB or MariaDB Galera cluster is healthy, slow, or one step from losing quorum.
Replicate the group, not the disk: consistency in array replication
Why replicating each volume alone can leave a remote copy that will not start, how consistency groups fix it, and how to test a replica safely.
One front door for every internal tool: a self-hosting pattern
How to run task boards, dashboards, a password vault and more behind one reverse proxy: wildcard DNS, containers under systemd, layered access, safe renames.
Read the scope line: checking a host's ISO claims
A logo proves little. What to read on a host's ISO certificate: the scope line, who issued and accredited it, the dates and the Statement of Applicability.
Central logging that holds up in an incident review
How to build central logging you can trust when it matters: reliable forwarding, one clean name per device, correct clocks, role streams and alarms on silence.
Wiring PHP to Valkey Sentinel, and proving the failover works
A replicated cache only helps if PHP follows the promotion. How to set up Sentinel, connect WordPress and Laravel, pick an eviction policy, test it.
The failure domain map, and the handover test that proves it
High availability is a claim until tested. How to map replicas to hosts, arrays and chassis, enforce anti-affinity, and run a failover test sheet.
How an EVPN fabric knows where your server is
A practical walk through BGP EVPN route types, anycast gateways and ingress replication, with the show commands an engineer uses to trace a host.
How to acceptance-test a Kubernetes cluster before production
A green dashboard is not a ready cluster. Test storage restores, node failure, disruption budgets, builds and tenant access on OpenShift or OKD first.
Write the rollback first: a template for routine upgrades
A practical upgrade template: watch releases, pre-flight every server, verify the backup, write the way back before you start, and measure downtime in seconds.
Change one thing, measure again: finding the real bottleneck
A repeatable method for slow servers: define the symptom, check each resource for use, saturation and errors, change one thing, measure again.
Pull-only backup: why production should never reach its own backups
How to design backups an intruder on production cannot delete: pull from the backup side, lock keys to one command, append-only repos, prune locally.
Upgrading self-hosted live chat without losing a conversation
A step-by-step method for upgrading self-hosted Chatwoot in containers: baseline counts, a quiesced dump, a written rollback and checks from the visitor's side.
The most privileged port in the rack is the one nobody watches
iLO and iDRAC can power off, reinstall or read any server. How to isolate management controllers on an air-gapped network, harden them and configure at scale.
Filter before you prefer: writing a BGP edge policy that fails safe
How to structure a multi-homed BGP edge: inbound hygiene first, then a tiered local-preference scheme, outbound discipline and anti-spoofing. With examples.
Live migrating a KVM guest with its storage, step by step
How to move a running KVM virtual machine and its disk between hosts with libvirt: compatibility checks, destination prep, the command, and when to go cold.
Bucketing PHP-FPM slow logs to find what your site waits on
PHP-FPM's slow log records a stack trace for every slow request. Grouped by the frame each request was stuck in, it tells you exactly where your time goes.
Stop comparing GPUs by the hour.
The comparison sheet has six providers and one column, dollars per GPU-hour, sorted ascending, decision gravitating to the top row. Nobody asks what the number is a price of. It could be a consumer card, a shared machine, or dedicated datacenter silicon in an EU rack, and the column cannot tell you which.
How to size a server (most people need less than they think)
Your last invoice records what you were charged, not what you used. Three commands on the box you already run give you the real number.
How we change routing without asking permission.
When most hosts need a routing change, they open a ticket and wait. We make the change ourselves, under a written runbook that keeps it safe.
We built a VPN Control Center for an agency's own team.
A multi-brand agency asked for self-service: make our own people able to run routine VPN changes. What we built, why it took the team that operates the infrastructure to build it, and what we kept.
Most read
The guides readers come back to- 01Top 10 Reasons Your Site Loads Slowly (And How to Fix Them)
- 02Important Linux Log Files You Must Be Monitoring on RHEL 9 and 10
- 03Configuring WordPress Multisite with Nginx and PHP-FPM on RHEL 9 and 10
- 04Archimedes and the compound pulley: how one man moved a ship
- 05Ultimate Guide to Understanding HTTP Status Codes: 300 Series
- 06Ultimate Guide to Understanding HTTP Status Codes: 400 Series
- 07How much RAM, CPU, Storage, and IOPS resources does your VPS really need?
Put the reading to work
Have a workload in mind?
Start with the numbers.
The sizing desks turn your requirements into a proposed configuration and an indicative price range. An engineer can help you review what fits.

