{"id":1872,"date":"2016-11-02T00:28:02","date_gmt":"2016-11-01T23:28:02","guid":{"rendered":"http:\/\/monodes.com\/predaelli\/?p=1872"},"modified":"2016-11-02T00:28:02","modified_gmt":"2016-11-01T23:28:02","slug":"cert-for-both-www-and-plain-domain","status":"publish","type":"post","link":"https:\/\/monodes.com\/predaelli\/2016\/11\/02\/cert-for-both-www-and-plain-domain\/","title":{"rendered":"Cert for both www and plain domain"},"content":{"rendered":"
\n
\n

Just a note for myself: renew Let’s Encrypt certificate to make it valid for both www and plain domain<\/p>\n<\/div>\n<\/div>\n

\n
\n
\n

You should be able to do that using the command you originally used to obtain the certificate. Add --force-renewal<\/code> to force the client to get a new certificate even if the current one isn’t close to expiring. Based on your earlier post, this would be something like:<\/p>\n

.\/letsencrypt-auto --apache -d example.me -d www.example.me -d mysql.example.me --force-renewal<\/code><\/p>\n

Revocation isn’t needed – that’s something you only need to bother with if your private key is compromised.<\/p>\n<\/div>\n<\/div>\n<\/blockquote>\n

\n
\n