Cannot get a certificate for website - "unauthorized"

My domain is:
jakraft.xyz
I ran this command:
certbot --nginx -d jakraft.xyz
It produced this output:

Domain: jakraft.xyz
   Type:   unauthorized
   Detail: 2001:19f0:7402:14:5400:4ff:fe24:8c9e: Invalid response from
   http://jakraft.xyz/.well-known/acme-challenge/81yP1WAFOzOkAE8akJoWFXB936S2MlA89JfJwTvBims:
   404

   To fix these errors, please make sure that your domain name was
   entered correctly and the DNS A/AAAA record(s) for that domain
   contain(s) the right IP address.

My web server is (include version):
Nginx 1.18.0
The operating system my web server runs on is (include version):
Debian 10
My hosting provider, if applicable, is:
Vultr
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 1.12.0

I go to jakraft.xyz just fine, except it isnt http, since i didnt setup ssl yet. but for some reason i get the unauthorized error. i have both A and AAAA records pointing to my server, so that isnt the issue.

Here is my Nginx configuration:

server {
    listen 80;
    #listen [::]:80;

    server_name jakraft.xyz

    root /var/www/jakraft.xyz;
    index index.html;
}

If you need any more info let me know

your nginx configuration is missing a semicolon at the server_name line. I assume nginx won't like that and can refuse to restart/reload.

2 Likes

yep, i noticed that right after posting! i added a semicolon and atleast the index page seems to show up, but still certbot doesnt work.

Also: your server block isn't responding on ipv6 because you told it not to. :smiley:

Uncomment that line.

2 Likes

ah, i dont know how i missed that....
thanks!

2 Likes