In this lesson we'll configure DNS and provision free, automated HTTPS on Pantheon.
If your site is already live and serving HTTPS traffic, and will require HTTPS on Pantheon, return to Connect a Domain Name and complete the steps to pre-provision HTTPS before updating DNS to avoid downtime.
These instructions cover the common
www.example.com domain configuration. For other domain configurations, see Platform and Custom Domains.
The icon within the Domains / HTTPS page indicates that the domain has not been properly routed to Pantheon. The following actions are required:
live-yoursite.pantheonsite.io), then use it to create a CNAME record wherever you manage DNS.
For more detailed instructions pertaining to your specific DNS host, click below:
The process to provision certificates kicks off automatically after the domain has been successfully routed to Pantheon, indicated by the following notice:
Both the bare domain and the
HTTPSYour DNS configuration is correct, and certificate provisioning is queued to start for this domain.
wwwdomain will be accessible over HTTPS once the HTTPS status turns green (which may take up to an hour):
HTTPSLet’s Encrypt certificate deployed to Pantheon’s Global CDN. Certificate renews automatically with no additional cost.
example.com) and/or subdomains (
blog.example.com) must point to Pantheon's servers so Let's Encrypt can verify domain ownership.