ERR 111: Connection refused !!!!

  • MadArtOrigin

    (@madartorigin)


    13 years, 2 months ago

    Good morning Sir,

    I get in touch with you because I have found a problem in the integrating of an API key about a wordpress’s plugin.

    It seems that the problem is about the hosting’site, which should open a port.

    The site shows me this messagge:
    “Uh-oh, we were unable to verify your API Key. Please check them and try again!
    The server said:Could not connect (ERR 111: Connection refused)”.

    I’ve searched in your site and I have found this answer (http://ww.wp.xz.cn/support/topic/plugin-mailchimp-list-subscribe-form-api-key-problem-mine-works-but-hers-does-not):

    “Hi Eric,
    yea I resolved it. It turned out the server host had blocked some ports.
    My API key worked but my clients didn’t. And it turned out it had something to do with a port (or set of ports) being blocked by the host.
    Good luck!”

    For this reason, I have got in touch with my hosting and he answers me the following:

    “Good morning,
    we have opened this IP: 184.173.175.192 in two ports: 80 and 443. This is the IP of the Url api.mailchimp.com.
    You should ask to the plugin’s developer if we have to open or to do something else, because in our opinion there shouldn’t be other problems”.

    Could you tell me what I have to do now?
    I’ve tried again but the problem persists.
    Thanks for your attention.
    Awaiting your kind answer,

    Best regards.

    http://ww.wp.xz.cn/extend/plugins/mailchimp/

Viewing 1 replies (of 1 total)
  • mc_tak

    (@mc_tak)

    13 years, 1 month ago

    Thanks for posting to the forum, and sorry to hear about the issues that you’re seeing. To confirm, this error message does generally indicate that the host is blocking ports, which is causing the outgoing calls (in this case, the call to validate the API key) to fail.

    The ports that our plugin should be using are port 80 for a non-secure connection, and port 443 for a secure connection. If you’re continuing to see issues, it’s possible that the IP address that you mentioned above, isn’t the correct one that you want to use.

    When deciding which IP to open up, you’ll want to use your specific MailChimp datacenter’s endpoint. So, for instance, us6.api.mailchimp.com is currently 108.168.210.218. The datacenter can be verified in the URL of your account after you login, or in the API key that you’re using. In the example above, the datacenter is “us6”.

    It’s generally recommended to not rely on this method though, as these IP addresses can change at any time, without notice. So you might see issues come up later in the future.

    If you’re still seeing issues, feel free to email me at mailchimptk[at]gmail.com and notify me of your MailChimp username. I can use that to login on my end and give the connection a try, to ensure that everything is working and it is indeed a local issue with the environment.

    -tk

Viewing 1 replies (of 1 total)

The topic ‘ERR 111: Connection refused !!!!’ is closed to new replies.