The Saga of the New Web Hosting Provider

As I mentioned a while back, I recently switched to a new web hosting provider, Media Temple. I wanted to provide a bit more detail as to why.

About a month-and-a-half ago I was uploading some new content to my personal site, which hosts a fair amount of video and audio for download, on my old web hosting provider, Web Hosting Buzz, when suddenly I was unable to connect to my site, either via FTP or the web. This had happened before, and I was starting to get concerned, so I decided to start a Live Chat session with tech support. After some poking around, the technician was able to determine that my site was available to everyone but me, the owner, and that my uploads had resulted in the blocking of my IP address. Seems they only allow a certain number of connections, and my FTP client (the venerable Yummy FTP) was set beyond their threshold. The tech person I was chatting with helpfully advised me to set the number of concurrent sessions to two or less. I set mine to one. He unblocked my IP address and all was again well with the universe.

Cut to the next day: Wash, rinse, repeat. Same problem, only this time the tech online told me that I was in violation of their acceptable usage policy, and directed me to the Disk Usage Provision section of that policy:

"90% or more of your content on your website must be linked from an HTML or similarly coded web page where all content is freely available to the public. Your website consists of web pages of a standard design, essentially HTML based text and graphics. Downloadable files, media, streaming content or any file which consumes more than 500kb of space must not exceed 10% of your total used disk quota." [Emphasis added]

Yikes!

This time the technician informed me that I had too many files that exceeded 500kb, and that I would need to remove all media that was in violation of this policy. Funny thing was, I'd been in violation for months. Why had no one informed me? Why was this suddenly a problem? I asked the tech. He said it had been their mistake, but that it was my fault for not having read the policy.

Ah, customer service! Ya gotta love it!

In fact, I had read the policy, but I'd kinda glossed over the whole, "You can't actually, feasibly use the total amount of disk space we claim to give you," part. I mean, really. Who would think that a company would offer you 1250GB of storage and then make it practically impossible to use said storage?

Call me naive.

So, after explaining to the technician that their "mistake" had cost me a great deal of time and effort, I asked him how I was to remove the content if my IP was still blocked. He told me he would unblock the IP for 24 hours if I promised to remove the files that violated the policy. During this conversation there was very much a sense that my site was being held hostage, so I didn't want to say anything, but it was at that point that I had decided to switch to a new web hosting provider as soon as I had a backup of my site in hand.

And by gum, that's just what I did.

Media Temple: Killer Icon

I'm currently hosting this site, as well as a few others, on a Media Temple (gs) Grid-Service account. Media Temple is famed for their customer service, which is a big deal considering how rudely I was treated over at WHB. But I've yet to even need MT's customer service. This is mostly due to their phenomenal online KnowledgeBase, which has managed to answer my every question, and believe me, I've had some doozies. Uptime and speed have been acceptable; I've had decent speed — faster than WHB by a smidge perhaps — and only the occasional, short-lived drop-outs, which seems to be about par for the course with consumer-level services. But perhaps best of all, I can't even find MT's acceptable usage policy. They don't seem to place any restrictions on what you can do with your disk space. Sure, there are bandwidth and capacity limits, and the capacity limit is smaller than I had with WHB. But at least now I have a chance of actually hitting it.

It's only been a month. A little early, I realize, to fully endorse Media Temple. But so far, so good.

Today I canceled my Web Hosting Buzz account. Nothing like the taste of sweet, sweet consumer revenge. I just have to wonder, when will companies realize that consumers can and do exercise their freedom of choice? It just doesn't ever pay to treat customers — or, hell, let's call them what they are, people — like shit. There's little I take greater pleasure in than dumping a company that does so.

UPDATE:

Lots of great comments on this post so far. In particular, one reader points out that Media Temple does have a usage policy (I figured!) on their legal page (not in their support pages or KnowledgeBase, which is where I was looking). Of particular interest, said reader points to the following passage:

"75% of customer’s content files stored on Provider’s server must have associated HTML, or PHP files inside the account linking to the content stored on that account."

