Azure Cloud Shell - Stuck at connecting terminal

Kevin Flückiger 31 Reputation points
2022-11-08T08:56:06.887+00:00

In my Free Trial account I have problems getting into a cloud shell. With my corporate account on the same machine, same browser, everything works flawlessly.

I don't get the ERR_CERT_AUTHORITY_INVALID error mentioned in some other questions, but a bunch of other errors (see attached Image). I already tried to delete the storage account but the result stays the same. So any help would be highly appreciated.

258166-000003.jpg

Azure Cloud Services
Azure Cloud Services
An Azure platform as a service offer that is used to deploy web and cloud applications.
677 questions
{count} vote

Accepted answer
  1. kobulloc-MSFT 26,131 Reputation points Microsoft Employee
    2022-12-01T06:07:18.393+00:00

    Hello, @Kevin Flückiger !

    Thank you again for all of your help in troubleshooting this issue!

    Azure Cloud Shell is stuck at Connecting terminal.... The console log shows a net::ERR_EMPTY_RESPONSE error.
    Most Azure Cloud Shell errors can be resolved by restarting the cloud shell (by clicking the power icon), by resetting the user settings (under the gear icon), or in extreme cases, by deleting your cloud shell storage (a storage account is created for the Azure Cloud Shell the first time you use it with a name similar to cs123456ab7c9012d in the cloud-shell-storage-regionname resource group).

    This case was unique in that a corporate account did not run into this error while a trial account did, even when using the same machine and the same browser. Ultimately we used the following for troubleshooting:

    • Email address of the account in question
    • Date and time the issue last occurred
    • The tenantid information of the account (How to find your tenant ID)
    • Response from the POST call (ERR_EMPTY_RESPONSE)

    We were able to identify that there were some websocket errors when attempting to mount the file share. If you encounter this, please start a thread so that we can reach out privately to collect the troubleshooting information above and investigate this further.

    Screenshot from @Kevin Flückiger

    265945-image.png

    Additional reading:

    0 comments No comments

0 additional answers

Sort by: Most helpful