I'm unable to create certificate

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: uwitu.me

I ran this command: certbot --apache -d uwitu.me

It produced this output:

Failed authorization procedure. uwitu.me (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://uwitu.me/.well-known/acme-challenge/44xcOsxaX0q0l8lHzFcQAayU8Q9MOJu0m59N2ON5LWY [2001:8d8:100f:f000::25a]: 204

My web server is (include version):
Server version: Apache/2.4.29 (Ubuntu)
Server built: 2019-04-03T13:22:37

The operating system my web server runs on is (include version):
Ubuntu 18.04.02 LTS (GNU/Linux 4.15.0-47-generic x86_64)

My hosting provider, if applicable, is: Digital Ocean

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 @HenryMehta

you have ipv4- and ipv6 - addresses ( https://check-your-website.server-daten.de/?q=uwitu.me ):

Host T IP-Address is auth. ∑ Queries ∑ Timeout
uwitu.me A 178.62.86.124 yes 1 0
AAAA 2001:8d8:100f:f000::25a yes
www.uwitu.me A 178.62.86.124 yes 1 0
AAAA 2001:8d8:100f:f000::25a yes

But your ipv6 doesn't work. Checking the standard urls you see the result:

Domainname Http-Status redirect Sec. G
http://uwitu.me/
178.62.86.124 403 0.050 M
Forbidden
http://uwitu.me/
2001:8d8:100f:f000::25a 403 0.066 M
Forbidden
http://www.uwitu.me/
178.62.86.124 403 0.050 M
Forbidden
http://www.uwitu.me/
2001:8d8:100f:f000::25a 403 0.070 M
Forbidden
https://uwitu.me/
178.62.86.124 -14 10.023 T
Timeout - The operation has timed out
https://uwitu.me/
2001:8d8:100f:f000::25a -10 0.046 P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.
https://www.uwitu.me/
178.62.86.124 -14 10.026 T
Timeout - The operation has timed out
https://www.uwitu.me/
2001:8d8:100f:f000::25a -10 0.046 P
SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel.
http://uwitu.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
178.62.86.124 403 0.054 M
Forbidden
Visible Content: Forbidden You don't have permission to access /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de on this server. Apache/2.4.29 (Ubuntu) Server at uwitu.me Port 80
http://uwitu.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:8d8:100f:f000::25a 204 0.057 A
Visible Content:
http://www.uwitu.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
178.62.86.124 403 0.047 M
Forbidden
Visible Content: Forbidden You don't have permission to access /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de on this server. Apache/2.4.29 (Ubuntu) Server at www.uwitu.me Port 80
http://www.uwitu.me/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de
2001:8d8:100f:f000::25a 204 0.053 A

Certbot creates a file in /.well-known/acme-challenge, Letsencrypt tries to check that file and prefers ipv6.

But your http + ipv6 sends a http status 204 - created, not the content of the file or (checking a not existing file) the expected http status 404 - Not Found.

So

  • fix your ipv6-config (or)
  • remove your ipv6 dns entry (the AAAA entry), create a certificate, then try to fix your ipv6, then add the dns entry

Using my online tool you can check your ipv6 without a dns entry - https://check-your-website.server-daten.de/?q=2001%3A8d8%3A100f%3Af000%3A%3A25a&h=uwitu.me

The ipv6 a query, the domainname as hostname.

So the visitors of your website use ipv4 and see the page, you can check your ipv6 config.