Dreamhost VPS: Don’t Go For It

We have been working on a project for a client whose identity is irrelevant to this post. This client has a pre-existing Dreamhost “VPS” plan to which we needed SSH access for some of the work that needed to be done. We were not familiar with Dreamhost (we are now) and, after some minor poking around, something seemed not quite as expected.

The suspicion began with the fact that subdomains have to be added using Dreamhost’s custom admin panel. A VPS should allow one complete control over server configuration, of course; instead, Apache’s httpd.conf would be rebuilt upon any change via the administration panel, overwriting custom changes. Giving the benefit of the doubt and supposing that perhaps this was a tool meant to be more user-friendly, we investigated more.

The second hint (tried on a hunch) was:

$ sudo cd /
[sudo] password for anastasllc_root:
sudo: cd: command not found

This points to chrooted access and not being on a true VPS. Next:

$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/hdv1 3.6T 808G 2.8T 23% /

Aside from the fact that we hadn’t used anywhere near 808G of disk space, 3.6T disk space on a cheaper VPS plan? More pertinently, /dev/hdv1 points to use of Linux VServer.

A virtual server is one that is, well, virtual. “Virtual” means that the entire server environment is emulated (in the same way that scifi “virtual reality” is meant to mimic reality entirely), via a hypervisor or otherwise, giving each customer what looks like an entire server whose entire filesystem and operating system can be entirely controlled. This “VPS” package is perhaps a “simulated private server”, but definitely not a “virtual private server”.

While we will work within the restrictions of Dreamhost’s “VPS” package for this client’s project, we recommend against opting for Dreamhost if a VPS is desired. If you want what is essentially shared hosting, get shared hosting. If you want complete control over your server, opt for a true VPS, such as via Linode¬†or AWS, both of which we use and recommend wholeheartedly.

Update: We should have looked at the actual “VPS” hosting plans offered by Dreamhost in the first place. Anything “unlimited” is always a red flag, and $15/month for 300mb RAM is ridiculous (for example, Linode’s current $20/month VPS hosting offers 1GB RAM, which Dreamhost charges $50/month for, 150% more). Opt for Linode, AWS, or similar instead to get more for your money.

This entry was posted in Expository. Bookmark the permalink.

6 Responses to Dreamhost VPS: Don’t Go For It

  1. Adrain says:

    Dreamhost are awful. I’m still waiting for replies on support tickets from December.

    • I’ve been mostly pleased with Dreamhost, but as my company is approaching the need from a VPS, I am not considering staying with Dreamhost. They over-charge for memory & that’s the whole reason I need a VPS: dedicated memory!

      In my experience, support tickets are usually answered in less than 12 hours and if I am in need of a faster response, tweeting to @DreamHostCare gets a response much faster.

  2. skyborne says:

    Well actually…

    [skyborne@aerie ~]$ sudo cd /
    sudo: cd: command not found

    cd is a shell builtin and does not necessarily exist in $PATH. In my case, aerie is a VirtualBox guest running CentOS on a Mac host.

    To my surprise, the cd command did work on the Mac because /usr/bin/cd exists. Why, however, is a mystery for the ages: it can’t really do anything if it doesn’t launch any further processes.

  3. Pingback: VPS Comparison: Run away from Dreamhost and to Linode | axfp.org

  4. AstroNerdBoy says:

    I went to DreamHost because it was recommended by a friend. I didn’t have any problems until I moved my anime blog over. Then, I started encountering problems as my anime blog is moderately popular. If I get an influx of traffic, I was choked down immediately.

    As such, I was researching the VPS options. I saw that their prices for so little RAM seemed ridiculous. I’m going to research new options.

  5. Eric says:

    Dreamhost used to be great – now they’re awful. Unstable servers, slow response times. I’m so bummed about these small hosting companies are great when small and then tank as they get more popular. I’m through working with the small ones — sticking to the big guys like Rackspace from now on.

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>