Solved.
I also submitted a trouble ticket to my web host provider. It took a couple hours, but we corrected the problem.
[1] cPanel had identified a PHP script as malware that blocked all my outgoing ports.
[2] I downloaded the script, then deleted it from my server. I used cPanel to re-open the ports.
[3] When everything was “normal” I revisited my dashboard to update my CleanTalk plugin. I was surprised to discover that ALL my plugins were out of date!!! CleanTalk was the only plugin that squawked and sent me separate instructions to manually update it.
Everything has been updated, and my site’s CleanTalk registration is now active.
__PostMortum__
On my desktop, I renamed the php file to php.xxx, then opened it in notepad. That, and another WP update message in cPanel, helped me figure out what had happened. The bottom line up front is that I did it to myself…
A year ago I acquired a new domain, but I didn’t want to set up an entire hosting account. Instead, on an old domain I created a folder named with the new domain name.
Next, I set up the new domain as an add-on domain to the old domain, then used cPanel to install WordPress. I built and tested the website. Worked well. It was intended to be a “playground,” and I learned a lot.
Fast-forward to this year. I was done with the domain, so I just let it expire. I left WordPress installed in the subdirectory, but it was basically an orphaned site.
Apparently www.remarpro.com (or a plugin) pushed an automatic update. My cPanel Softaculous isolated the installation by writing a temporary script that closed the ports. Softaculous was unable to complete the upgrade because there was no return DNS information.
So, cPanel was hung up with the outgoing ports closed. The upgrade couldn’t go forward, and it didn’t go back.
I removed the file (see above), then forced the ports open through cPanel.
Another lesson learned: clean up! I used Softaculous to uninstall WordPress from the folder, “un-added” the add-on domain, and finally deleted the folder and few remaining files.
Issue resolved: the contributing environment cleaned up, and I hadn’t been hacked!!!
-
This reply was modified 6 years, 9 months ago by RJaggers.