While you didn’t notice because the basic site was up, I’ve been dealing with some backend routing problems at my host.
I have learned that I should just wait, because every time I devised a work around, they had devised another that defeated mine. Sigh, I’m not patient when I want to rant.
On-line Opinion Magazine featuring annoyed rumblings from the leading edge of the Baby Boom firmly tied to a reality-based world.
Established: 21 November 2004
The opinions expressed in Comments are those of the individuals making them. Truly absurd comments and opinions are subject to being cruelly mocked, but "flame wars" will take place on someone else's dime.
Your first comment, all comments with extensive links, and random comments that the software decides it doesn't like for no discernible reason will be held for moderation.
[Be aware that for unknown reasons the software rejects comments shorter than 15 characters, so if you want to leave a short comment fill the gap with periods ........]
8 comments
“…backend routing problems at my host…”
*WHEW* this techno-dweeb would be having a headache JUST thinking about it!
Usually I just count on distracting those Vicious Attack Internets with PIE (any PIE you have on hand ought to do it – VCI’s are not picky!) *wink*
(p.s. I miss fafblog!)
oops…that ought to say VAI’s are not picky (Ah – another day in the life of the Queen of Typos). 🙂
I’m on the same host, but based on their support page, I think I slept through just about all of the problem.
Karen, I am not among the Vicious Attack Internets, but you’re welcome to distract me with PIE if you have any left over. I’m not picky, either. 🙂
I use cookies and coffee, Karen, lots of coffee because it’s cold here at the moment.
They’ve made some changes to IP addresses and they haven’t propagated, so my FTP program doesn’t work. I can upload other ways, but I’ll have to go back and clean up later.
The sites were visible, but the administration functions of WordPress didn’t work because some of the PHP files weren’t reachable. The site was visible and comments worked, but I couldn’t upload new content.
More cookies.
They’ve made some changes to IP addresses and they haven’t propagated…
Now there’s a surprise… I’d have thought Florida, if anywhere, would be a place to find a propagator.
By the time I was aware of the problem, my FTP was working. It sounds from our host’s explanation on the support page as if this is truly not their fault.
They don’t control the routing and I would assume that their host controls the DNS that gets seen first, so we have to wait until all of the routers find the new addresses. It’s a pain, but the site was up and usable. It doesn’t do any good to be able to post what no one can read, so this was better than a situation where I could post but no one else could read it.
My former host… this is part of the reason they are former… put up an older version of the YDD home page during Hurricane Rita. That’s right… they put up a page no less than a week old, and left it there during the storm and several days thereafter. And I was paying for that hosting as a low-bandwidth commercial site; it wasn’t free. I’m glad I wasn’t selling something that had highly variable prices on it.
You are absolutely right: it is better to be able to see the current site but not post to it than it is to have the reverse of that situation. Our current host has, on the whole, been more reliable… and much, much cheaper… than my previous host. Besides, they have the good sense to offer PHP (the previous host offered only Perl), so I can practice skills I need to learn.
I remember the Rita problem and thought it was odd to revert to an older version. That must have been a back-up server.
The PhP/MySQL is pretty standard these days especially in commercial development and you have to be able to test.
Everything is back to normal, and from the notes on the problem I get the feeling that the same error won’t occur again.