It produced this output: Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for rmm.aptechnologiesgroup.com
Waiting for verification...
Challenge failed for domain rmm.aptechnologiesgroup.com
http-01 challenge for rmm.aptechnologiesgroup.com
Cleaning up challenges
Some challenges have failed.
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): nginx/1.22.1
The operating system my web server runs on is (include version): Ubuntu 20.04.5 LTS
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):
The version of my client is (e.g. output of certbot --version or `` if you're using Certbot): certbot 0.40.0
It was working but for whatever reason I can't access the site publicly but only locally. I had it working at one point but forever reason it broke and i started from the beginning and can't remember i got it working
I've looking into that and got the same error. I'm stumped on why it's not able to reach out to the public. I've configured a port forward from the internal IP with port 80.
$ nmap rmm.aptechnologiesgroup.com
Starting Nmap 7.80 ( https://nmap.org ) at 2022-11-15 21:09 UTC
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 3.18 seconds
$ nmap -Pn rmm.aptechnologiesgroup.com
Starting Nmap 7.80 ( https://nmap.org ) at 2022-11-15 21:09 UTC
Nmap scan report for rmm.aptechnologiesgroup.com (108.34.212.60)
Host is up (0.085s latency).
rDNS record for 108.34.212.60: pool-108-34-212-60.prvdri.fios.verizon.net
Not shown: 999 filtered ports
PORT STATE SERVICE
9001/tcp open tor-orport
Nmap done: 1 IP address (1 host up) scanned in 59.22 seconds
I'm running a VM hosting this website and it seems i've ran out of certs. I've built and destroyed this server a bit too many times and not realizing that the certs have a rate limit. I would need to wait until the certs expires to try again unfortunately
That's not the correct way to see hitting a rate limit. The correct way of seeing it is: "I've been abusing a free to use, but costly to run service due to lack of knowledge, which is not an excuse."
Yeah, you are right it's not an excuse but I wasn't aware of it and it was a learning curve for me. There was no form of abuse here especially with no malice intentions. I believe among many other techs we all ran into some issues like this at point but learned from it and educate newcomers to not to feel discourage on asking without knowing. Plus it was my own findings that came to the solution of the problem. Learned from my mistakes and moved on. If you would like to point me in the direction on paid SSL to start using a testing for my environment i would be glad to take your recommendations.