Update from support feedback: assistant network/VPN troubleshooting#6428
Merged
Conversation
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ethanpalm
reviewed
Jul 8, 2026
ethanpalm
approved these changes
Jul 8, 2026
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
2 participants
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.
Summary
Add a troubleshooting entry to the assistant page explaining that corporate networks, VPNs, and firewalls can block the assistant at the network level, with the outbound hostnames readers or their IT team may need to allow.
Changes
assistant/use.mdx: new "Assistant blocked on a corporate network, VPN, or firewall" accordion covering the network-level cause, the hostnames to allow (leaves.mintlify.com,*.mintlify.dev,*.mintlify.com,hcaptcha.com/*.hcaptcha.com), and guidance for site owners responding to reader reports.es/assistant/use.mdx,fr/assistant/use.mdx, andzh/assistant/use.mdx.Context
Recent support threads showed readers assuming the assistant was broken when it only failed on their work network or VPN. The existing accordion only covers browser-level content blockers (EasyList/Brave/Comet), and the CSP page targets admins customizing headers — neither addresses the visitor-side network case.
Note
Low Risk
Documentation-only troubleshooting copy with no runtime, auth, or deployment behavior changes.
Overview
Adds a Troubleshooting accordion for when the assistant works on personal networks but fails on corporate networks, VPNs, or firewalls, explaining that outbound HTTPS to Mintlify and hCaptcha hosts is often blocked at the visitor’s network.
The new section lists hostnames for IT allowlists (
leaves.mintlify.com,*.mintlify.dev,*.mintlify.com,hcaptcha.com/*.hcaptcha.com), gives readers steps to confirm network-specific failure, and tells site owners how to respond and when to point to CSP configuration for self-hosted setups.The same accordion is added to the Spanish, French, and Chinese
assistant/use.mdxtranslations.Reviewed by Cursor Bugbot for commit a08095c. Bugbot is set up for automated code reviews on this repo. Configure here.