SSL Certificate Issue: Error with Certbot and Nginx Authentication

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. crt.sh | 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:
frozenassassine.de

I ran this command:

sudo certbot --nginx

It produced this output:

Requesting a certificate for frozenassassine.de and www.frozenassassine.de
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
  Domain: frozenassassine.de
  Type:   unauthorized
  Detail: 2606:50c0:8002::153: Invalid response from http://frozenassassine.de/.well-known/acme-challenge/CCUe4cqq34IrN1iWJShOmFFNgS1girldFDOkywi-LUk: 404

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

My web server is (include version):

nginx/1.18.0 (Ubuntu)

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

Ubuntu 22.04.2 LTS

My hosting provider, if applicable, is:

Ionos for the Server and Strato for the domain

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 2.8.0

Welcome to the community @FrozenAssassine

Looks like your DNS AAAA record for IPv6 is pointing at a github server and not nginx. The --nginx plugin option you chose only works with nginx.

Your DNS A record points to an nginx server so your IPv6 address is probably just wrong. Best to update it for the correct address and try again.

Many ways to determine that address but one if by running this command

curl -6 https://ifconfig.io

If that fails then you probably don't have IPv6 enabled so should then remove the AAAA record (or fix IPv6)

4 Likes

Thank you very much, totally forgot to change that back from Github. Now everything is working as expected. :smile:

3 Likes

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