• Resolved Gustavo Cieslar

    (@gustavodc)


    Hello!

    we have been using your plugin in our website slator.com for a couple of months without any problem, but it suddenly disconnected from Mailchimp. We now receive the 403 Forbidden error response: screenshot

    I read a related ticket also called “Forbidden 403” but we couldn’t find a solution in it. I run the curl command and we get a HTTP/1.1 200 OK response:


    -bash-4.2$ curl -v https://us10.api.mailchimp.com/3.0/?apikey=xxxxxxxxxxxxxxxxx-us10
    * Trying 23.212.33.79...
    * Connected to us10.api.mailchimp.com (23.212.33.79) port 443 (#0)
    * Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
    * successfully set certificate verify locations:
    * CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
    * TLSv1.2 (OUT), TLS handshake, Client hello (1):
    * TLSv1.2 (IN), TLS handshake, Server hello (2):
    * NPN, negotiated HTTP1.1
    * TLSv1.2 (IN), TLS handshake, Certificate (11):
    * TLSv1.2 (IN), TLS handshake, Server key exchange (12):
    * TLSv1.2 (IN), TLS handshake, Server finished (14):
    * TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
    * TLSv1.2 (OUT), TLS change cipher, Client hello (1):
    * TLSv1.2 (OUT), TLS handshake, Unknown (67):
    * TLSv1.2 (OUT), TLS handshake, Finished (20):
    * TLSv1.2 (IN), TLS change cipher, Client hello (1):
    * TLSv1.2 (IN), TLS handshake, Finished (20):
    * SSL connection using TLSv1.2 / ECDHE-RSA-AES128-GCM-SHA256
    * Server certificate:
    * subject: C=US; ST=GA; L=Atlanta; O=ROCKET SCIENCE GROUP; OU=Rocket Science Group; CN=*.api.mailchimp.com
    * start date: Sep 22 14:39:14 2015 GMT
    * expire date: Sep 22 14:39:13 2016 GMT
    * subjectAltName: us10.api.mailchimp.com matched
    * issuer: C=NL; L=Amsterdam; O=Verizon Enterprise Solutions; OU=Cybertrust; CN=Verizon Akamai SureServer CA G14-SHA2
    * SSL certificate verify ok.
    > GET /3.0/?apikey=3f271a8e395cf41f18a5dccfb7bf5a60-us10 HTTP/1.1
    > Host: us10.api.mailchimp.com
    > User-Agent: curl/7.45.0
    > Accept: */*
    >
    < HTTP/1.1 200 OK
    < Server: nginx
    < Content-Type: application/json; charset=utf-8
    < Content-Length: 2900
    < Vary: Accept-Encoding
    < X-Request-Id: 24294df5-d48c-4044-aea1-8fe214986033
    < Link: <https://us10.api.mailchimp.com/schema/3.0/Root.json>; rel="describedBy"
    < Date: Thu, 21 Jan 2016 17:54:44 GMT
    < Connection: keep-alive
    <
    {"account_id":"2f420a68098......

    We also contacted Mailchimp’s support and they said:

    “When the cURL command was run, we were seeing a response of 200 OK, which shows that our system is able to give a positive response when connecting to that IP address.
    With that said, we definitely want to investigate why the 403 error is appearing. In order to do so, we’re going to need the reference number associated with the 403 forbidden error. In order to get this reference number, you might want to reach out to the developer of the plugin to see if they can provide that information.”

    Could you provide us the “reference number”? Any idea of what the problem could be? Our host is MediaTemple.

    Many thanks for your help.

    Kind regards,

    Gustavo

    https://ww.wp.xz.cn/plugins/mailchimp-for-wp/

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Danny van Kooten

    (@dvankooten)

    Hi Gustavo,

    Are you 100% certain that you’re running the CURL command from the same server (and ultimately: IP Address) that the plugin is installed on?

    The response should get you the same response as the response the plugin gets, and then show you the reference number.

    We made some adjustments to the plugin a few days ago that will show you the reference number. We haven’t yet released those changes but you can download the development version of the plugin here: https://github.com/ibericode/mailchimp-for-wordpress/archive/master.zip .

    Hope that helps. If not, let me know!

    Thread Starter Gustavo Cieslar

    (@gustavodc)

    Hi Danny,

    thanks for your quick answer.

    Yes, I’m running the CURL command on a SSH access on the same account where the plugin is running.

    But, today we entered into the plugin settings and we saw that it’s connected again. The same happened a couple of weeks ago. It was disconnected (Forbidden 403) for one or two days, and then suddenly reconnected. So, I don’t know how log this status will last.

    I’ll upload the plugin update you sent me, and I’ll let you know if we have new issues.

    Thanks.
    Cheers!

    Thread Starter Gustavo Cieslar

    (@gustavodc)

    Hi there!

    the good news lasted just a couple of days. For the last two weeks it was disconnected again (403 forbidden). I updated the plugin to 3.1.1 but I don’t see the Akamai firewall reference number.

    I run the curl command (on same server) and I get 200 OK response.

    I installed the plugin in a different website/server and it connects fine using the same API key.

    It’s strange that the curl command gives 200 OK response but the plugin can’t connect. Any ideas of what can I check?

    Thanks!

    Gustavo

    Plugin Author Danny van Kooten

    (@dvankooten)

    Hi Gustavo,

    Ugh, that sucks. I’m not sure why the plugin response would differ from the CURL command on the same server, Akamai blocks by IP address (afaik) so it should be the same response… It could be the user agent that WordPress sets?

    Would it be possible for me to take a closer look at this in private? You can reach us at [email protected], I’d love to do some debugging on this so we can tackle it in a better way..

    Thanks in advance!

    Thread Starter Gustavo Cieslar

    (@gustavodc)

    Hi Danny,

    when we installed a SSL Certificate one month ago, it connected and we had no problems since then.

    Thanks anyway!!

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

The topic ‘Forbidden 403 – Reference number’ is closed to new replies.