• Resolved RJaggers

    (@rjaggers)


    I am getting the following message every 5 seconds as my cleantalk plugin tries to call home to register itself. I have just manually updated the plugin to the latest version…

    “CURL error: ‘Connection timed out after 15001 milliseconds’ or disabled allow_url_fopen in php.ini.”

    Note: I am running cleantalk on another domain with the same host, and that 2nd installation seems to be running error-free: BayshoreTownhomes.com

    Suggestions?

    The page I need help with: [log in to see the link]

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Support SergeM

    (@serge00)

    Hello.

    Thank you for your request.

    Please, give us more details:
    1. The CleanTalk plugin does not call itself. Could you check the connection between your website and the CleanTalk servers:
    78.47.62.84
    78.47.96.11
    88.198.153.60
    138.68.234.8
    159.203.121.181
    162.243.144.175

    2. Tell us where do you see the error? Is it in your webserver logs or in your WP backend?

    Write back anytime. Sorry for the inconveniences.

    Your CleanTalk Control Panel: [ https://cleantalk.org/my/ ].

    Best regards.

    Thread Starter RJaggers

    (@rjaggers)

    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.
    Plugin Support SergeM

    (@serge00)

    We are glad to hear that everything turned out well.

    If you have any issues with the CleanTalk plugins contact us anytime.

    Your CleanTalk Control Panel: [ https://cleantalk.org/my/ ].

    All the best.

    Thread Starter RJaggers

    (@rjaggers)

    It was CleanTalk that alerted me to the problem. CleanTalk monitors the version that users have. They provide instructions on how to update using a zip file. When even that failed, I had to look more closely!

    Thank you.

    Plugin Support sergecleantalk

    (@sergecleantalk)

    You are always welcome!

    Feel free to contact us.

    Best regards

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘WP Error Message for plug-in’ is closed to new replies.