So, yes, there are some restrictions on the sorts of files that can be stored in your Media Temple account. But I understand this rule. It's there to prevent you from simply using the allotted disk space as storage. Media Temple wants you to use the space to serve websites, not as an online storage repository. Web Hosting Buzz has a similar clause in their policy. But, to be clear, the Web Hosting Buzz policy goes an additional step in limiting the size of the files I can put in my account to a measly 500kb, regardless of whether or not they are linked via HTML, PHP or the like. (For the record, 10% of your files can exceed this limit.) The way I read this is that you can only use your WHB account for serving basic HTML/PHP sites that use mainly text and/or image files, and not particularly large image files at that. And that'd be fine if it were clear from the start, in which case I never would have used them. But, while this policy is buried in an otherwise seemingly reasonable usage policy, WHB boastfully offers 1250GBs of storage on their main page. This is what you see most prominently when you sign up for their service. It's plastered all over their site. But when taking the usage policy into account, it becomes clear that that 1250GBs is pretty impossible to actually use; it would require hundreds of thousands of HTML and image files, more than even the largest websites use. A 1250GB quota suggests, to me anyway, that you can use this space to host decent sized media files like audio and video. But this is clearly not the case. So, yes, I find the offer of a virtually unreachable 1250GB quota misleading. Is WHB intentionally tricking people into purchasing their service in order to make a fast buck? I don't know. And it's very possible that I am misunderstanding something. But my experience certainly made me feel cheated. The second technician I dealt with was neither apologetic about the situation (which was referred to by said technician as a "mistake" on their part for not having caught the overage) nor helpful about a resolution to the problem. I was simply told to remove the problematic files (which would render my website essentially useless) or have my account suspended.

Emotions aside, ultimately the 500kb file size limit is, quite simply, a deal breaker for me. There's no way I can run my other sites with such a restriction in place. So, whether or not WHB is misleading folks, I have no choice but to make changes to my service. Had the WHB tech been a bit more helpful about the situation, a bit more symapthetic, I might have considered upgrading my WHB service to one that could accomodate my needs. Unfortunatley, that's not how things played out.

