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

[VS Code] Could not connect to the server via. Check that you are using a valid service endpoint [ via Proxy ] #151

Closed
alioguzhan opened this issue Mar 21, 2018 · 3 comments

Comments

@alioguzhan
Copy link

alioguzhan commented Mar 21, 2018

Error:

Could not connect to the server. Check that you are using a valid service endpoint

Steps to Reproduce:

I can't log in to my account behind the corporate proxy. If i switch to no-proxy connection everything [logging in to account / starting live share etc. ] work perfectly.

Traceback:

Agent.Rpc.Auth V] > #1 [14] auth.login(<0:>)
[Agent.Http V] < POST https://insiders.liveshare.vsengsaas.visualstudio.com/auth/token
[Agent.Http E] > POST https://insiders.liveshare.vsengsaas.visualstudio.com/auth/token => An error occurred while sending the request.
[Agent V] < #1 telemetry.httpRequestComplete: <65:35e51a44>
[Agent.Rpc.Auth V] < #1 [14] Error: Could not connect to the server. Check that you are using a valid service endpoint
[Client.Rpc.Auth E] > auth.login() error:    at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Cascade.Tracing.TracingHttpMessageHandler.<SendAsync>d__14.MoveNext() in E:\A\_work\12\s\src\Common\Tracing\TracingHttpMessageHandler.cs:line 79
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.Cascade.Agent.ForwardResponseMessageHandler.<SendAsync>d__7.MoveNext() in E:\A\_work\12\s\src\Agent\ForwardResponseMessageHandler.cs:line 55
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime...
Version Data
extensionName VSLS
extensionVersion 0.2.206
protocolVersion 2.1
applicationName VSCode
applicationVersion 1.21.1
platformName MacOS
platformVersion 16.7.0
@alioguzhan alioguzhan changed the title [VS Code] Could not connect to the server. Check that you are using a valid service endpoint [VS Code] Could not connect to the server via. Check that you are using a valid service endpoint [ via Proxy ] Mar 21, 2018
@Chuxel
Copy link
Member

Chuxel commented Mar 21, 2018

@alioguzhan Thanks for reporting the issue! Yes, this appears to be another symptom of #86 as you already identified. Would you mind if we merged this bug in with #86 to consolidate information in one spot?

@alioguzhan
Copy link
Author

alioguzhan commented Mar 21, 2018 via email

@Chuxel
Copy link
Member

Chuxel commented Mar 21, 2018

Great! Done. Thanks for reporting it!!

@Chuxel Chuxel closed this as completed Mar 21, 2018
Chuxel pushed a commit that referenced this issue Sep 18, 2019
Confirm merge from repo_sync_working_branch to live to sync with https://github.com/microsoftdocs/live-share (branch master)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants