starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Cannot Connect to Cloud Shell anymore #20622

New Issue
Closed
opened 2026-01-31 07:19:16 +00:00 by claunia · 20 comments
claunia commented 2026-01-31 07:19:16 +00:00
Owner
Copy Link

Originally created by @bferg317 on GitHub (Oct 3, 2023).

Windows Terminal version

1.17.11461.0

Windows build number

10.0.22621.2283

Other Software

No response

Steps to reproduce

  1. Create Azure Cloud Shell Tab
  2. Step through browser login
  3. Select tenant

Expected Behavior

Expecting a cloud shell terminal.

Actual Behavior

Requesting a cloud shell instance...
Succeeded.
Requesting a terminal (this might take a while)...

[process exited with code 1 (0x00000001)]

Originally created by @bferg317 on GitHub (Oct 3, 2023). ### Windows Terminal version 1.17.11461.0 ### Windows build number 10.0.22621.2283 ### Other Software _No response_ ### Steps to reproduce 1. Create Azure Cloud Shell Tab 2. Step through browser login 3. Select tenant ### Expected Behavior Expecting a cloud shell terminal. ### Actual Behavior Requesting a cloud shell instance... Succeeded. Requesting a terminal (this might take a while)... [process exited with code 1 (0x00000001)]
claunia added the Issue-BugIn-PRNeeds-Tag-FixProduct-TerminalArea-AzureShell labels 2026-01-31 07:19:17 +00:00
claunia commented 2026-01-31 07:19:19 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 4, 2023):

Are you sure that's all the output that was displayed in the Terminal? We're pretty confident that there's supposed to be an exception handler in that path that should have written out the error message from Azure.....

The exception handler only handles std::exceptions. Maybe another type of exception was thrown.
4145f18768/src/cascadia/TerminalConnection/AzureConnection.cpp (L107-L107)

or there's no exception text

@zadjii-msft commented on GitHub (Oct 4, 2023): Are you sure that's all the output that was displayed in the Terminal? We're pretty confident that there's supposed to be an exception handler in that path that should have written out the error message from Azure..... The exception handler only handles `std::exceptions`. Maybe another type of exception was thrown. https://github.com/microsoft/terminal/blob/4145f18768772270da03f9ea56b5ec6f7157375c/src/cascadia/TerminalConnection/AzureConnection.cpp#L107-L107 or there's no exception text
claunia commented 2026-01-31 07:19:19 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 4, 2023):

A WPR trace of this would be helpful: Capturing a Debug ETL Trace

@zadjii-msft commented on GitHub (Oct 4, 2023): A WPR trace of this would be helpful: [Capturing a Debug ETL Trace](https://github.com/microsoft/terminal/wiki/Toubleshooting-Tips#capturing-a-debug-etl-trace)
claunia commented 2026-01-31 07:19:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Oct 12, 2023):

Oh also a note: a winrt exception does NOT inherit from std::exception: https://github.com/microsoft/cppwinrt/issues/1367

@zadjii-msft commented on GitHub (Oct 12, 2023): Oh also a note: a winrt exception does NOT inherit from `std::exception`: https://github.com/microsoft/cppwinrt/issues/1367
claunia commented 2026-01-31 07:19:20 +00:00
Author
Owner
Copy Link

@bferg317 commented on GitHub (Oct 12, 2023):

A WPR trace of this would be helpful: Capturing a Debug ETL Trace

I have uploaded the ETL to Feedback Hub: https://aka.ms/AAn1y80

Also, no, the only output I get is "[process exited with code 1 (0x00000001)]." I even tried installing the Azure CLI latest version and manually editing the winterm json to point to that .exe and it returns the same.

Additional info: this behavior started about the same time Cloud Shell stopped working in vscode; though in vscode it manifests as not displaying any available subs/directories when I try to start the shell. Connect-AzAccount from pwsh 7.3.7 in winterm allows me to run commands just fine, but this requires some adaption to the runbook I'm building so testing isn't 1:1.

image
image

