Hi @voylinux, if you chose “Secure” when you installed the certificate, it would have added a redirect directive to your Apache configuration which sends a redirect header at the HTTP level to tell clients that the location of the page has moved to the HTTPS version. If you remove the redirect directive from your Apache configuration file and restart Apache, people should once again be able to go to the HTTP version of the site.
/etc/letsencrypt directory does contain cryptographic keys which are needed to prove your identity to the Let’s Encrypt CA (and to people who visit your site). Without those cryptographic keys, you can’t easily revoke a certificate because there’s no way to distinguish you from anyone else who shows up asking for a certificate to be revoked! Also, revocation does not affect the rate limits so it wouldn’t allow you to get new certificates sooner.
If you registered an e-mail address when you originally ran the client, there may be a way to do e-mail-based recovery to set up an account key. I’m not sure what the state of the implementation of that functionality is on the client or server side at the moment; I think we may not have the tools finished. But I think in your situation revocation isn’t exactly what you need because it won’t help with the rate limit, and simply removing the redirect should allow you to let people visit your site again.