Custom TLS certificates that are installed for a domain should be renewed by the customer prior to their expiration date. The expiration date for a domain’s TLS certificate is displayed in the column labeled “Certificates” in the Domains & TLS panel of the VIP Dashboard.
Archives: How-to Guides
Showing page 1 of 13
The VIP Platform will automatically make attempts to renew a domain’s installed Let’s Encrypt certificate 28 days prior to the certificate’s expiration date.
After a Let’s Encrypt TLS certificate has been provisioned, it is possible to switch to a custom TLS certificate at any time.
The VIP Platform is built to support a “code moves up; content moves down” workflow. This means that any new content needs to be added to the production site and then synced down to non-production environments, and new code should be tested on the non-production environment prior to deploying to the production environment.
After a custom TLS certificate has been provisioned, it is possible to switch to a Let’s Encrypt TLS certificate at any time.
To install a custom TLS certificate for a domain with a CSR that was not generated by VIP, customers must have in their possession a complete certificate chain generated by a Certificate Authority (CA).
A certificate signing request (CSR) from VIP can be generated in order to obtain a custom certificate from a Certificate Authority (CA). A CSR generated by VIP contains the necessary information, plus VIP’s authorization, that the CA needs to process a TLS certificate.
A generated custom TLS certificate must meet all of the following requirements in order to be successfully installed:
By default, the current version of Jetpack plugin is automatically made available to all WordPress sites via VIP MU plugins.
Installing PHPCS at the project level limits the availability of PHPCS to only from within that project directory. Following these instructions will install: