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.
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.
Cleaning up challenges
Some challenges have failed.
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.
My web server is (include version): unbuntu 20
The operating system my web server runs on is (include version): windows 10
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know): i don't know
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):certbot 2.10.0
The --nginx option you chose uses an HTTP Challenge. This challenge requires your domain to be reachable using HTTP (port 80) from the public internet.
As the message says, the HTTP challenge request failed with a timeout which is likely a firewall blocking access to your server.
This can also be a router or even your ISP blocking these ports. Is this a residential setup?
I am puzzled by these answers. Are you running Ubuntu as a guest VM under Windows 10? If so, you may need to check your port sharing to that VM.
Im currently at work using their internet but I've set up web page before here so I don't understand why it would affect me now. The only thing that is different is I now have Mcafee on my computer as opposed to AVG. But I went into the firewall and created a rule to allow ports 80 and 443.I am running ubuntu on my vm that I created through google cloud.
You should have a working HTTP site before trying to secure it via HTTP-01 authentication.
And you should do your testing on the staging environment [not the LE production environment].
In your screenshot in post #10, your ISP's router is listening on those ports instead of forwarding the traffic to the server that you are running behind it.
