We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Re: Relaunch Existing Pantheon Site
Priority: Medium
This page seem to lack guidelines for sites that requires moving Custom Certificates to Front-end sites.
Ideally, users should do this - https://docs.pantheon.io/custom-certificates#disable-lets-encrypt-with-caa-records - before they add their domain on the new site instance so the site blocks issuance of Let's Encrypt certificates.
A quick reminder about CAA records before the Relaunch Procedure section should suffice.
The text was updated successfully, but these errors were encountered:
rachelwhitton
No branches or pull requests
Re: Relaunch Existing Pantheon Site
Priority: Medium
Issue Description:
This page seem to lack guidelines for sites that requires moving Custom Certificates to Front-end sites.
Ideally, users should do this - https://docs.pantheon.io/custom-certificates#disable-lets-encrypt-with-caa-records - before they add their domain on the new site instance so the site blocks issuance of Let's Encrypt certificates.
Suggested Resolution
A quick reminder about CAA records before the Relaunch Procedure section should suffice.
The text was updated successfully, but these errors were encountered: