I cant visit my site

Help
1

I activated ssl and everything was fine at first. A few days later, my website suddenly stopped opening, but I could still access the server.
I tried to reissue the certificate, but it didn't work. I exhausted my 5 attempts. Then I tried to delete it, but it still didn't work. What should I do?

My domain is: ge.bazzay.ru

I ran this command:
sudo apt-get remove --purge certbot
sudo rm -rf /etc/letsencrypt
sudo rm -rf /var/lib/letsencrypt
sudo apt-get autoremove

It produced this output: -

My web server is (include version):

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

My hosting provider, if applicable, is: aeza

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

2

Temporarily switch to a different CA like buypass or zerossl (or google). You will need to fix the "I tried to reissue the certificate, but it didn't work" because it sounds like it did work and that's why you hit the rate limit.

Check your domain is actually pointing at your server IP, currently it's a google server that's responding.

3

So if I set up zerossl, everything will work?
And how can I completely disable letsencrypt so that the site runs on http?

4

Requests to your domain get replied to by a google server. See: SSL Checker

You should review the IP address in your public DNS and make sure it points to your public IP and not google's server. If you did not set that up you should contact your hosting service.

3 Likes
5

Thanks for answer, i cheked it. All good. What next?

6

Why do HTTPS requests to your domain return a certificate for google domain names and the cert issued by Google? See pic below

And, HTTP connections not all good. See:

HTTPS requests to your domain use this certificate. Why?

echo | openssl s_client -connect ge.bazzay.ru:443 | head -20

Certificate chain
 0 s:CN = *.google.com
   i:C = US, O = Google Trust Services, CN = WR2
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Jul  7 08:34:03 2025 GMT; NotAfter: Sep 29 08:34:02 2025 GMT
 1 s:C = US, O = Google Trust Services, CN = WR2
   i:C = US, O = Google Trust Services LLC, CN = GTS Root R1
   a:PKEY: rsaEncryption, 2048 (bit); sigalg: RSA-SHA256
   v:NotBefore: Dec 13 09:00:00 2023 GMT; NotAfter: Feb 20 14:00:00 2029 GMT
4 Likes
7

i dont know. Maybe i was used it before. Can you tell me what to do please?

8

I think you should contact your hosting provider and ask for help

I don't see any problem that is related to Let's Encrypt.

4 Likes
9

Thank you! I followed your advice and was able to restore my work, but now I have a different question: how can I get the latest activated letsencrypt ssl certificate?

10

I don't see anything different. HTTP requests to your domain still fail. HTTPS requests still see a google server.

In your first post you deleted all of them. So, you will need to request another one. You were rate limited so need to wait 34 hours before a new request might work. See: Rate Limits - Let's Encrypt

An HTTP Challenge will not succeed until you fix HTTP connections. You never described what command or method you used to get the cert but a DNS Challenge might work even with your broken HTTP.

5 Likes
11

Thanks for the answers. In conclusion, I cannot generate a new ssl certificate before 14.08.25?

12

No, why do you think that? Getting certs isn't your problem.

Something in your server or network configuration is wrong. HTTP requests still fail and HTTPS requests see a google server. Same as before.

This is your recent cert history (from https://crt.sh)

image
image1701×402 105 KB

4 Likes
13

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.