VSCode failed to Azure sign in and cannot open Azure Bash after latest upgrade #801
Comments
|
|
|
My team and I are experiencing the same issue since about a week ago. We're working behind a company proxy and cannot connect to azure through the vscode extension. It seems it was cause by the latest update. I'm also getting this error: |
|
I am also getting the same error after s/w upgrade. Would appreciate a fix on this. |
|
I'm trying to find out if this was a result of the VS Code April 1.78 release or the recent 0.11.4 release of the Azure Account extension. Does downgrading the Azure Account extension to a previous version fix the issue? Does downgrading VS Code fix the issue? |
@JackH11 this looks like a different error than the original issue. Could you file a new issue and include specific details for your case? Thanks. |
|
No, I just uninstalled and reinstalled latest version which is 1.78 /0.11.4 release (recommended). It appears that the upgrade caused the problem as others reporting the same problem. |
|
Click wrong button (Issue not resolved). |
|
Just try downgrade to VSCodeUserSetup-x64-1.77.3 . First uninstalled the current one (1.78.1) and then installed, but right after installation complete, it appears that VSCode will automatically upgrade to the latest version (1.78.1). FYI. It is not me encountering this problem, but my teammates too with recent version upgrade. |
|
It's the exact same issue coming after the new update. Running Azure Account v0.11.4. I start by getting the error "You appear to be offline". The issue certificate is an additional error I get after the appearing offline. Is there a way I can point the certificate to somewhere else? |
|
A change released in the VS Code 1.78 April release breaks loading OS certificates on Windows. Meaning self-signed certificates and CA certificates picked up from a network proxy are currently broken. See microsoft/vscode#181404 for more details. It looks like VS Code is planning to include a fix in the 1.78.2 release (April recovery 2). Until that is released, you can downgrade to VS Code 1.77. Also, other users have had success installing the win-ca extension, which makes Trusted Root Certificates on Windows available to VS Code extensions. Another workaround if your CA certificate is provided by a network proxy is to configure the proxy related settings in VS Code. |
Downgrading to VS Code 1.77 Fixed the issue for me |
|
VS Code just released version 1.78.2 which should fix the certificates issue, could you please update VS Code and retry the operation? |
|
Tried on VS Code (Version 1.78.2) with Azure Account extension (v0.11.4), it still failed. However, when I downgraded Azure Account extension to previous version v0.11.3, the problem is fixed! Thanks! My solution is that VS Code version 1.78.2 plus Azure Account extension v0.11.3. Thanks!
|
|
@mz1245 weird, there should be no changes in v0.11.4 that impact cloud shell. Sorry to make you do this, but could you upgrade to v0.11.4 and try again? Thanks. If that doesn't work, could you share the logs when it fails? See the Enable and View Logs section of the wiki for how to capture and share Azure Account extension logs. |
|
It failed right after upgrade to v0.11.4
***@***.***
From: Alex Weininger ***@***.***>
Sent: Thursday, May 11, 2023 6:43 PM
To: microsoft/vscode-azure-account ***@***.***>
Cc: ZHANG, MICHAEL ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/vscode-azure-account] VSCode failed to Azure sign in and cannot open Azure Bash after latest upgrade (Issue #801)
@mz1245<https://urldefense.com/v3/__https:/github.com/mz1245__;!!BhdT!jNF695X_NW-Qf7WL2B3q1GXhKUmOCweNIm_5raJOC5TMAUUG0W9aT4R8-8ZzDSgZofdQPN8w4DWUl2YTQ0QP1cE$> weird, there should be no changes in v0.11.4 that impact cloud shell. Sorry to make you do this, but could you upgrade to v0.11.4 and try again? Thanks.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/microsoft/vscode-azure-account/issues/801*issuecomment-1544785400__;Iw!!BhdT!jNF695X_NW-Qf7WL2B3q1GXhKUmOCweNIm_5raJOC5TMAUUG0W9aT4R8-8ZzDSgZofdQPN8w4DWUl2YTbxMvfjk$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ASOHEB6HUC2KDZL2AG4BV43XFVTQRANCNFSM6AAAAAAXZ7NDYE__;!!BhdT!jNF695X_NW-Qf7WL2B3q1GXhKUmOCweNIm_5raJOC5TMAUUG0W9aT4R8-8ZzDSgZofdQPN8w4DWUl2YTquCqrC8$>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
Could you share the logs when it fails? See the Enable and View Logs section of the wiki for how to capture and share Azure Account extension logs. |
|
It appears that no problem to do sign in to Azure account, but it failed when open Azure Bash shell. Here is the log for Window.
2023-05-11 19:05:55.351 [trace] KeybindingService#dispatch Enter [ No matching keybinding ]
2023-05-11 19:06:03.471 [trace] Stopped polling file:///c%3A/Users/mz1245/AppData/Roaming/Code/logs/20230511T182740/window1/renderer.log
2023-05-11 19:06:06.522 [trace] onWillActivateByEvent: onTerminalProfile:azure-account.cloudShellBash
2023-05-11 19:06:06.524 [trace] CommandService#executeCommand _setContext
2023-05-11 19:06:06.633 [trace] terminalInstance#ctor (instanceId: 12) {"name":"Azure Cloud Shell (Bash)","executable":"node.exe","args":["-e","require('c:\\\\Users\\\\mz1245\\\\.vscode\\\\extensions\\\\ms-vscode.azure-account-0.11.4\\\\dist\\\\cloudConsoleLauncher').main()"],"icon":{"id":"azure"},"ignoreConfigurationCwd":true,"env":{"CLOUD_CONSOLE_IPC":"\\\\.\\pipe\\vscode-cloud-console-add2fe86edc023e890606e42075f14170031055c-sock"},"extHostTerminalId":"8b05b8b8-c744-4722-baf7-b23da546e8e4","isExtensionOwnedTerminal":true,"isTransient":true}
2023-05-11 19:06:06.676 [debug] Buffer content tracker: 0 lines cached
2023-05-11 19:06:06.677 [debug] Viewport content update complete, 0 lines in the viewport
2023-05-11 19:06:06.677 [debug] Buffer content tracker: set 0 lines
2023-05-11 19:06:06.709 [trace] Webgl was loaded
2023-05-11 19:06:06.758 [debug] Buffer content tracker: 0 lines cached
2023-05-11 19:06:06.758 [debug] Viewport content update complete, 7 lines in the viewport
2023-05-11 19:06:06.758 [debug] Buffer content tracker: set 7 lines
2023-05-11 19:06:06.765 [debug] Buffer content tracker: 0 lines cached
2023-05-11 19:06:06.765 [debug] Viewport content update complete, 0 lines in the viewport
2023-05-11 19:06:06.765 [debug] Buffer content tracker: set 0 lines
2023-05-11 19:06:06.779 [trace] [DEBOUNCE: Links] for vscode-terminal:/29a05e1056e2ad43353814aa14cbb116/12#accessible-buffer- is 1000ms
2023-05-11 19:06:06.851 [debug] Terminal process ready (shellProcessId: 2388)
2023-05-11 19:06:06.857 [debug] terminalInstance added capability 3
2023-05-11 19:06:08.621 [debug] Terminal process exit (instanceId: 12) with code undefined
2023-05-11 19:06:08.621 [debug] Terminal process exit (instanceId: 12) state 6
2023-05-11 19:06:08.621 [trace] terminalInstance#dispose (instanceId: 12)
2023-05-11 19:06:08.692 [debug] Buffer content tracker: 0 lines cached
2023-05-11 19:06:08.692 [debug] Viewport content update complete, 7 lines in the viewport
2023-05-11 19:06:08.692 [debug] Buffer content tracker: set 7 lines
2023-05-11 19:06:10.955 [trace] Started polling file:///c%3A/Users/mz1245/AppData/Roaming/Code/logs/20230511T182740/window1/renderer.log
2023-05-11 19:06:17.685 [trace] InteractiveSessionService#onWillSaveState: Persisting 0 sessions
2023-05-11 19:06:19.590 [trace] CommandService#executeCommand notification.clear
2023-05-11 19:06:20.669 [trace] CommandService#executeCommand notification.clear
2023-05-11 19:06:20.679 [trace] CommandService#executeCommand _setContext
2023-05-11 19:06:21.674 [error] Disconnecte
From: Alex Weininger ***@***.***>
Sent: Thursday, May 11, 2023 6:51 PM
To: microsoft/vscode-azure-account ***@***.***>
Cc: ZHANG, MICHAEL ***@***.***>; Mention ***@***.***>
Subject: Re: [microsoft/vscode-azure-account] VSCode failed to Azure sign in and cannot open Azure Bash after latest upgrade (Issue #801)
Could you share the logs when it fails? See the Enable and View Logs<https://urldefense.com/v3/__https:/github.com/microsoft/vscode-azure-account/wiki/Enable-and-view-logs__;!!BhdT!mGbUHc1pKcXkmIa3c19YEv_AftpeHULUJ01dy8w6R0ho5Q_4RwPLYhQgA1L9G9emPojAoZqVGNs2IERwyv5D9Sg$> section of the wiki for how to capture and share Azure Account extension logs.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/microsoft/vscode-azure-account/issues/801*issuecomment-1544791156__;Iw!!BhdT!mGbUHc1pKcXkmIa3c19YEv_AftpeHULUJ01dy8w6R0ho5Q_4RwPLYhQgA1L9G9emPojAoZqVGNs2IERw2Zoq0mM$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ASOHEBYCNQKLDT3OZCOICR3XFVUODANCNFSM6AAAAAAXZ7NDYE__;!!BhdT!mGbUHc1pKcXkmIa3c19YEv_AftpeHULUJ01dy8w6R0ho5Q_4RwPLYhQgA1L9G9emPojAoZqVGNs2IERwz-2-u0E$>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
|
AND also find this message in another log:
2023-05-11 19:07:13.048 [trace] Error while resolving configuration file 'vscode-userdata:/c%3A/Users/mz1245/AppData/Roaming/Code/User/tasks.json': Unable to read file 'vscode-userdata:/c:/Users/mz1245/AppData/Roaming/Code/User/tasks.json' (Error: Unable to resolve nonexistent file 'vscode-userdata:/c:/Users/mz1245/AppData/Roaming/Code/User/tasks.json')
There is no such tasks.json file in that directory, but instead, there is settings.json .
Hopefully this can help.
Sorry, I have to drop now.
Thanks,
Michael,
From: ZHANG, MICHAEL
Sent: Thursday, May 11, 2023 7:12 PM
To: microsoft/vscode-azure-account ***@***.***>
Subject: RE: [microsoft/vscode-azure-account] VSCode failed to Azure sign in and cannot open Azure Bash after latest upgrade (Issue #801)
It appears that no problem to do sign in to Azure account, but it failed when open Azure Bash shell. Here is the log for Window.
2023-05-11 19:05:55.351 [trace] KeybindingService#dispatch Enter [ No matching keybinding ]
2023-05-11 19:06:03.471 [trace] Stopped polling file:///c%3A/Users/mz1245/AppData/Roaming/Code/logs/20230511T182740/window1/renderer.log
2023-05-11 19:06:06.522 [trace] onWillActivateByEvent: onTerminalProfile:azure-account.cloudShellBash
2023-05-11 19:06:06.524 [trace] CommandService#executeCommand _setContext
2023-05-11 19:06:06.633 [trace] terminalInstance#ctor (instanceId: 12) {"name":"Azure Cloud Shell (Bash)","executable":"node.exe","args":["-e","require('c:\\\\Users\\\\mz1245\\\\.vscode\\\\extensions\\\\ms-vscode.azure-account-0.11.4\\\\dist\\\\cloudConsoleLauncher').main()"],"icon":{"id":"azure"},"ignoreConfigurationCwd":true,"env":{"CLOUD_CONSOLE_IPC":"\\\\.\\pipe\\vscode-cloud-console-add2fe86edc023e890606e42075f14170031055c-sock<file://.//pipe/vscode-cloud-console-add2fe86edc023e890606e42075f14170031055c-sock>"},"extHostTerminalId":"8b05b8b8-c744-4722-baf7-b23da546e8e4","isExtensionOwnedTerminal":true,"isTransient":true}
2023-05-11 19:06:06.676 [debug] Buffer content tracker: 0 lines cached
2023-05-11 19:06:06.677 [debug] Viewport content update complete, 0 lines in the viewport
2023-05-11 19:06:06.677 [debug] Buffer content tracker: set 0 lines
2023-05-11 19:06:06.709 [trace] Webgl was loaded
2023-05-11 19:06:06.758 [debug] Buffer content tracker: 0 lines cached
2023-05-11 19:06:06.758 [debug] Viewport content update complete, 7 lines in the viewport
2023-05-11 19:06:06.758 [debug] Buffer content tracker: set 7 lines
2023-05-11 19:06:06.765 [debug] Buffer content tracker: 0 lines cached
2023-05-11 19:06:06.765 [debug] Viewport content update complete, 0 lines in the viewport
2023-05-11 19:06:06.765 [debug] Buffer content tracker: set 0 lines
2023-05-11 19:06:06.779 [trace] [DEBOUNCE: Links] for vscode-terminal:/29a05e1056e2ad43353814aa14cbb116/12#accessible-buffer- is 1000ms
2023-05-11 19:06:06.851 [debug] Terminal process ready (shellProcessId: 2388)
2023-05-11 19:06:06.857 [debug] terminalInstance added capability 3
2023-05-11 19:06:08.621 [debug] Terminal process exit (instanceId: 12) with code undefined
2023-05-11 19:06:08.621 [debug] Terminal process exit (instanceId: 12) state 6
2023-05-11 19:06:08.621 [trace] terminalInstance#dispose (instanceId: 12)
2023-05-11 19:06:08.692 [debug] Buffer content tracker: 0 lines cached
2023-05-11 19:06:08.692 [debug] Viewport content update complete, 7 lines in the viewport
2023-05-11 19:06:08.692 [debug] Buffer content tracker: set 7 lines
2023-05-11 19:06:10.955 [trace] Started polling file:///c%3A/Users/mz1245/AppData/Roaming/Code/logs/20230511T182740/window1/renderer.log
2023-05-11 19:06:17.685 [trace] InteractiveSessionService#onWillSaveState: Persisting 0 sessions
2023-05-11 19:06:19.590 [trace] CommandService#executeCommand notification.clear
2023-05-11 19:06:20.669 [trace] CommandService#executeCommand notification.clear
2023-05-11 19:06:20.679 [trace] CommandService#executeCommand _setContext
2023-05-11 19:06:21.674 [error] Disconnecte
From: Alex Weininger ***@***.******@***.***>>
Sent: Thursday, May 11, 2023 6:51 PM
To: microsoft/vscode-azure-account ***@***.******@***.***>>
Cc: ZHANG, MICHAEL ***@***.******@***.***>>; Mention ***@***.******@***.***>>
Subject: Re: [microsoft/vscode-azure-account] VSCode failed to Azure sign in and cannot open Azure Bash after latest upgrade (Issue #801)
Could you share the logs when it fails? See the Enable and View Logs<https://urldefense.com/v3/__https:/github.com/microsoft/vscode-azure-account/wiki/Enable-and-view-logs__;!!BhdT!mGbUHc1pKcXkmIa3c19YEv_AftpeHULUJ01dy8w6R0ho5Q_4RwPLYhQgA1L9G9emPojAoZqVGNs2IERwyv5D9Sg$> section of the wiki for how to capture and share Azure Account extension logs.
—
Reply to this email directly, view it on GitHub<https://urldefense.com/v3/__https:/github.com/microsoft/vscode-azure-account/issues/801*issuecomment-1544791156__;Iw!!BhdT!mGbUHc1pKcXkmIa3c19YEv_AftpeHULUJ01dy8w6R0ho5Q_4RwPLYhQgA1L9G9emPojAoZqVGNs2IERw2Zoq0mM$>, or unsubscribe<https://urldefense.com/v3/__https:/github.com/notifications/unsubscribe-auth/ASOHEBYCNQKLDT3OZCOICR3XFVUODANCNFSM6AAAAAAXZ7NDYE__;!!BhdT!mGbUHc1pKcXkmIa3c19YEv_AftpeHULUJ01dy8w6R0ho5Q_4RwPLYhQgA1L9G9emPojAoZqVGNs2IERwz-2-u0E$>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
|
Could you share the logs from the Azure Account output channel? Please enable trace logs for the Azure Account extension first.
See the Enable and View Logs section of the wiki for how to capture and share Azure Account extension logs. |
|
I am also seeing similar issues with 1.78.2 and Azure Account v0.11.5 when trying to connect via the Azure Automation extension. The logs I'm getting are: 2023-05-22 10:25:13.339 [info] MSAL: [Mon, 22 May 2023 15:25:13 GMT] : @azure/msal-node@1.14.6 : Info - getTokenCache called I've also tried disabling everything but the Azure Account extension and it doesn't make a difference. Downgrading to 0.11.3 as noted above also doesn't help. |
Does this occur consistently? Yes
Repro steps:
Action: azure-account.loginToCloud
Error type: AzureLoginError
Error Message: Offline
Version: 0.11.4
OS: win32
OS Release: 10.0.22000
Product: Visual Studio Code
Product Version: 1.78.0
Language: en
Call Stack
All works fine until last week VSCode upgrade automatically, (I just simple answered Yes ). I have uninstalled /re-install node.js, vscode et. al. But no luck! Does anyone encounter the same problem last week after upgrade?
The text was updated successfully, but these errors were encountered: