By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

An HTTP request is sent from WooCommerce Webhooks to Amazon API Gateway, this works in 90% of the cases, but occasionally the wrong certificate is returned.

0

When the HTTP request is sent from the WooCommerce webhook to the API gateway, in approx. 10% of the cases we receive the following error and the gateway rejects the webhook:

cURL error 60: SSL: no alternative certificate subject name matches target host name '....execute-api.eu-west-1.amazonaws.com'

We have no authoriser attached to the route.

It seems completely random which ones are rejected, when we retrigger the delivery of the same webhook, it goes through. We have tried updating the cacert.pem on the Wordpress side, with no success...

How can we resolve this issue?

  • Emily
    a year ago

    Thank you very much for your reply! Unfortunately none of these things have resolved the problem. We are not using a custom domain, have updated the libraries, updated to PHP 8, updated the CA certificates, checked the domain name... Do you have any other ideas of what may be causing this? What's really bizarre is that 95% of the requests go through, and we cannot find any pattern dictating which ones receive this error.

Topics
ServerlessFront-End Web & MobileNetworking & Content Delivery
Tags
Amazon API Gateway
Language
English
Emily
asked a year ago360 views
1 Answer
0
  1. If you're using a custom domain for your API Gateway, make sure it's set up properly with the right SSL certificate. In case you're using the default domain provided by Amazon API Gateway, you can ignore this step.
  2. Update both cURL and OpenSSL libraries on your WooCommerce server, as older versions might lead to SSL-related problems. Don't forget to restart the web server after updating to apply the changes.
  3. Double-check the domain name in your WooCommerce webhook configuration, especially if you're using a custom domain for your API Gateway. A small typo or misconfiguration can result in SSL certificate validation errors.
profile picture
EXPERT
Sedat Salman
answered a year ago
  • Emily
    a year ago

    Thank you very much for your reply! Unfortunately none of these things have resolved the problem. We are not using a custom domain, have updated the libraries, updated to PHP 8, updated the CA certificates, checked the domain name... Do you have any other ideas of what may be causing this? What's really bizarre is that 95% of the requests go through, and we cannot find any pattern dictating which ones receive this error.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content