• Resolved abruski17

    (@abruski17)


    That’s the error message I keep getting. I had some back and forth with support that never really went anywhere. Hoping to have better luck here. Each of the questions posed to me by the plugin author were forwarded to my host and answered sufficiently. We have them whitelisted and ping tests have already proven successful.

    If CleanTalk wants to actually explain why their stuff isn’t working, we’re all ears.

    • This topic was modified 4 years, 7 months ago by abruski17.
Viewing 15 replies - 1 through 15 (of 60 total)
  • Plugin Author alexandergull

    (@alexandergull)

    Hello @abruski17

    We suppose it may be caused by running the plugin on a staging site.

    Can you try to check the plugin work on a live site? Just check if the error persists.

    If it does not – so you have found a solution. Check your staging site permissions and settings.

    Keep us informed of the result.

    Thread Starter abruski17

    (@abruski17)

    Hi. We would never test something on live that we haven’t tested on staging. This is a professional website, not a 6th grade class project. This will get edited to something less direct if you can provide decent service from here on out.

    • This reply was modified 4 years, 7 months ago by abruski17.
    Plugin Author alexandergull

    (@alexandergull)

    Can you check if allow_url_fopen is enabled in php.ini for staging site?
    Best regards,

    Thread Starter abruski17

    (@abruski17)

    I asked the host and they confirmed that it has been enabled the entire time.

    Plugin Author alexandergull

    (@alexandergull)

    The most important question we have to ask: does the protection work on a staging site? We’d prefer to test it ourselves but we can’t access the staging site.
    It can be easily checked – just try to register or submit a contact form with [email protected]. You should be blocked.
    For now, we are figuring out what else can be a reason for this error.
    Best regards,

    Thread Starter abruski17

    (@abruski17)

    Anything?

    Have you guys checked to make sure .cloud sites can connect? That this hasn’t come up as a use-case scenario already is a little bit frightening for a security plugin.

    Plugin Support SergeM

    (@serge00)

    Hello, @abruski17.

    Yes, “.cloud” websites can connect to the CleanTalk service.

    Perhaps you can create a temporary account for us to check the plugin first-hand? If yes, please, contact us privately via email:
    [email protected]

    Thank you.

    Plugin Author Denis

    (@shagimuratov)

    Hello @abruski17,

    Do you see that message in plugin settings, WordPress admin console or in the site logs?

    It would be great, if you sent us a screenshot with error.

    Thread Starter abruski17

    (@abruski17)

    @shagimuratov No, I figured I’d toss an idea out there since there had been no response.

    @serge00 since my last ticket with your support channel went unresponded to why don’t you guys reply to it and we can go from there.

    Plugin Support SergeM

    (@serge00)

    Done.

    I sent you an email.

    Thread Starter abruski17

    (@abruski17)

    Okay. Let’s see how this goes.

    Thread Starter abruski17

    (@abruski17)

    Anything?

    Plugin Author alexandergull

    (@alexandergull)

    Hello.

    We will send you the fixed version with a few hours

    Thank you

    Thread Starter abruski17

    (@abruski17)

    Hi guys,

    I emailed you yesterday a screenshot showing the same error.

    Plugin Support SergeM

    (@serge00)

    Hello, @abruski17.

    Did you do it after we sent you a fixed archive?

Viewing 15 replies - 1 through 15 (of 60 total)
  • The topic ‘CONNECTION_ERROR : “cURL error 28: Operation timed out after 10001 milliseconds’ is closed to new replies.