Topic · 5 items
Hosting
This page brings together news about servers, hosting providers and the cloud: outages and what they teach, system-level flaws to patch, infrastructure choices. It's for people who run websites or advise clients on hosting, and Preload follows here whatever calls for action on your side.
Follow this topic By RSS, in your feed reader
Spamhaus now requires consistent DNS from every server that sends email
Email sent directly from your servers may get blocked if they lack a consistent DNS identity: since November, rolling out over several months, Spamhaus requires every sending IP to have a valid HELO name (the name the server announces when it connects), a reverse PTR record and an A record that point to each other, or the server may be mistaken for a compromised machine. Exposed: servers that send mail themselves with the host's generic PTR and a default HELO, such as WordPress and WooCommerce on a VPS using mail(), Laravel or Symfony apps, monitoring alerts and cron jobs.
Next step
Test each sending IP with the HELO/DNS check on Spamhaus's Sender Guidelines page. Ask your host for a PTR that matches the server's HELO name, or move transactional email to an authenticated SMTP service or API: Google Workspace, Microsoft 365 and sending services such as Brevo manage their own IPs.
There's no hard deadline, but order confirmations and password resets are the first emails to vanish silently: now is the time to move transactional mail off
mail().
A six-hour Google Cloud outage exposes multi-zone setups without spare capacity
On October 20, from 7:00 to 13:10 London time, Google Cloud's europe-west2-b zone in London lost power, and more than 40 Google Cloud products were affected. According to the preliminary report of October 22, after the grid outage, both the primary and backup controllers failed to start the generators and the UPS batteries ran out; the traffic shifted to the region's two other zones then overloaded them (timeouts, 500 and 503 errors). Revolut was disrupted the same morning without naming a cause; the link to Google rests on an anonymous source quoted by Reuters.
Next step
Check that your critical services run across several zones with enough spare capacity to absorb the loss of a whole zone. For a service that can't go down, consider a second region.
Spreading across zones isn't enough if the remaining ones can't take the load of the zone that fails. Beyond that, relying on a single provider is a concentration risk, to weigh against the cost of a multi-region architecture.
Certificate authority keys exposed: Chrome and Firefox drop eMudhra
A valid TLS certificate could be forged for any domain: on October 17, the private keys of eight intermediate certificates from the Indian authority eMudhra, six of them for TLS, turned out to be recoverable (flawed generation, keys too small). Chrome blocked them that evening through CRLSet and announced it will remove the affected eMudhra root, Firefox revoked them through OneCRL, and Mozilla is urgently removing emSign ECC Root CA G3. eMudhra estimates around 30,000 certificates need to be migrated.
Next step
Update the certificate stores on your servers, Docker images and runtimes (Node.js did so on October 21), then redeploy. If one of your sites uses an emSign certificate, switch authorities, and never turn off TLS verification to work around an error.
Deno joins Cloudflare, Deno Deploy shuts down in six months
The Deno team is joining Cloudflare. The runtime will get one more year of bug fix and security releases, after which development stops; the code stays open source. Deno Deploy will shut down in six months, around April 2027, with migration help to Cloudflare Workers for paying customers. The JSR registry continues.
Next step
List your projects hosted on Deno Deploy and plan their migration now; for new projects, stop picking Deno.
Plesk: ten critical fixes in eight weeks
Between August 5 and September 29, the Plesk core received updates flagged “critical security issue” on ten separate dates. From February to July, there had been only three. The fixes include root code execution through the REST API (CVE-2026-68492, fixed in 18.0.80.8 and 18.0.81.1) and through an imported database name in Site Import (CVE-2026-87898, fixed in 1.12.2). On January 1, 2027, license prices go up: €15.99 per month excluding VAT for Web Admin, €28.99 for Web Pro and €62.99 for Web Host.
Next step
Run plesk version to confirm the server is at least on 18.0.80.9 or 18.0.81.2, update Site Import and Plesk Migrator or uninstall them if unused, and turn on automatic build updates. If you manage a fleet, stop waiting for the monthly maintenance window when a fix is flagged critical.
AI speeds up both the discovery and the exploitation of vulnerabilities, and update cycles have to shrink accordingly. We read the price increase as the cost of that pace; Plesk itself does not make that connection.