Thankfully, Media Temple does not seem to have the same sort of restrictions in their usage policy (and, in what is probably a good sign, they do not offer nearly as much disk space, though it's certainly more than enough). But, as I said, the jury's still out. And I'll take, as always, a wait-and-see approach. If I encounter problems, I will take my business elsewhere. But I'm hopeful that, at least for a while, I've found a new home in Media Temple.

UPDATE 2:

I've edited the post for clarity.

Aaaand... We're Back!

So if you've been obsessively checking the site tonight — and you really should have been — you may have noticed a bit of unscheduled downtime. This was just me trying to be clever and failing miserably. See, I've moved to a new web hosting provider, and I wanted desperately to make the transistion seamlessly. Obviously, no such luck. I borked the whole thing up. Majorly. Oh well, I wasn't down too long, and, hey, now I know better.

And, if you're wondering, I'm leaving my old web hosting provider, Web Hosting Buzz. Seems they have a rule that essentially forbids putting "downloadable files" greater than 500 kb. Yeah, that's right. Web Hosting Buzz gives you 1200 GB of storage and then limits you to files 500 kb in size. Sound scammy? I thought so too.

So, The Adventures of Systems Boy! is now living on a Media Temple Grid-Service account. We'll see how it goes. But my initial tests have shown the service to be quite reliable thus far, and I can't find anything that even hints at file size limits. But then, why would I?

Anyway, we're back in business again. Thanks for your patience.

Stats

Sorry for the self-indulgence. I realize that the bulk of posts here have been about the blog itself. This is a passing phase due the the newness of self-publishing. And by passing, I mean it will pass. Promise. That said, one of the great things about self-hosting this site is that I now have easy access to statistics. Even though I'm using one of the cheaper hosting packages, a statistics package is just a click away. I turned it on a few days ago, and now, for the first time in the history of this site, I have stats. And stats, I'm discovering, can yield some really interesting information.

Some of the stuff I find oddly fascinating:

  • My most popular articles since moving are the recent Default Shell Hell, the famed iCal Publising post and the one about Sending Remote Commands via SSH. The first and last of which are pretty insanely geeky.
  • By far, the most popular means of accessing this site is via the Firefox web browser. I find this intriguing as it reflects my own particular preference to a far greater extent than it does actual, real-world browser usage. Oddly, the second most popular way to access this site is through NetNewsWire, which does not reflect my preferences for anything.
  • Heartening, but hardly surprising, is the fact that this site is read primarily by Mac users, or at least by people who are on Macs at the time they read the site.
  • And, finally, I'm quite pleased to see that people are actually still visiting this site, despite all the recent hullabaloo. Over the last couple weeks I've had several thousand hits from a few hundred unique visitors. That's way more than I ever thought were visiting the site, even when I was on Blogger. Neat-o!

At any rate, if anyone happened to visit today, they may have noticed some strange goings-on here at TASB. Yeah, that was me completely breaking — and subsequently restoring — the site. Let's just call it an episode of, "When Good SysAdmins Do Incredibly Stupid Things," and leave it at that. I really don't want to discuss it except to ask one thing: Did Blogger do something to completely break Wordpress's ability to import posts? 'Cause I haven't been able to do that now for a few weeks, and I need to.

In any case, it's always useful to reiterate: Always make a backup. And perhaps it's also useful to make an additional one if you happen not to be at the computer that has the backups on it. You know, before you go screwing around with delete keys and the like.

Okay then. See all 358 of you later.

UPDATE: And, oh yeah, since I totally broke it anyway, I decided to try another new look. I think I like this one better, now that I've had my way with it. A little stuffy, but still, pleasant and appealing.

UPDATE: The trouble importing Blogger to Wordpress is discussed and a solution proffered here on the Wordpress forums. For some reason it seems to work using a Wordpress.com login, but not on my 2.6.1 install. In fact, I think the last time it worked was when I was still at v.2.6, so perhaps this is a 2.6.1 bug. Whatever. I'm kind of over it after yesterday's fiasco.

Meet the New Systems Boy!

Hello everyone! I'm back! Things have been going extremely well at the new job and the new home, and they're finally settling down to a pace at which I find myself able to write. And, what with the new job and all, I've got about a jillion things to write about. But I've been holding off because I finally decided to move the site to my own hosting provider. Using Blogger for the past three years has been great, but there are certain limitations to the platform that I'm starting to feel, and certain advantages to self-hosting that I think I'm ready for.

So, the new site can be found at the exceptionally sensible URL: http://systemsboy.com

New Banner

The site is live and active, and all the content has been easily ported over to Wordpress, thanks to some terrific reader feedback. Though all the old content remains available on the new site, I will also maintain a complete (though unsearchable) archive of the old site (everything including and prior to this article) at: http://systemsboy.com/bloggerarchive

You know. Just in case.

Finally, sometime in the near future (possibly by the end of the week), any Blogger URL on this site will redirect to the new front page. And, of course, following this article, all new content will be posted there as well.

Please feel free to let me know what you think of the new look in the comments, if you're so inclined. And do check back soon for new articles, which should start appearing very shortly.

Cheers!

What's Going On

I've attempted this post twice now, and it never seems to come out right. It's one of those future-of-the-blog type posts that everyone hates so much, but it's kind of a biggie. So here goes attempt number three.

MIA

Regular readers may have noticed the blight of posts lately (with the exception of the pre-programmed Anniversary post). Also, uncharacteristically, comments have gone unanswered. And the missing scripts and site banner have surely been a tip-off that something is amiss. Indeed.

The short version is that I am in the process of moving to a new home, and in the process of transitioning to a new job (which job was offered me on the anniversary of this site, ironically — Universe, you're a riot). As you can imagine, changing up these two things alone changes so many things that fall beneath them in the hierarchy of life. A blog is certainly no exception.

Earthlink Blows

To be a bit more specific — or as specific as I can at this point — the missing banner and downloads are due to my change of home address and subsequent ISP service transfer. Seems when I transferred my cable service to my new home, Earthlink started a whole new account in my name and unceremoniously rendered the entirety of my old account — including every file I'd stored on their FTP server over the past eight years — null and void. Yep. They deleted all my shit without so much as a phone call and charged me for the pleasure. Rat bastards! If I weren't already signed up and so damn frantic already, I'd drop them like a hot potato. Rest assured, I will do so when next I have a chance (as I did with Sprint — how you like me now, Sprint? Bitches!). Earthlink has just lost my 8+ years of business. Maybe not today; maybe not tomorrow; but soon, and for the rest of my life.

The Future

All of this in conjunction with my upcoming change of employ leaves the future of this blog very much in question. For one, without Earthlink, how will I handle the file archive? How will I handle every dead link on my now-three-year-old site? Would I continue to use Blogger for the site? Or should I start running my own site to mitigate such future transitions? Doing so would allow me to update all the broken links en masse fairly easily, but would be extra hassle, responsibility and downtime. Going forward, will I have issues with the new employer? Or maybe I won't. Will I finally be able to reveal my secret identity? What will I blog about? The fame! The fortune! It's downright dizzying!

Or should I just take this as an omen and throw in the towel?

Honestly, I'd like to not do that. And my friends and colleagues tell me that I "have to" keep blogging. So understand that I will be looking hard for ways to continue writing about systems in a public forum such as this. Understand that The Adventures of Systems Boy! is not planning on going away. (And if it ever does I'll post an explanation. This will never be one of those sites where the author just stops writing. I frickin' hate that. Just kill it, man! Jesus!) But please also understand that this transition will require a great deal of thought, planning and effort on my part, particularly if I switch hosts. It will take time. I may not write much for a while. Comments that don't require a response (and maybe even those that do) may go unanswered for some time. And there are likely to be some significant changes to the content of the site. (Suffice to say, the Macintosh platform plays a significantly smaller role at my new job. Linux, anyone? Anyone?)

In the meantime, if anyone has any suggestions regarding a transition such as the one I'm describing, I'm all ears. Otherwise, please feel free to catch up on the past three years worth of posts. I will write more as soon as I'm able, and will update the site periodically as details about its future solidify. Please stay tuned. (God, I finally get what feed readers are good for!)

Okay, I think that covers everything.

Hope to see you all soon!

UPDATE:

The banner is back! Finally! That was bugging the hell out of me.