Breaking news
Jan 4th, 2008 by handolio
Recent experience suggests that I’ve lost my IT mojo: that silicon and I are no longer on speaking terms. And yet, I persist in fooling around with forces more powerful than I can imagine.
First it was the broadband upgrade, then a tedious episode over Christmas that started out as an attempt to breathe new life into an ageing desktop PC. Now, Hackbash falls under my ruinous focus.
And so, over this weekend, I’ll be buggering about with our hosting. If all goes well a newer, better Hackbash awaits.
If all unravels with a tedious and crushing predictability, well, don’t say I didn’t warn you.
*Glances around at walls and celiling*
Everything appears to be online and well. Did you get caught up in the Fasthosts hacking / password reset nonsense?
Tom
Whoah, how did you do that? You must be, like, the only person in the world that it’s working for at the moment, and stuff?
We’ve moved from hosting on wordpress.com to a self-hosted wordpress install. There was a problem getting the DNS records changed over the weekend, but now they’ve been updated the site seems to be totally broken: I’m only able to get at it using the default web host’s address.
Did you access it at http://blog.hackbash.com?
When I wrote that, everything was fine and dandy. Later that day blog.hackbash.com disappeared, and it still doesn’t work now. I figured maybe my comment had jinxed the system
The recent comments thing seems to have gone odd, too?
I still don’t understand how come you’re able to leave comments when the site’s not working – I have to come to the dev address to do it.
*science_bit*
The comments look inconsistent because they were left at the WordPress hosted blog which is still live, just no longer at blog.hackbash.com.
You (somehow) are managing to see the new, self-hosted blog (which runs in WordPress software still), but which isn’t yet live at blog.hackbash.com. It’s technically an entirely different blog, even if I’ve imported all the other content and tried to get it looking the same.
Anyway, the DNS changes have now propagated across, which means that the site is now equally broken, no matter where you are in the world. I think the remaining problem is a config issue with my webspace – I’ve asked the hosts to check everything at their end, and I’m hoping they find a problem that’s easily fixed, because we’ve been out of action for a couple of days now
*/science_bit*
Ah – all becomes clear. I could comment because I have magic web donkey skills*.
Looks like everything’s fine now, though. I’ve been impressed by how well self-hosted WordPress ticks along – upgraded my installation last weekend and it was surprisingly problem-free (crosses fingers, toes etc
Tom
*DNS record plus guesswork plus browser history = magic web donkey skills.
All hail Tom’s magic web donkey.
I’m happy now that it’s working. Hope to make some improvements over the next little while, but that was definitely the first on the list.