Dreamhost has added a nicer DNS management interface, along with some other updates to its panel.Continue reading post "#3322"
There was another DreamCompute incident leading to downtime of my site / server.Continue reading post "DreamCompute downtime incident 2020"
This site was down tonight, possibly for a couple hours, seemingly due to another issue with DreamCompute.Continue reading post "#2486"
My server and site were down for about 16 hours from Tuesday evening (≈18:08) to Wednesday morning (≈10:36). This was due to a significant problem that occurred due to an upgrade to the Ceph system running Dreamcompute. Numerous people were affected, based on Twitter posts, and we still have little information about what happened.Continue reading post "DreamCompute disruption incident"
So, this site was down for like 16 hours due to a botched update of DreamCompute by Dreamhost. Back up and running now. Will report more when I get home tonight.
I decided to contact Dreamhost about my Apache logs showing 200 statuse codes for all
mod_rewrite responses. It took seven back-and-forths to get across what was happening, discuss options, and conclude that “DreamHost systems are configured with a default environment meant to meet the most common webapp and customer requirements”.
I’ve done some more testing on the problem I mentioned before of all requests showing up as
200‘s in the Apache log on my Dreamhost shared server. I’m pretty sure it’s specific to their
Dreamhost must’ve had an outage of some sort this (last) morning. I noticed a little after 11 that I couldn’t upload anything to or log into my (shared) server. My sites were inaccessible. I tried the sites of a couple other people I know using Dreamhost (also shared), and they were also inaccessible, so it must’ve been something somewhat significant. Strangely, nothing relevant was on Dreamhost status. I tweeted about it at 11:20 and got a response from DreamhostCare that they were looking into it. They didn’t say anything more, but I noticed things were up and running again around 11:42. I found later that it must’ve been a DDoS on their nameservers. Outages have been rare, but certainly annoying when they happen.