Locked myself out of my website again

Well ya know... old age and computers, you can know just enough to get yourself into trouble.

I was editing my onsite blog and editing a webpage on my site via FrontPage and then for some reason I got the "blue screen of death" on my monitor and my computer restarted.

Yikes! So reopen my brower tabs and got the autosave of my blog post and it wouldn't save. Says that I had to get in touch with the webhost or some such.

As I'm poking about trying to figure out what happened I lose internet access. After an hour of resetting the router, reinstalling the AT&T HighSpeed Internet, and jumping through flaming hoops in a ball gown of cheap toilet paper, humming "O Fortuna" on a kazoo. I still can't update my blog post.



Rats. I can get to Facebook and get encouragment from family and friends, but I got to be able to blog to the WordPress blog on my site and update my web pages.

I go to my cPanel for my website and can't get in there.

I go to my webhost's home page and no go.

Then it dawns on me. This has happened again. If you go through the history of this blog here, the Hide Out, you'll see how many times my IP has been blocked my my webhost firewall. The only time I use this blog is when my website is down and that's usually the cause.

I used a website that hides one's IP address and I can see my website and my blog. So others can see it also. Good. I make effort to update my blog post, no go because I got to pay to do that. I go to my webhost's home page, I can see that, good. I make effort to post a trouble ticket, no go, free use of the cloaking site won't allow that. sigh

Ok, so email to the support team of the webhost will have to do. No big problem. I wasn't doing anything all that critical on my website other than updating the volunteers on the CITY-Computer Moderator page, which I don't think may of the members of CITY-Computer has gone to visit anyway. My blog entry ended at "Good, the update worked." LOL

So here I am again, writing on this blog when my website is unavailable to me. All this has taken about 4 hours to transpire. Let's see how long it takes my webhost to fix what I screwed up.