Context deadline exceeded when creating certs

I’m getting this error, never issued more than 50 certificates as rate limit specifies

My domain is: aeoncyberdefense.com

I ran this command: certbot certonly -d www.aeoncyberdefense.com -d vpn.aeoncyberdefense.com -d aeoncyberdefense.com --dry-run

It produced this output: urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Error reading HTTP response body: context deadline exceeded

My web server is (include version): Apache 2.4

The operating system my web server runs on is (include version): Linux, Fedora 28

My hosting provider, if applicable, is:

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

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

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

1 Like

Hi @jcalvarez

checking your domain via https://check-your-website.server-daten.de/?q=aeoncyberdefense.com - there is no answer.

Domainname Http-Status redirect Sec. G
http://aeoncyberdefense.com/ 92.176.68.161 -14 10.030 T
Timeout - The operation has timed out
http://www.aeoncyberdefense.com/ 92.176.68.161 -14 10.030 T
Timeout - The operation has timed out
https://aeoncyberdefense.com/ 92.176.68.161 -14 10.013 T
Timeout - The operation has timed out
https://www.aeoncyberdefense.com/ 92.176.68.161 -14 10.030 T
Timeout - The operation has timed out
http://aeoncyberdefense.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 92.176.68.161 -14 10.030 T
Timeout - The operation has timed out
Visible Content:
http://www.aeoncyberdefense.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 92.176.68.161 -14 10.030 T
Timeout - The operation has timed out
Visible Content:

Only timeouts. A working port 80 is required if you want to create a certificate via http validation.

2 Likes

Hello Juergen, thanks for checking. My Firewall was OK, it was the Intrusion Prevention which was blocking the requests. Thank you very much!

2 Likes

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