Add Troubleshooting article about "could not be reached" error #1448
Conversation
This file contains 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
alfred-landrum
approved these changes
Feb 11, 2021
Co-authored-by: Alfred Landrum <alfred@leakybucket.org>
Co-authored-by: Alfred Landrum <alfred@leakybucket.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A particular Windows community user on Slack has reported a problem where Brim consistently fails to come up after auto-updates to new versions. We've provided some debug tips over Slack but have yet to determine a root cause, as each time they've ended up working around it by doing an uninstall/reinstall and perhaps a reboot. As a starting point for revisiting the topic with this user in the future or to get ahead of other users experiencing a similar problem, I've added a new Troubleshooting article here that points at some of the possible root causes and debug steps.
Since these don't get pushed into the wiki until the merge to master, I've staged a copy of it in a personal repo at https://github.com/philrz/scratchwiki/wiki/Troubleshooting#brim-shows-connection-error-the-service-at-localhost9867-could-not-be-reached so folks can review the formatted version.