-
Notifications
You must be signed in to change notification settings - Fork 50
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
Create troubleshooting page in docs #587
Labels
documentation
Improvements or additions to documentation
Comments
waldekmastykarz
added
documentation
Improvements or additions to documentation
needs peer review
Issue needs review from other team members
labels
Feb 26, 2024
Nice idea. How would folks get to the page and how would they know that it exists? Are you thinking of a |
To raise awareness of the page, we should do the following:
I'm not sure if a doctor command would help us automatically detect the things that need to be checked in order to determine what's wrong. |
waldekmastykarz
removed
the
needs peer review
Issue needs review from other team members
label
Mar 11, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
To help customers troubleshoot proxy not working as intended, we should create a page to which we can point to in-product, from issues, on social, etc.
The page should contain walk customers through the same troubleshooting steps that we'd take if we're to help them 1:1. Proposed structure:
Symptom: Proxy is not intercepting requests
Symptom: Requests intercepted but passed through
Symptom: You get an SSL error in your app when using Dev Proxy:
The text was updated successfully, but these errors were encountered: