01.18.06
Ranting: godaddy
I have been helping to create a website for my neighbors and their budding music careers. During that process, I am reminded of why web design and development is so frustrating. First, you get the pleasure of dealing with browsers and their intricacies of dealing with the state-of-the-art markup. Next, you get to deal with the fact that a lot of visitors to your site will likely be using older browsers (e.g. Netscape 4 or Internet Explorer 5). Last, you get to deal with topic of my current rant, godaddy.com.
Jer, of brookeANDjer, choose to register his domain with godaddy. After doing so, it seemed logical to go ahead and use them as the web host as well (as opposed to some others like lunarpages or dreamhost). I figured it couldn’t do much harm since most of the hosts are similar and we were not planning on doing much in terms of web applications. This assumption was wrong.
The first experience was not anything to write about but it was annoying. While Jer was walking through the setup process, they provided a very confusing set of options that were not explained well. Not only were they not explained, the page design made it hard to comprehend and make a good decision because it was way to “busy” to allow us to focus on the content (flashing ads, bright colors, etc.). So, we ended up thinking that setting up a shopping cart was a good idea. So, the gripe here is that they should provide good descriptions for items that they want you to purchase and provide an interface/design that makes it easy to see the real content of the page and not distract the user with ads and other “stuff”. Ok, no big deal, really our fault on this and it turned out ok since he got it removed from the account.
The second experience was not that big of a deal and was a result of user error. Jer was trying to get the domain redirection working (they own three domains and want all of them pointing to the same content). He messed with it enough that the site we had uploaded disappeared. It turned out that the management software got confused and started pointing the DNS to the wrong IP (not sure how their infrastructure is setup but it looks like they don’t share a single file-system). So, the files were still there, just not on the machine that DNS pointed to. No big deal, a phone call later and Jer got them to fix it.
The third experience was where it got annoying. They want users to use FTP to upload websites. This is very, very annoying because: 1) the username/password travels in clear-text, and 2) my firewall is setup so that ftp does not work (not on purpose, just chance). So, I had to use their web interface to upload and mess with files until I could find a passive-mode FTP client that allowed this access (that did not take long, just annoying that I have to use a GUI client when I just need to upload files). Ok, this is not a big problem, just annoying (have they not heard about ssh/scp???).
The fourth, and final, experience (to date) happened last night when we wanted to “go live” with the site. To provide a little context, brookeandjer wanted their music to start playing when their website was loaded. To do this, I grabbed an open-source flash-based music player. This music player uses a file format named XSPF (which is just an XML-based format) that describes a playlist. You simply embed the music player in your page and provide it a link to the xspf file and it “just works”. Or rather, it just worked in our development environment (my laptop running Linux/Apache). When I uploaded the site, the music did not play. After several minutes of trouble-shooting the issue I found was that the file could not be found. Double-checked to see that the file existed on the server using ftp (at this point, I was hoping for a shell) and the file was there and had content but using a browser I would get the error code 404 and the wonderful Microsoft IIS error page. Long story short (or rather an hour later), it turns out that godaddy does not serve files that end in xspf but will serve files that end in xml. To fix this issue, I had to change the web pages to point to an xml file and rename the xspf file to an xml file extension. This is just aweful. I would guess that they are blocking unknown file extensions from being used. But is this on purpose? If so, why? If this is not on purpose, how bad of a web host do you have to be to screw this up?
Based upon these experiences, I am officially claiming that godaddy is not a good web host.
Permalink Comments off