This was the same command as before.
However, the too frequent requests may be a clue. I've run into that once before, and made changes to avoid that. However, doing manual testing may well have exceeded the limit.
Yes, when I'm not actually running the certbot command, my local firewall blocks bad CIDRs. As I mentioned earlier ipfw is stoped when a certbot challenge is performed. It has since been restarted giving predictable results. nginx also normally blocks the majority of the internet (i.e. places I would not try to access my server from). However, I have disabled the nginx ip block list until I find some solution to my cert renewal issue.
If you show us the full output from the command we can help interpret the results.
1 Like
As this server is for personal use, I threw in the towel and generated a self signed certificate.
This is unfortunate, as I had successfully used certbot on this machine for many years and have been maintaining the MacPorts certbot port (before switching to new hardware and FreeBSD, my previous server was running macOS).
Have you considered moving to a DNS-01 challenge?
1 Like
No. I was not familiar with that option.
A quick look at the list of providers who integrate with Let's Encrypt validation showed that my DNS provider was not there. It's a bit strange, as I have Dreamhost provide Let's Encrypt certificates for the sites I host there.
Which list did you look at?
Because while I don't see Dreamhost supported by Certbot there are many other ACME Clients you can use.
This one, for example, supports Dreamhost: DNS Providers :: Let’s Encrypt client and ACME library written in Go.
As does this one: acme.sh/dnsapi/dns_dreamhost.sh at master · acmesh-official/acme.sh · GitHub
If you are skilled at writing scripts you could use Certbot with its --pre-hook and --post-hook to add and delete the needed TXT records. But, it is much easier to use a client that supports it already.
2 Likes
I looked at DNS providers who easily integrate with Let's Encrypt DNS validation
However, this is issue is regarding my home server, which only has forward DNS, as it's on Mediacom cable.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.