Hetzner Cloud firewall: structure rules before multiplying servers
The Hetzner Cloud firewall applies upstream of VMs — without naming conventions and groups, ten servers become ten diverging configurations.
Browse our Technical posts on European hosting.
No results for this search
The Hetzner Cloud firewall applies upstream of VMs — without naming conventions and groups, ten servers become ten diverging configurations.
Without a shared hypervisor layer, Leaseweb bare metal leaves hardware responsibility with you — SMART, IPMI, temperature, and network saturation become critical.
A TransIP snapshot reassures on paper — without restore test, measured RTO, and off-panel procedure, it is only an unverified photo.
Which layer serves HTML, objects and plugins, and in which order to purge. Plugin, SSH and root limits are another article.
Retrying all failed emails at once after an SMTP outage guarantees a second incident — blacklist, rate limit and saturated mailboxes. The queue needs a backoff strategy.
A cron that exceeds its interval, a deployment that restarts workers, DST handled badly — without a lock, you duplicate invoices, emails or imports without noticing.
Elasticsearch is hungry for heap and I/O. On a VPS shared with your app, a poorly tuned reindex can OOM-kill your PHP or Node process overnight.
Meilisearch is light and quick to install — but snapshot backup and recovery need discipline many Docker deployments skip until the first index loss.
A chat, real-time dashboard or online game that disconnects every 60 seconds often points to a misconfigured proxy — not your WebSocket code.
HTTP/3 runs on QUIC over UDP. If firewall or host blocks UDP 443, clients silently fall back to HTTP/2 — or fail without clear message.
Long-lived connections die silently when a NAT or load balancer cuts idle flows. TCP keepalive detects that — provided you do not confuse it with application heartbeats.
Some pages load on Wi-Fi but not on 4G, or stall after the first MB. Often the culprit is MTU or broken PMTUD — not your application.
Adding an AAAA without checking the full stack can break access for some visitors. Here is how to enable IPv6 without timeouts or blank pages.
A scanner reporting 200 CVEs does not tell you which ones touch your attack surface. Here is how to prioritise fixes by real exposure, not raw scores.
A strict CSP header on Friday night and Stripe checkout vanishes: the XSS barrier only ships via report-only → enforce, with marketing in the loop.
CORS console error: not the API lock but browser policy — origin whitelist, OPTIONS preflight, and independent auth.
After Let's Encrypt renewal, the mobile app may stay offline: pinning on the old key without backup pin blocks the whole fleet.
Midnight cutover without schema/data parity: sequence expand/contract, sync and traffic — clone dry-run before prod window.
A reversed rsync cron wipes prod: trailing slash, --delete, and written SRC→DST direction prevent destructive sync.
Object Lock blocks ransomware on copies — only if you proved restore before trusting immutability.
Restoring the whole VM for one customer erases everyone's timeline: granular restore requires tenant architecture and semiannual drills.
Prod encrypted at rest, backups land plaintext in a shared bucket: one compromised credential exposes full history.
Serving 10 GB user exports through PHP would saturate CPU. Presigned URLs delegate download to storage — with an expiry date you must not forget.
The S3 bill doubles quietly: millions of never-read objects sit in Standard tier. Lifecycle rules automate archiving — if you test them.