This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
plugins:letsencrypt [2016/11/23 16:27] nuxwin [Manual execution of the certbot client] |
plugins:letsencrypt [2016/11/23 16:29] nuxwin [Let's Encrypt Rate Limits] |
||
---|---|---|---|
Line 51: | Line 51: | ||
===== Certbot client version ===== | ===== Certbot client version ===== | ||
- | It is possible to use latest released version or development version of the Certbot client by changing the value of the `certbot_version` configuration parameter in the plugin configuration file. Be aware that usage of the development version is discouraged in production environments. | + | It is possible to use latest released version or development version of the Certbot client by changing the value of the **certbot_version** configuration parameter in the plugin configuration file. Be aware that usage of the development version is discouraged in production environments. |
===== Let's Encrypt registration ===== | ===== Let's Encrypt registration ===== | ||
Line 57: | Line 57: | ||
The plugin automatically process your Let's Encrypt account registration, using the administrator email address that you have provided during i-MSCP setup phase. If you need change that email, you must not forget to run the following command to update your Let's Encrypt account: | The plugin automatically process your Let's Encrypt account registration, using the administrator email address that you have provided during i-MSCP setup phase. If you need change that email, you must not forget to run the following command to update your Let's Encrypt account: | ||
- | <konsole root> | + | # certbot-auto register --update-registration --email <new_email> |
- | certbot-auto register --update-registration --email <new_email> | + | |
- | </konsole> | + | |
- | where `<new_email>` is your new email address. | + | where **<new_email>** is your new email address. |
If you don't do so, a new account will be created using the new email address and there will be inconsistencies with SSL certificate lineages, making the plugin unable to work properly. | If you don't do so, a new account will be created using the new email address and there will be inconsistencies with SSL certificate lineages, making the plugin unable to work properly. | ||
Line 69: | Line 67: | ||
Be sure to read https://letsencrypt.org/docs/rate-limits | Be sure to read https://letsencrypt.org/docs/rate-limits | ||
- | Note that when the Let's Encrypt limits are reached, the plugin will automatically set the status of the SSL certificate to `pending`. The pending tasks are postponed as long as the limits are not released. | + | Note that when the Let's Encrypt limits are reached, the plugin will automatically set the status of the SSL certificate to **pending**. The pending tasks are postponed as long as the limits are not released. |
===== Let's Encrypt SSL certificates for the control panel and services (FTP, IMAP/POP and SMTP) ===== | ===== Let's Encrypt SSL certificates for the control panel and services (FTP, IMAP/POP and SMTP) ===== |