If you use the WordPress 2.5 blog software on your site, be sure to upgrade to WordPress 2.5.1 as soon as possible. The upgrade contains an important security fix. (We’ve updated our own blog, and it was painless.)
Although all WordPress users should upgrade right away, we’ve also added a security rule to our servers to try and protect our customers who haven’t yet upgraded. Other people may also find the security rule useful if they use mod_security on Apache Web servers. The rest of this post contains more technical details.
Read the rest of this entry »
A heads-up if you use Ruby on Rails: We’re going to be upgrading the default version on our servers to 2.0.2 soon. We want to give you plenty of notice, because when we tried upgrading some older test applications, they didn’t work without changes.
Read the rest of this entry »
Starting at 10:14 AM this morning, our elzar server experienced an unexpectedly high server load that effectively made some processes on the server unusable for about 10 minutes.
Web sites using scripts or databases on the elzar server may have seemed unresponsive during that time. Also, any customer hosted on elzar who was reading their e-mail during this time may have felt the system was slow or unresponsive (no e-mail was lost, of course).
Customers on other servers were not affected.
Read the rest of this entry »
The “farnsworth” Apache Web server had an outage lasting approximately five minutes at 11:36 AM Pacific time today, resulting in an interruption of service for Web sites and e-mail on that server. Other servers were not affected.
The problem occurred when the Apache web server process failed to gracefully restart when a new SSL certificate was added. We have discovered why this happened and will take steps to prevent it in the future.
We sincerely apologize to anyone affected by this.
Update: We have added a new automated step to our certificate installation process that checks for problems with SSL certificates, guaranteeing that this problem will not recur.
