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.
I ran this command: sudo certbot --nginx -d www.alexgrow.biz -d alexgrow.biz
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Requesting a certificate for www.alexgrow.biz and alexgrow.biz
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Detail: Invalid response from http://alexgrow.biz/.well-known/acme-challenge/6BG9GOa9zXG0bWIZRkSvr59Vs7t_L4KI5_wRXJNGiXw [2a03:b0c0:3:d0::11a3:1001]: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx/1.18.0 (Ub"
Detail: Invalid response from http://www.alexgrow.biz/.well-known/acme-challenge/o6kI9sdIEJLckX84THFAd1D-Qbh-MsLr8C-9VuQ9Cxo [2a03:b0c0:3:d0::11a3:1001]: "<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx/1.18.0 (Ub"
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): Ubuntu 20.04.3 LTS
The operating system my web server runs on is (include version): GNU/Linux 5.4.0-81-generic x86_64
Ooh, thx very much!
But why i have problem with my IPv6? I have been add this ip in my control panell on digital ocean (screen, if u can see: this different domain on the same server and have same IPv6 width letsencrypt cert). I have several domains on server and do same with each domains and had no problems. But this domain is explode my brain
Sorry, I meant the file alexgrow, the nginx configuration file didn't have .biz on the end, my bad. I've edited my post above. Please show the contents of the file (the files shown now are symbolic links to the actual configuration files in /sites-available/, you should be able to open the file alexgrow and see the contents to put here.)
Hm, strange, the two listen directives for port 80 and port 443 are essentially the same. But for some reason HTTP on port 80 works good, both IPv4 and IPv6, while HTTPS on port 443 works for IPv6 but not for IPv4? WEIRD!
You could try to add ipv6only=off to the listen [::]:443 directive, but I'm not sure why that wouldn't be necessary for the port 80 listen directive..