-
Notifications
You must be signed in to change notification settings - Fork 156
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
Improve warning messages when a remote connection cannot be established #45
Labels
Milestone
Comments
tlovett1
added
type:enhancement
New feature or request.
and removed
type:question
Further information is requested.
labels
Jul 28, 2018
I'm gonna connect this with #368, moving to 1.6. |
To get some recent notes on testing external connections: Automatic setup These seem pretty good. Somewhat geek oriented with the curl error IDs but I don't this that's entirely a bad thing.
Manual setup These could still do with some work but I suspect they're not seen very frequently as manual set up is behind an additional link.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setting up remote connections is causing some confusion with early testers; I think our warning messages might be a bit too vague.
Can we be a bit more specific in catching and explaining common failure use cases? Like the REST API not being available, not finding a secure connection (even linking to a recommended auth plugin), Distributor not being detected on the other end... ?
The text was updated successfully, but these errors were encountered: