Im trying to re-install a cert that expire, I try to renew and failed, so I decide to re-install certbot and create a new cert, but it failed (same error)
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): Apache/2.4.18
The operating system my web server runs on is (include version): Ubuntu 16.04.5 LTS
My hosting provider, if applicable, is: DigitalOcean
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
Your server seems to be serving HTTP (rather than HTTPS) on port 443.
The challenge comes in over HTTP and you’re redirecting it to HTTPS; Let’s Encrypt will happily follow the redirect but there needs to be a working HTTPS connection at the end of it (not necessarily a valid certificate, but HTTP on port 443 won’t work).
There should be some directives to enable HTTPS (SSLEngine on and so forth) in your port 443 VirtualHost, or in an included file such as options-ssl-apache.conf - do you remember removing something like this? You may need to put it back in.
Or you could try temporarily disabling the redirect until you get things working again.
Did you re-enable it again? It still seems to be redirecting, for me.
I'm not sure what you mean by this ... mod_ssl doesn't do anything with redirects, rather it allows you to enable SSL/TLS. And it still seems to be disabled on your server.
It's often useful to post the error anyway, even if it looks the same, as there might be subtle differences that could be meaningful to the folks here...
Posting the relevant parts of your Apache configuration (for that domain) might be helpful.
An unexpected error occurred: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/
There is a Failed Validation limit of 5 failures per account, per hostname, per hour. This limit is higher on our staging environment, so you can use that environment to debug connectivity problems.
First use the testsystem (option --staging), there is a higher limit. If that works, use the productive system.
Perhaps use (with the testsystem) certonly as option, so your configuration is unchanged.
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.
Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.