-
Notifications
You must be signed in to change notification settings - Fork 982
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
add faq for sl error #4532
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
||
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. |
There was a problem hiding this comment.
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.
wonderful, thank you so much Diego! i've folded in your changes and tweaked it further -- can you double check it please? thank you! |
There was a problem hiding this 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 :)
adding an SL faq to help users unblock themselves when they encounter an alpn error per slack thread