Remove steps about using full strict with Cloudflare #283
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We are suggesting users to enable strict mode with custom domains and Linksharing TLS. This won't work, because we require that you don't proxy at all if using Linksharing TLS, or creation/renew cert challenges will fail. It sort of works if you first create the certificate on Linksharing, _then_ change the setting to strict, but this is not reliable because it will fail in 3 months when the certificate is attempted to be renewed.
|
Visit the preview URL for this PR (updated for commit 1435090): https://storj-docs--pr283-custom-domain-cdn-pa-3xdxwm5l.web.app (expires Mon, 09 Oct 2023 01:38:27 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 Sign: 3c1f0a7f83da2cd749f45c4149016bdb4af1841c |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We are suggesting users to enable strict mode with custom domains and Linksharing TLS. This won't work, because we require that you don't proxy at all if using Linksharing TLS, otherwise certificate creation/renewal challenges will fail.
It sort of works if you first create the certificate on Linksharing, then change Cloudflare to proxy and set the mode to strict, but this is not reliable because it will fail in 3 months when the certificate is attempted to be renewed.
I will add a new dedicated section about using Cloudflare and other proxies with Linksharing TLS in another change.