Viewing 7 replies - 1 through 7 (of 7 total)
  • Plugin Author Martin Tod

    (@mpntod)

    Historically, this problem has been used by people using the HTTP access module in the Core Control plug-in to switch off cURL.

    Do you have a good connection to the internet from your server?

    Martin

    Thread Starter edvercarraro

    (@edvercarraro)

    Hi Martin,

    I installed the Core Control plug-in and I disabled the cURL, but now it show this:

    Error message received from WordPress: 111: Connection refused. Please verify your connection settings.

    My internet connection is very good. Do you think the problem is on the server?

    Thank’s.

    Plugin Author Martin Tod

    (@mpntod)

    Yes. This would normally mean a problem in the connection from your server to Twitter – not your home internet connection.

    Is your server able to download updates to WordPress plug-ins etc.?

    Martin

    Thread Starter edvercarraro

    (@edvercarraro)

    Martin,

    Yes, my server is enable for all updates.

    I will contact the provider to try to resolve .

    I’m using the Hostinger, and I heard that the Twitter blocked this provider.

    Thank’s.

    Plugin Author Martin Tod

    (@mpntod)

    Good luck. Please let me know if you find a solution.

    Martin

    gabrieldiniz

    (@gabrieldiniz)

    I’m using hostinger too, and got the same error.
    Did you found a solution?

    Plugin Author Martin Tod

    (@mpntod)

    If I understood the issue earlier, I think the implication of edvercarraro‘s post is that Twitter is refusing connections from Hostinger – which would mean there is no solution from Hostinger’s end.

    It may be that Hostinger have sorted this out with Twitter, but, if they haven’t, you would probably need to find a new hosting service.

Viewing 7 replies - 1 through 7 (of 7 total)

The topic ‘Error message received from WordPress: couldn't connect to host.’ is closed to new replies.