-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Connection to compute instance fails occasionally with 403 Forbidden #2501
Comments
Could you please set the log level to debug or trace and paste the connection log again? This will be more helpful for us to debug the issue. Additionally, you can enable the new feature |
Here's the trace of connection attempt:
Enabling the Choosing "Restart and connect" seems to have no effect, probably due to this warning that comes up with the dialog: Manually restarting the compute instance does not prevent the above dialog. "use exec server" trace
|
@Manezki, it seems you're encountering an issue when trying to initiate the Jupyter terminal in your CI. You can try unchecking the When you enable the |
@Siglud I don't feel comfortable disclosing subscription id nor the workspace name on a public forum. Do you have an established way how I could share that information privately? |
Hi @Manezki, could you please reach out to us via this email? I think we need the subscription id, resource group id, workspace name and the CI name |
I've emailed the info that you requested |
Meanwhile I've tried the following workarounds without consistent success:
|
Does this occur consistently? No
Repro steps:
Unable to reliably reproduce.
Action: Resolver.resolve
Error type: Yg
Error Message: Connection is forbidden. Please make sure that you are logged in with the right Azure Account and the Remote target exists. (Error: Invalid response: 403 Forbidden)
Version: 1.4.0
OS: linux
OS Release: 6.11.0-17-generic
Product: Visual Studio Code
Product Version: 1.97.1
Language: en
Call Stack
Additional information:
Any workaround, fixes, or debugging steps would greatly appreciated.
The text was updated successfully, but these errors were encountered: