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

ECONNREFUSED when starting Omnisharp #200

Closed
germansak opened this issue Apr 15, 2016 · 7 comments
Closed

ECONNREFUSED when starting Omnisharp #200

germansak opened this issue Apr 15, 2016 · 7 comments

Comments

@germansak
Copy link

Hi, I'm on

When I try to open a sample (c#) it refuses to start Omnisharp with this error:

[INFO] Starting OmniSharp at 'c:\Users\germansak\cli-samples\HelloMvcApi'...
[ERROR] Error: connect ECONNREFUSED 192.30.252.127:443

Could it be that I'm behind a proxy?

Thanks!

@MathiasKowoll
Copy link

it may be, once you install the new version it needs to connect internet and download de new debugger. 192.30.252.127 listen for api.github.com

@germansak
Copy link
Author

Thanks BeelzeBu, is there any way to solve it? Maybe setting somewhere my proxy address (already did it on Code, but no luck)

Cheers!

@DustinCampbell DustinCampbell changed the title Error starting Omnisharp ECONNREFUSED when starting Omnisharp Apr 16, 2016
@DustinCampbell
Copy link
Member

Unfortunately, there's no way to set this today, but I've capture this issue as a feature request.

You can get this working by downloading and unpacking the appropriate OmniSharp release for your operating system from here. (If you're on Linux, it's best to grab the release that matches your distro.) Then, in VS Code, select Preferences->User Settings from the menu and add the following to settings.json:

"csharp.omnisharp": "/path/to/the/omnisharp/executable/you/just/downloaded/and/unpacked"

@germansak
Copy link
Author

Hi Dustin, thanks for the reply!
I've verified that the error is the proxy. It tested it at home (no proxy) and it worked perfectly. There's no need for me to apply this workaround because I'm just testing stuff. I can wait for it to be fixed.

Thanks again
Germán

@DustinCampbell
Copy link
Member

Did you intend to close this issue? We won't take a look at it if there isn't an active issue.

@germansak
Copy link
Author

Ooops!! Sorry

@germansak germansak reopened this Apr 18, 2016
@DustinCampbell
Copy link
Member

This is now fixed with this PR: #350.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants