-
-
Save eslachance/e3cb5a47f1682df30c17bb9a69359f6c to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| root@vps83813:~# letsencrypt renew | |
| Saving debug log to /var/log/letsencrypt/letsencrypt.log | |
| ------------------------------------------------------------------------------- | |
| Processing /etc/letsencrypt/renewal/evie.codes-0001.conf | |
| ------------------------------------------------------------------------------- | |
| expected /etc/letsencrypt/live/evie.codes-0001/cert.pem to be a symlink | |
| Renewal configuration file /etc/letsencrypt/renewal/evie.codes-0001.conf is broken. Skipping. | |
| ------------------------------------------------------------------------------- | |
| Processing /etc/letsencrypt/renewal/evie.codes.conf | |
| ------------------------------------------------------------------------------- | |
| Cert is due for renewal, auto-renewing... | |
| Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org | |
| Renewing an existing certificate | |
| Performing the following challenges: | |
| tls-sni-01 challenge for evie.codes | |
| tls-sni-01 challenge for c9.evie.codes | |
| tls-sni-01 challenge for db.evie.codes | |
| tls-sni-01 challenge for discord.evie.codes | |
| tls-sni-01 challenge for evie-banned.me | |
| tls-sni-01 challenge for guardian.evie.codes | |
| tls-sni-01 challenge for how.evie-banned.me | |
| tls-sni-01 challenge for omnic.xyz | |
| tls-sni-01 challenge for omnicbot.evie.codes | |
| tls-sni-01 challenge for proof.evie-banned.me | |
| tls-sni-01 challenge for www.evie.codes | |
| tls-sni-01 challenge for www.omnic.xyz | |
| nginx: [warn] conflicting server name "evie.codes" on 0.0.0.0:443, ignored | |
| nginx: [warn] conflicting server name "omnic.xyz" on 0.0.0.0:443, ignored | |
| Waiting for verification... | |
| Cleaning up challenges | |
| Attempting to renew cert from /etc/letsencrypt/renewal/evie.codes.conf produced an unexpected error: urn:acme:error:rateLimited :: There were too many requests of a given type :: Error creating new cert :: too many certificates already issued for exact set of domains: c9.evie.codes,db.evie.codes,discord.evie.codes,evie-banned.me,evie.codes,guardian.evie.codes,how.evie-banned.me,omnic.xyz,omnicbot.evie.codes,proof.evie-banned.me,www.evie.codes,www.omnic.xyz: see https://letsencrypt.org/docs/rate-limits/. Skipping. | |
| All renewal attempts failed. The following certs could not be renewed: | |
| /etc/letsencrypt/live/evie.codes/fullchain.pem (failure) | |
| Additionally, the following renewal configuration files were invalid: | |
| /etc/letsencrypt/renewal/evie.codes-0001.conf (parsefail) | |
| 1 renew failure(s), 1 parse failure(s) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment