Skip to content
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

If the users has a remote server specified and that server is down we show a hard to diagnose ECONNREFUSED error #3574

Closed
IanMatthewHuff opened this issue Mar 7, 2019 · 1 comment
Assignees

Comments

@IanMatthewHuff
Copy link
Member

I've run into this case myself and it took me a second to realize what was going on. When you set jupyter to use a remote server it's easy to forget that setting was set, particularly as you can set that setting per workspace. If you then shutdown that server and try to connect again instead of a reasonable error you get that ECONNREFUSED message that has plagued us. You do see the server name in that message, but it's not clear that you still have the remote setting on. We need to make this more clear to customers as this could be the cause of some ECONNREFUSED messages.

@ronglums
Copy link
Contributor

ronglums commented Mar 8, 2019

Make the message more friendly at minimum.

@IanMatthewHuff IanMatthewHuff self-assigned this Mar 11, 2019
@rchiodo rchiodo closed this as completed Apr 24, 2019
@lock lock bot locked as resolved and limited conversation to collaborators May 22, 2019
@microsoft microsoft unlocked this conversation Nov 14, 2020
@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 14, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 7, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants