The site experienced another 429 “Too Many Requests” error. The whole thing stems from my plan being on a shared server, which I could mitigate by paying for a private one that can handle the traffic. Also, I’m no website administrator– I’m here to post stuff, and all the behind the scenes tech stuff is beyond my poor ability to grok and always will be.
Thing is, this isn’t a revenue generator (I don’t post ads or accept donations) and I need to make a decision on what it’s worth to me. I could bring essentially the same information to a resurrected Blogspot site and just take care not to run afoul of Google censorship which prompted the move to here.
For now, all I can say is if you try to access the site and can’t, I am already working on it. The best “solution” I can offer at this time is go do something else for an hour or two and try again.
Shared servers are the pits. The hosting shop puts some spammer on the same server as you, he spams for a day or so before getting found out and kicked off, then blackhole lists around the world block all mail from YOU to anyone else for a week or more. But I hear you when you say administration is too steep a learning curve. I’ve been a computer guy for 55 years, running my own server for three, and I’m still learning new things I have to know to keep it running.
I’m a cloud architect. Get in touch if you’d like me to take a look at what you’re doing and suggest alternatives.