TLS Failure in web-hook response

I’m using stripe web-hooks and it gives me TLS Failure in response when web-hook is triggered.
it looks like the DNS CAA is missing, also there looks to be a chain issue.

My Domain name is: https://api.test.numuworld.com

I ran web-hooks on this domain

Output : TLS Failure

My API is running on AWS

Certbot version 0.30.2

Hi @MusabAkram

please answer the following questions. That’s the template of #help


Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot):

Your certificate is good (output from https://check-your-website.server-daten.de/?q=api.test.numuworld.com ):

CN=api.test.numuworld.com
	19.03.2019
	17.06.2019
expires in 61 days	api.test.numuworld.com - 1 entry

But your chain is incomplete:

Chain - incomplete
1 CN=api.test.numuworld.com

Your server doesn’t send the intermediate certificate. Check, if you are able to send fullchain.pem (instead of cert.pem).

The domain

CAA - Entries

Domainname flag Name Value ∑ Queries ∑ Timeout
d2ddjon14bbsx5.cloudfront.net 0 no CAA entry found 1 0
api.test.numuworld.com 0 no CAA entry found 1 0

doesn’t have a CAA entry. But this is only relevant if you create a new certificate.

But I don’t know the details of “stripe web-hooks”, so I don’t know if there is a CAA entry required. If a CAA entry is required, it’s a non-standard usage of a CAA entry.

Perhaps add a redirect http -> https.

Domainname Http-Status redirect Sec. G
http://api.test.numuworld.com/
52.211.168.186 200 0.170 H
https://api.test.numuworld.com/
52.211.168.186 200 0.827 B
1 Like

Thank you issue resolved.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.