Troubleshoot When Let's Encrypt Renewal Is Not Working
January 21, 2019Check renewal configuration at /etc/letsencrypt/renewal/.
Content of www.mydomain.com.
# renew_before_expiry = 30 days
version = 0.22.2
archive_dir = /etc/letsencrypt/archive/www.mydomain.com
cert = /etc/letsencrypt/live/www.mydomain.com/cert.pem
privkey = /etc/letsencrypt/live/www.mydomain.com/privkey.pem
chain = /etc/letsencrypt/live/www.mydomain.com/chain.pem
fullchain = /etc/letsencrypt/live/www.mydomain.com/fullchain.pem
# Options used in the renewal process
[renewalparams]
authenticator = webroot
installer = nginx
account = bf2a***Test renewal.
certbot renew --cert-name www.mydomain.com --dry-runMy original renewal through webroot authenticator is failing because of missing /.well-known/acme-challenge directory.
I switch to nginx authentication to solve the issue.
certbot renew --cert-name www.mydomain.com --nginxList all certbox certificates.
certbot certificates- android
- android-ktx
- android-studio
- bootstrap
- cloud-functions
- coding-interview
- coroutines
- crashlytics
- css
- dagger2
- datastore
- eslint
- firebase
- firestore
- flask
- fontawesome
- git
- glide
- google-app-engine
- google-drive
- google-maps
- google-places
- google-play
- google-sheets
- hugo
- java
- java-time
- javascript
- kotlin
- lets-encrypt
- linux
- markdown
- moshi
- nginx
- npm
- pip
- python
- room
- rxjava
- selenium
- ssl
- static-site-generator
- sublime-text
- ubuntu
- unit-test
- uwsgi
- virtualbox
- vue-cli
- vuejs
- web-development
- web-hosting
- webpack
- windows
- workmanager