@bferg317 commented on GitHub (Oct 12, 2023): > A WPR trace of this would be helpful: [Capturing a Debug ETL Trace](https://github.com/microsoft/terminal/wiki/Toubleshooting-Tips#capturing-a-debug-etl-trace) I have uploaded the ETL to Feedback Hub: https://aka.ms/AAn1y80 Also, no, the only output I get is "[process exited with code 1 (0x00000001)]." I even tried installing the Azure CLI latest version and manually editing the winterm json to point to that .exe and it returns the same. Additional info: this behavior started about the same time Cloud Shell stopped working in vscode; though in vscode it manifests as not displaying any available subs/directories when I try to start the shell. Connect-AzAccount from pwsh 7.3.7 in winterm allows me to run commands just fine, but this requires some adaption to the runbook I'm building so testing isn't 1:1. ![image](https://github.com/microsoft/terminal/assets/46008360/b79800dd-232f-4f5b-8b20-582f81745764) ![image](https://github.com/microsoft/terminal/assets/46008360/25371c8e-62ad-4e9e-a5c0-5ad6b7c7df42)
claunia commented 2026-01-31 07:19:20 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Oct 13, 2023):

We've gotten a few of these reports recently so there's likely something here. I have collected traces of the login process from someone who was unable to connect and the current suspicion is that there was an API change on the Azure side that we aren't conforming to. We have set up a meeting with the Cloud Shell team, will update here once that's done.

@PankajBhojwani commented on GitHub (Oct 13, 2023): We've gotten a few of these reports recently so there's likely something here. I have collected traces of the login process from someone who was unable to connect and the current suspicion is that there was an API change on the Azure side that we aren't conforming to. We have set up a meeting with the Cloud Shell team, will update here once that's done.
claunia commented 2026-01-31 07:19:20 +00:00
Author
Owner
Copy Link

@klercke commented on GitHub (Oct 23, 2023):

@PankajBhojwani Sorry to be pushy, but do you have an update on this? I manage ~100 tenants through cloud shell so this is slowing me down quite a bit.

Thanks for the transparency!

@klercke commented on GitHub (Oct 23, 2023): @PankajBhojwani Sorry to be pushy, but do you have an update on this? I manage ~100 tenants through cloud shell so this is slowing me down quite a bit. Thanks for the transparency!
claunia commented 2026-01-31 07:19:20 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Oct 23, 2023):

A few things - the Azure Cloud Shell team is undergoing some amount of migration regarding where they store the sessions, which could explain why only some users are facing this issue and why it seems to sometimes be intermittent. Other than that, there might be some post-handling of the URLs that Terminal needs to do to make sure our requests are going to the right place and are well formed. We are continuing to investigate this!

@PankajBhojwani commented on GitHub (Oct 23, 2023): A few things - the Azure Cloud Shell team is undergoing some amount of migration regarding where they store the sessions, which could explain why only some users are facing this issue and why it seems to sometimes be intermittent. Other than that, there might be some post-handling of the URLs that Terminal needs to do to make sure our requests are going to the right place and are well formed. We are continuing to investigate this!
claunia commented 2026-01-31 07:19:21 +00:00
Author
Owner
Copy Link

@shurick81 commented on GitHub (Jan 19, 2024):

Is not this happening again?

image

But Azure health does not show any regression, so it did not show any issues back in October 2023: https://azure.status.microsoft/en-us/status/history/

