Skip to content
New issue

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

add faq for sl error #4532

Merged
merged 9 commits into from
Nov 30, 2023
Merged

add faq for sl error #4532

merged 9 commits into from
Nov 30, 2023

Conversation

mirnawong1
Copy link
Contributor

adding an SL faq to help users unblock themselves when they encounter an alpn error per slack thread

@mirnawong1 mirnawong1 requested a review from a team as a code owner November 24, 2023 11:34
Copy link

vercel bot commented Nov 24, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
docs-getdbt-com ✅ Ready (Inspect) Visit Preview 💬 Add feedback Nov 30, 2023 5:30pm

@github-actions github-actions bot added content Improvements or additions to content size: small This change will take 1 to 2 days to address Docs team Authored by the Docs team @dbt Labs labels Nov 24, 2023

If you're receiving a `Failed ALPN` error when trying to connect the dbt Semantic Layer with the available [data integration tool](/docs/use-dbt-semantic-layer/avail-sl-integrations), it typically happens when connecting from a computer behind a corporate VPN or Proxy, such as Zscaler.

To fix this, add an SSL interception exception for the dbt Cloud domain in your settings.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think adding a bit of context on why the error occurs might help users work with their IT department to figure out. Maybe something like:

The problem is due to the proxy interfering with the TLS handshake. The Semantic Layer uses gRPC/HTTP2 to connect, so if your proxy does not support this you'll need to add an exception for the dbt Cloud domain. If your proxy does support this, you'll need to make sure it's configured correctly to allow ALPN, or create an exception for the dbt Cloud domain.

@mirnawong1
Copy link
Contributor Author

wonderful, thank you so much Diego! i've folded in your changes and tweaked it further -- can you double check it please? thank you!

Copy link

@aiguofer aiguofer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Thanks so much :)

@mirnawong1 mirnawong1 merged commit 71da5e3 into current Nov 30, 2023
7 checks passed
@mirnawong1 mirnawong1 deleted the mwong-sl-alpn-error branch November 30, 2023 17:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content Docs team Authored by the Docs team @dbt Labs size: small This change will take 1 to 2 days to address
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants