Certbot no longer works

I won't have any more time tonight to walk through all these issues.

But, your problem probably originated with the changed IP. Either your DNS was still pointing to the prior IP. Or, perhaps your ISP imposed new restrictions on port 80 and/or 443. Or a setting in your new router was faulty (like any NAT or port forwarding).

Right now I cannot reach either of your domains using HTTP (port 80) or HTTPS (port 443). And, Let's Debug and Let's Encrypt Staging system both fail to reach your domain using HTTP. I think something may be wrong with your comms config now. And, possibly even with Apache too.

How did you get the 5 certs that are now causing a rate limit for a 6th?

Did you read the Rate Limit page linked to in the error message? (This page) There is a work-around that may work for you given what I see in your cert history.

By the way, the method you used to delete certs was poor. There is a Certbot delete command for that and also you must remove all references to those deleted files from your Apache web server otherwise it will fail to start.

To safely delete certs see:
https://eff-certbot.readthedocs.io/en/latest/using.html#safely-deleting-certificates

4 Likes