Hi , let's encrypt is showing the following errors and i am unable to install SSLcertificate for my server. And even webroot path is correct it showing the below error?

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:techslaim.com

I ran this command: certbot --apache -d techslaim.com -d www.techslaim.com

It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for techslaim.com
http-01 challenge for www.techslaim.com
Enabled Apache rewrite module
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. techslaim.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://techslaim.com/.well-known/acme-challenge/L2weSLqtLmFDIprcP9wixw6XbcI0t7MOLFa-aOou8R0 [2a02:4780:1:1::1:8e32]: “\n\n404 Not Found\n\n

Not Found

\n<p”, www.techslaim.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.techslaim.com/.well-known/acme-challenge/yDor1E1xdAbV6SgeIKjUL_p5CggOQtLwizDIELUjirM [2a02:4780:1:1::1:8e32]: “\n\n404 Not Found\n\n

Not Found

\n<p”

IMPORTANT NOTES:

My web server is (include version): Apache/2.4.29

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

My hosting provider, if applicable, is: hostinger.in

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): certbot 0.31.0

Hi @adarshnbidari

checking your domain you see the problem - https://check-your-website.server-daten.de/?q=techslaim.com

You have ipv4- and ipv6 - addresses:

Host T IP-Address is auth. ∑ Queries ∑ Timeout
techslaim.com A 31.220.62.10 Greenville/South Carolina/United States (US) - HOSTINGER US Hostname: techslaim.com yes 2 0
AAAA 2a02:4780:1:1::1:8e32 Atlanta/Georgia/United States (US) - HOSTINGER US yes
www.techslaim.com C techslaim.com yes 1 0
A 31.220.62.10 Greenville/South Carolina/United States (US) - HOSTINGER US Hostname: techslaim.com yes
AAAA 2a02:4780:1:1::1:8e32 Atlanta/Georgia/United States (US) - HOSTINGER US yes

Letsencrypt sees a “Not Found”, the online tool sees a timeout checking ipv6.

Both is wrong.

  • Is there a country specific filter?
  • Looks like ipv6 isn’t configured

And there is a new certificate:

Issuer not before not after Domain names LE-Duplicate next LE
Let’s Encrypt Authority X3 2019-09-01 2019-11-30 techslaim.com, www.techslaim.com - 2 entries
Let’s Encrypt Authority X3 2019-07-03 2019-10-01 techslaim.com, www.techslaim.com - 2 entries

So it’s not critical.

So fix your ipv6 configuration. Perhaps define a vHost with *, not an ip address. And check, if Listen [::]:80 is defined.

Sir , how can i fix ipv6 configuration?

And is this correct

<VirtualHost *:80>
ServerAdmin techslaim@localhost
ServerName techslaim.com
ServerAlias www.techslaim.com
DocumentRoot /var/www/techslaim/
ErrorLog {APACHE_LOG_DIR}/error.log CustomLog {APACHE_LOG_DIR}/access.log combined

<VirtualHost *:443>
ServerAdmin techslaim@localhost
ServerName techslaim.com
ServerAlias www.techslaim.com
DocumentRoot /var/www/techslaim/
ErrorLog {APACHE_LOG_DIR}/error.log CustomLog {APACHE_LOG_DIR}/access.log combined

You have root access, so check your ip configuration (ifconfig etc.) to find your local ipv6 configuration.

Then use the online tool to check, if your ipv6 answers with the correct content.

If yes, update your dns AAAA entry.

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