If you’ve visited this site at all within the last month or so, especially in the mornings (for some strange reason), you might have seen a screen giving you a “500 Internal Server Error”. I was seeing it regularly and this was incredibly frustrating to me. So with the redesign and all the new things that are and are about to be happening here, I also wanted to improve the hosting infrastructure. I use DreamHost for my hosting.
I use DreamHost because:
- They are green (they buy carbon credits for all their power usage/emissions).
- They have a kickass custom admin panel that is really easy to use. In my opinion, it’s so much better than cPanel.
- They have decent to good customer service. And anyone with any experience with hosting customer service would relish having a good experience.
But I have to say my sites not loading was really starting to get me down. I was starting to think I needed to move off of DreamHost, which I didn’t want to do for the reasons above. Plus, moving databases is a gigantic pain in the ass. So after an email message thread (I think by the end it was 30 messages long and was over a week of back and forth—I really didn’t want to move DBs) we figured out the problem.
The problem
My sites were using too much memory and thus going over my allotted amount and thus the error was produced. WordPress plugins tend to use a lot of memory, I learned. Especially, poorly written plugins. One in particular came to the mind of DreamHost, who wrote in their Terms of Service:
8. Customer agrees to not engage in activities pertaining to Black Hat SEO, Spamdexing, and so-called “Scraper sites.” These can all have a severely detrimental effect on server performance and are not permitted. Pursuant to this policy, the poorly-written WordPress plugin “All in One SEO Pack” is expressly prohibited on DreamHost shared hosting servers and may only be installed on DreamHost Private Servers (VPS).
I use the plugin “All in One SEO Pack”. This is part of the problem. The other part is the Lifestream plugin that I use. And another are the automatic database backup plugins I use. When they run they bog things down.
And after many, many, many emails, I found out how DreamHost sets the allowed amount of memory/cpu for each domain. With shared hosting you only get so much memory and cpu. That’s just a fact. I know it. However, I didn’t know that they separate those amounts by users, not by domains. (This information really isn’t going to be helpful unless you are familiar with DreamHost.) I had one main account and all my domains were feeding off one set amount/user account. However, with multiple users, they all get their own separate amount.
The solution
I made a unique user for each domain. If everyone has a unique user than they all get their own resources to pull off of. But I have gone a step further with Bailing Bucket. I don’t want their to be anymore issues so I have installed DreamHost Private Servers. DreamHost PS gives me control over the resources I require and should stop the site from ever experiencing another “500 Internal Server Error”. This comes with a cost, but I think it’s worth it. I have big dreams for this blog and I want to make sure I am setup right.
The request
It’s true that I have had my troubles with DreamHost, but really they’ve been great. They’ve taken my frustrations and worked with me through everything. If you are thinking about hosting your own blog (it’s definitely worth it), I’d reccomend them. In fact, I’ve created an offer I hope you can’t refuse. Plus, you’d help me offset the costs of this somewhat expensive hobby.
Sign up for a DreamHost account and use the promo code “BAILINGBUCKET” and you will get $50 (US) off your first year of hosting, plus 1 free domain name (ie: yourname.com).