@shurick81 commented on GitHub (Jan 19, 2024): Is not this happening again? ![image](https://github.com/microsoft/terminal/assets/11289124/b47bcc71-88ec-4784-a97c-5a16ec1c27a7) But Azure health does not show any regression, so it did not show any issues back in October 2023: https://azure.status.microsoft/en-us/status/history/
claunia commented 2026-01-31 07:19:21 +00:00
Author
Owner
Copy Link

@GraniteGolem commented on GitHub (Jan 19, 2024):

Is not this happening again?

image

But Azure health does not show any regression, so it did not show any issues back in October 2023: https://azure.status.microsoft/en-us/status/history/

Yes, I am getting this as well. Luckily this is not urgent for me. Will check back tomorrow.

@GraniteGolem commented on GitHub (Jan 19, 2024): > Is not this happening again? > > ![image](https://private-user-images.githubusercontent.com/11289124/298156719-b47bcc71-88ec-4784-a97c-5a16ec1c27a7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDU2ODgzOTEsIm5iZiI6MTcwNTY4ODA5MSwicGF0aCI6Ii8xMTI4OTEyNC8yOTgxNTY3MTktYjQ3YmNjNzEtODhlYy00Nzg0LWE5N2MtNWExNmVjMWMyN2E3LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAxMTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMTE5VDE4MTQ1MVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTBiYWRmMmIxYjUyOTZhMjcyMzhkNjc3NGI1MDYzMzMwYjIyMmViYzU0NDAyNGQzOTI5ZDBhZTg3ZGViNzA0Y2UmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.zeSMN_pS6xBW1eVDBsT8fxl6YS8obzucEQUOgySIYgE) > > But Azure health does not show any regression, so it did not show any issues back in October 2023: https://azure.status.microsoft/en-us/status/history/ Yes, I am getting this as well. Luckily this is not urgent for me. Will check back tomorrow.
claunia commented 2026-01-31 07:19:21 +00:00
Author
Owner
Copy Link

@brianbaldock commented on GitHub (Jan 19, 2024):

Experiencing the same issue on my end.
image
image

@brianbaldock commented on GitHub (Jan 19, 2024): Experiencing the same issue on my end. ![image](https://github.com/microsoft/terminal/assets/72090857/0d0bc474-4623-4b76-bf04-84db0c842aba) ![image](https://github.com/microsoft/terminal/assets/72090857/9d86073a-fd91-460a-b539-2f186982299a)
claunia commented 2026-01-31 07:19:21 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Jan 19, 2024):

I am not able to access the cloud shell even through the azure portal in my browser, which leads me to believe this is an issue on the server side, not Terminal. Can you access the cloud shell in your browser?

image

@PankajBhojwani commented on GitHub (Jan 19, 2024): I am not able to access the cloud shell even through the azure portal in my browser, which leads me to believe this is an issue on the server side, not Terminal. Can you access the cloud shell in your browser? ![image](https://github.com/microsoft/terminal/assets/26824113/42529209-0e2c-45e5-b440-92b8e25a9edc)
claunia commented 2026-01-31 07:19:21 +00:00
Author
Owner
Copy Link

@brianbaldock commented on GitHub (Jan 19, 2024):

I am not able to access the cloud shell even through the azure portal in my browser, which leads me to believe this is an issue on the server side, not Terminal. Can you access the cloud shell in your browser?

image

Nope, getting this as an error:
image

@brianbaldock commented on GitHub (Jan 19, 2024): > I am not able to access the cloud shell even through the azure portal in my browser, which leads me to believe this is an issue on the server side, not Terminal. Can you access the cloud shell in your browser? > > ![image](https://private-user-images.githubusercontent.com/26824113/298169451-42529209-0e2c-45e5-b440-92b8e25a9edc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MDU2OTA5NjAsIm5iZiI6MTcwNTY5MDY2MCwicGF0aCI6Ii8yNjgyNDExMy8yOTgxNjk0NTEtNDI1MjkyMDktMGUyYy00NWU1LWI0NDAtOTJiOGUyNWE5ZWRjLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDAxMTklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwMTE5VDE4NTc0MFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTg3NmU1ZTVkZmE1ZTFkZGQ2MDYxNTBmMDI5ZDkyOGRhZDQxM2ZkNGE4MmQ5MDU1ZGMxNDlkMjdhMjA1MGRhMWImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.baEL9v52ZjgKebDccplTO4ZVDjYHZDGn0JhKFF9fOQs) Nope, getting this as an error: ![image](https://github.com/microsoft/terminal/assets/72090857/b8b92620-b73f-4144-aeda-a7d7b1c56c94)
claunia commented 2026-01-31 07:19:22 +00:00
Author
Owner
Copy Link

@PankajBhojwani commented on GitHub (Jan 19, 2024):

Yep so that pretty much confirms its a server side issue. We're going to have to wait on the Cloud Shell team to fix it on their end.

@PankajBhojwani commented on GitHub (Jan 19, 2024): Yep so that pretty much confirms its a server side issue. We're going to have to wait on the Cloud Shell team to fix it on their end.
claunia commented 2026-01-31 07:19:22 +00:00
Author
Owner
Copy Link

@brianbaldock commented on GitHub (Jan 20, 2024):

Works now 👍 thanks @ team

@brianbaldock commented on GitHub (Jan 20, 2024): Works now 👍 thanks @ team
claunia commented 2026-01-31 07:19:22 +00:00
Author
Owner
Copy Link

@shurick81 commented on GitHub (Jan 20, 2024):

Shouldn't this be visible in the Azure status pages?

@shurick81 commented on GitHub (Jan 20, 2024): Shouldn't this be visible in the Azure status pages?
claunia commented 2026-01-31 07:19:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Jan 22, 2024):

Shouldn't this be visible in the Azure status pages?

I'm sorry. The Windows Terminal team (as a client of Azure just like y'all) does not control whether--or what--information shows up on the Azure status page.

@DHowett commented on GitHub (Jan 22, 2024): > Shouldn't this be visible in the Azure status pages? I'm sorry. The Windows Terminal team (as a client of Azure just like y'all) does not control whether--or what--information shows up on the Azure status page.
claunia commented 2026-01-31 07:19:23 +00:00
Author
Owner
Copy Link

@donnykwitty commented on GitHub (Jan 30, 2024):

This issue is fixed?
Why am I experiencing it now?

Requesting a cloud shell instance...
Succeeded.
Requesting a terminal (this might take a while)...

[process exited with code 1 (0x00000001)]
You can now close this terminal with Ctrl+D, or press Enter to restart.
@donnykwitty commented on GitHub (Jan 30, 2024): This issue is fixed? Why am I experiencing it now? ``` Requesting a cloud shell instance... Succeeded. Requesting a terminal (this might take a while)... [process exited with code 1 (0x00000001)] You can now close this terminal with Ctrl+D, or press Enter to restart. ```
claunia commented 2026-01-31 07:19:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 30, 2024):

@donnykwitty Looks like the fix made it into v1.18.3181.0 (Stable) / v1.19.3172.0 (Preview). Which version are you on?

There was also an incident upstream: https://azure.status.microsoft/en-us/status/history/

image

@zadjii-msft commented on GitHub (Jan 30, 2024): @donnykwitty Looks like the fix made it into [v1.18.3181.0](https://github.com/microsoft/terminal/releases/tag/v1.18.3181.0) (Stable) / [v1.19.3172.0](https://github.com/microsoft/terminal/releases/tag/v1.19.3172.0) (Preview). Which version are you on? There was also an incident upstream: https://azure.status.microsoft/en-us/status/history/ ![image](https://github.com/microsoft/terminal/assets/18356694/9f3f5b6e-3561-4605-b3a9-9509bb4048fb)
claunia commented 2026-01-31 07:19:23 +00:00
Author
Owner
Copy Link

@shurick81 commented on GitHub (Jan 30, 2024):

now I can see this too @zadjii-msft !

@shurick81 commented on GitHub (Jan 30, 2024): now I can see this too @zadjii-msft !
claunia commented 2026-01-31 07:19:23 +00:00
Author
Owner
Copy Link

@donnykwitty commented on GitHub (Jan 30, 2024):

@zadjii-msft Thanks! My bad. I thought Terminal had been updated via Windows update--it hadn't.

@donnykwitty commented on GitHub (Jan 30, 2024): @zadjii-msft Thanks! My bad. I thought Terminal had been updated via Windows update--it hadn't.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-AzureShell In-PR Issue-Bug Needs-Tag-Fix Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#20622
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?