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: safiya-mylo.ru
I ran this command: certbot renew
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Processing /etc/letsencrypt/renewal/safiya-mylo.ru.conf
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Renewing an existing certificate for safiya-mylo.ru
Failed to renew certificate safiya-mylo.ru with error: urn:ietf:params:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new order :: too many failed authorizations recently: see https://letsencrypt.org/docs/failed-validation-limit/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/safiya-mylo.ru/fullchain.pem (failure)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1 renew failure(s), 0 parse failure(s)
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
My web server is (include version): nginx/1.14.0 (Ubuntu)
The operating system my web server runs on is (include version): ubuntu 18.04
My hosting provider, if applicable, is: timeweb.cloud
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): with ssh and with panel
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 2.6.0
my nginx file for my server:
server {
server_name safiya-mylo.ru;
location = /favicon.ico { access_log off; log_not_found off; }
location /static/ {
root /root/Safya-soapshop/config;
}
location /media/ {
root /root/Safya-soapshop/config;
}
location / {
include proxy_params;
proxy_pass http://unix:/run/gunicorn.sck;
}
listen 443 ssl; # managed by Certbot
ssl_certificate /etc/letsencrypt/live/safiya-mylo.ru/fullchain.pem; # managed by Certbot
ssl_certificate_key /etc/letsencrypt/live/safiya-mylo.ru/privkey.pem; # managed by Certbot
include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot
ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot
}
server {
if ($host = safiya-mylo.ru) {
return 301 https://$host$request_uri;
} # managed by Certbot
listen 80;
server_name safiya-mylo.ru;
return 404; # managed by Certbot
}
I run certbot certificates:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Found the following certs:
Certificate Name: safiya-mylo.ru
Serial Number: 31c85260ad315d76e58db5a892bdac944de
Key Type: ECDSA
Domains: safiya-mylo.ru
Expiry Date: 2023-07-30 05:19:16+00:00 (INVALID: EXPIRED)
Certificate Path: /etc/letsencrypt/live/safiya-mylo.ru/fullchain.pem
Private Key Path: /etc/letsencrypt/live/safiya-mylo.ru/privkey.pem
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
my domain belongs to my address... I'm at a loss, because I did not work with let's encrypt (((
