Kelly, the Buffalo-area guy, posted about going to the moon. And then nothing for a couple of weeks. I thought that Ralph Kramden had assaulted him.
As it turned out, his blog was full. Specifically, “I have been unable to access my site on the back end for over a week, because the database was full. I’m not entirely sure what that means, but I think it’s that after over 24 years of blogging, I finally filled up the space I’ve been paying for here. (Well, I was on BlogSpot for years and years, but I ported all of that content over here.)” I assumed he was physically all right; he had posted on Facebook.
This, of course, got me to start wondering about the state of the blog at rogerogreen.com. Lessse, what IS the name of my provider? (It really DID take me a minute to remember.)
No threats from viruses – yay! I had an entity fix a hack attack in 2024 and spent $30/year to maintain it.
“This certificate is valid and currently in use; it will automatically renew.”
My storage is at 30%; that’s comforting, given that I have imported not only MY Blogspot blog from 2005 to 2010, but also my Times Union blog from 2008 to 2021, though I didn’t blog there daily.
My CPU is only 4%. But my RAM is at 90%. I had this problem six months ago, and it was fixed. Also, I bought extra RAM. Do I understand what was done? Do you understand the grown-ups in a Charlie Brown cartoon? I’ll have to keep monitoring it and ask for help again.
Bill coming due
Ooo, I switched to this hosting plan in March 2017 based on a recommendation by the late Dustbury. I spent a bit of change back then. It expires in March 2027. Can I renew for another decade? I cannot. The longest available option is 36 months. Of course, the three years will cost 70% of what the ten years have run me.
I suppose it’s the cost of therapy.
One other thing: I have the Jetpack plugin. But it’s not responding as it did before, when it would tell me each morning whether my blog had been posted or had gone down. After “talking” with Jetpack’s bot, I wrote to my provider:
Hello, Support – I am experiencing an issue with Jetpack on my WordPress site, and it seems that XML–RPC access is being blocked. Here are the details: – The xmlrpc.php file returns no response at all. – Jetpack backups require XML–RPC to be enabled. – A “200” error is indicated in Jetpack‘s connection test, suggesting XML-RPC is blocked at the server level. Could you please check your firewall/security settings for any XML-RPC blocks? It would be appreciated if you could whitelist XML-RPC access for my site or adjust the security settings to allow it. Thank you for your assistance.
I barely know what I just wrote, but it was in my provider’s queue. Long answer (involving six emails and a few hours), after disconnecting Blackhole for Bad Bots, Really Simple SSL, and, surprisingly, Jetpack Protect, my Jetpack is finally working, which made me happy.