Forum Replies Created

Viewing 1 replies (of 1 total)
  • Hello,
    Same problem here. I followed your instruction on diagnosing the problem, and below you will find the result from curl -v -X GET command I run on web hosting server. (Its a shared hosting server with dedicated IP).

    enpangr@wayne [~]# curl -v -X GET https://{us18}.api.mailchimp.com/3.0/ecommerce/stores?apikey={98*************************bbac-us18}
    * About to connect() to us18.api.mailchimp.com port 443 (#0)
    * Trying 96.7.201.18… connected
    * Connected to us18.api.mailchimp.com (96.7.201.18) port 443 (#0)
    * Initializing NSS with certpath: sql:/etc/pki/nssdb
    * CAfile: /etc/pki/tls/certs/ca-bundle.crt
    CApath: none
    * SSL connection using TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
    * Server certificate:
    * subject: CN=wildcardsan2.mailchimp.com,OU=IT,O=”The Rocket Science Group, LLC”,L=Atlanta,ST=Georgia,C=US
    * start date: May 09 00:00:00 2018 GMT
    * expire date: Sep 07 12:00:00 2019 GMT
    * common name: wildcardsan2.mailchimp.com
    * issuer: CN=DigiCert ECC Secure Server CA,O=DigiCert Inc,C=US
    > GET /3.0/ecommerce/stores?apikey=98c989b8765e1a1ee2c8bd24ba68bbac-us18 HTTP/1.1
    > User-Agent: curl/7.19.7 (x86_64-redhat-linux-gnu) libcurl/7.19.7 NSS/3.27.1 zlib/1.2.3 libidn/1.18 libssh2/1.4.2
    > Host: us18.api.mailchimp.com
    > Accept: */*
    >
    < HTTP/1.1 503 Service Unavailable
    < Server: Apache
    < Content-Length: 126
    < Content-Type: application/json
    < ETag: “953d389c654d003dd7a67b8f959df97a:1452000673”
    < Cache-Control: max-age=52939
    < Date: Thu, 28 Feb 2019 10:49:46 GMT
    < Connection: keep-alive
    <
    * Connection #0 to host us18.api.mailchimp.com left intact
    * Closing connection #0
    {“type”:”akamai_error_message”,”title”:”akamai_503″,”status”:503,”ref_no”:”Reference Number: 00.d82bf648.1551350986.47a807a2″}

    I have also contacted MailChimp, so below is their reply regarding our servers IP address reply :

    TJ (Mailchimp)
    Feb 26, 11:26 AM EST
    Hello –

    Thanks for reaching back out and providing your IP address – I don’t see a block on your IP so that’s good. But I do understand you may still be seeing errors and it would be helpful if you’re able to rerun whatever process you used that generated the first TXT error log you enclosed. I’d like to see a new Reference number so I can check the reason why Akamai may be blocking the API commands.

    Following this reply, I run a curl GET command and sent them the results. Their answer was as following:

    TJ (Mailchimp)
    Feb 27, 12:37 PM EST
    Hello –

    Thank you so much for getting that reference code – that was helpful in trying to troubleshoot this issue.

    It looks like the reason the API calls are being blocked are because of a Reputation bock. It looks like some SQL injections coming from that IP address. You may have a script or program that’s doing something that may appear to be doing something malicious.

    If it’s happening with multiple dedicated IP addresses, then you’ll want to check the integration, etc. to review what type of actions it’s taking.

    Your host provider may be able to determine the source of those SQL injections, so I’d recommend reaching back out to them. Please let me know if you have further questions on this!

    Thanks,
    TJ

    Thinking of the last reply from MailChimp, what comes in my mind is that the company who was assigned the development of the web site, has an identical web site running on their servers. This version works as expected without any problems.
    So I thought of the possibility that the fact of using the same API key from two different IPs, it is being recognized as an attack so our IP has been blocked.
    I created a new API key and set it up in our web site only, but with no luck till now.

    Now I am stuck !

    Any ideas ?

    Thank you in advance.

    Sincerely,
    Stamatis

Viewing 1 replies (of 1 total)