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:
pressurewash.io
I ran this command:
sudo certbot certonly --webroot --webroot-path /tmp/letsencrypt/ --dry-run -d pressurewash.io
It produced this output:
-
The following errors were reported by the server:
Domain: pressurewash.io
Type: connection
Detail: Fetching
http://pressurewash.io/.well-known/acme-challenge/CMIjiAak0xRXbppBAnFU6lYVz8bcff-5-bAOtgh_Poc:
Timeout during connect (likely firewall problem)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. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you’re using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
My web server is (include version):
golang standalone
The operating system my web server runs on is (include version):
centos7 latest
My hosting provider, if applicable, is:
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):
0.31.0
Extra information: I was having trouble getting certbot to work for me, and so i searched and found this tutorial. I expected it to work since i can readily access pressurewash.io when running the backend, and i figured this would resolve some of my port 80 problems. Sadly, no, this is the same error i got earlier. I followed this guide exactly, and it still has timeout error.
📄 Adding webroot support to your existing Go/Golang server