How recover from too many failed attempts - wrong port in Router fixed

Help
1

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.

My domain is: app.spartanmainframe.au

I ran this command: sudo certbot --apache

It produced this output: Too many attempts... "face palm"

My web server is (include version): Apache2

The operating system my web server runs on is (include version): Ubuntu 24.04

My hosting provider, if applicable, is: Swoop

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): certbot --classic

What is the penalty wait time to safely try again now I have the ports in router correctly pointed at my Server.

2

The message should have provided a time but in case it did not the wait time is one hour for excessive failed attempts. There should also have been a link to the explanation page: Failed Validation Limit - Let's Encrypt

After the first failure you should use the Let's Encrypt staging system to avoid this on the production system.

The Let's Debug test site is also helpful to debug comms problems. Which currently look OK for your domain

3 Likes