Add INTERNAL_LIGHTDASH_HOST_IGNORE_HTTPS_ERRORS docs for internal HTTPS headless browser setup#592
Merged
rephus merged 1 commit intomainfrom May 4, 2026
05-04-add_internal_lightdash_host_ignore_https_errors_docs_for_internal_https_headless_browser_setup
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
…TTPS headless browser setup
rephus
force-pushed
the
05-04-add_internal_lightdash_host_ignore_https_errors_docs_for_internal_https_headless_browser_setup
branch
from
6d0b089 to
d1f089d
Compare
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Documents the new
INTERNAL_LIGHTDASH_HOST_IGNORE_HTTPS_ERRORSenvironment variable and adds a dedicated section explaining how to run Lightdash on a fully internal HTTPS network whenSECURE_COOKIES=true.The new section covers why plain HTTP for
INTERNAL_LIGHTDASH_HOSTfails in this configuration (HSTS causing Chrome to auto-upgrade requests), and provides two options for handling TLS on the internal hostname:INTERNAL_LIGHTDASH_HOSTto an HTTPS URL.INTERNAL_LIGHTDASH_HOST_IGNORE_HTTPS_ERRORS=trueto skip TLS validation for screenshot traffic, with a note on the security trade-off and when this is appropriate.The environment variables reference is updated to include
INTERNAL_LIGHTDASH_HOST_IGNORE_HTTPS_ERRORSwith a description of its behaviour, default value, and a link to the new section.