Hey Dillon,
Please note that sometimes the IP address is different when testing using SSH vs the one used when a website connects over cURL.
Can you please share the output of the command that you ran via SSH (please make sure to remove any sensitive information, or you can also share it via some 3rd party website).
Hello Harish, thank you for your reply.
I didn’t come back immediately as it seemed to work the next day.
I’ve just updated the plugin however and it doesn’t work again, though I didn’t check it before updating…
Once again I get the 503 error.
Below is today’s output over SSH:
Just so you know I can see the API calls at the Mailchimp end….
Thanks
Dillon
* TCP_NODELAY set
* Connected to us16.api.mailchimp.com (104.123.90.126) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
* CAfile: /etc/ssl/cert.pem
CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* 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, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-ECDSA-AES256-GCM-SHA384
* ALPN, server accepted to use http/1.1
* Server certificate:
* subject: C=US; ST=Georgia; L=Atlanta; O=The Rocket Science Group, LLC; OU=IT; CN=wildcardsan.us15.list-manage.com
* start date: Jun 16 00:00:00 2018 GMT
* expire date: Dec 15 12:00:00 2019 GMT
* subjectAltName: host “us16.api.mailchimp.com” matched cert’s “us16.api.mailchimp.com”
* issuer: C=US; O=DigiCert Inc; CN=DigiCert ECC Secure Server CA
* SSL certificate verify ok.
> GET /3.0/?apikey=XXXXXXXXXXXXXXXXXXXXXXXXXXXX HTTP/1.1
> Host: us16.api.mailchimp.com
> User-Agent: curl/7.54.0
> Accept: */*
>
< HTTP/1.1 200 OK
< Server: openresty
< Content-Type: application/json; charset=utf-8
< Content-Length: 3876
< Vary: Accept-Encoding
< X-Request-Id: f981319d-8730-47d0-b706-69679a9a3736
< Link: <https://us16.api.mailchimp.com/schema/3.0/Root.json>; rel=”describedBy”
< Date: Sat, 15 Dec 2018 19:36:16 GMT
< Connection: keep-alive
< Set-Cookie: _AVESTA_ENVIRONMENT=prod; path=/
< Set-Cookie: _mcid=1.29f7a781e843ba54a5586340f2c3b527; expires=Sun, 15-Dec-2019 19:36:16 GMT; Max-Age=31536000; path=/; domain=.mailchimp.com
<
* Connection #0 to host us16.api.mailchimp.com left intact
-
This reply was modified 7 years, 6 months ago by
dillonphoto.
-
This reply was modified 7 years, 6 months ago by
dillonphoto.
Hey Dillon,
As per the logs, it seems the connection with MailChimp.com went through. Can you please ask your web host if a connection using your website over cURL uses the same IP address (IP address of your server) as the connection done via SSH?
Hello,
There have been no replies to this topic, so I’m marking this as resolved. Please do let us know if you’re still experiencing an issue.