Press F12 - go to developer mode (console)
You can see there an error Failed to load resource:net::ERR_CERT_AUTHORITY_INVALID
Click that link and click in your browser: "Proceed to *.gateway02.westus2.console.azure.com (unsafe)"
You get error
Return back to Azure and refresh the terminal
Azure Cloud Shell - Failed to request a terminal.
Until yesterday my Azure cloud shell was working fine, but now i see an error when requesting cloud shell terminal, as below
Requesting a Cloud Shell.Succeeded.
Connecting terminal...
Failed to request a terminal.
Any idea what can cause this or how to get past this as im not able to proceed without a terminal.
4 answers
Sort by: Most helpful
-
Douglas Vann 16 Reputation points
2022-03-27T02:38:37.487+00:00 -
Carlos Solís Salazar 18,061 Reputation points MVP
2022-03-22T13:37:09.957+00:00 Hi @Anonymous
Thank you for asking this question on the **Microsoft Q&A Platform. **
Please, follow all recommendations of https://learn.microsoft.com/en-us/azure/cloud-shell/troubleshooting
If you still have errors, please share screenshots.
Hope this helps,
Carlos Solís Salazar----------
Accept Answer and Upvote, if any of the above helped, this threat can help others in the community looking for remediation for similar issues.
NOTE: To answer you as quickly as possible, please mention me in your reply.
-
James Hightower Test Account 1 Reputation point
2022-03-29T19:41:23.637+00:00 @Douglas Vann is right. It seens that MS updated gatewayXX.westus.console.azure.com with new certs, but failed to install the required IM certs.
Azure is updating their TLS certs, as covered in this doc: tls-certificate-changesIn short, they are changing from certs chained to the Baltimore CyberTrust Root, to certs chained up to a Digicert root. However, when they updated gatewayXX.westus.console.azure.com, they installed certs signed by "Microsoft Azure TLS Issuing CA 01" but did not include an IM cert connecting CA 01 to the Digicert root, or any other root your browser would recognize. Fail!
The work-around is to grab the missing IM cert package from Microsoft, and import it into your browser.
The IM cert is available from Azure's CA page found here: certificate-authorities
The direct download link is Microsoft%20Azure%20TLS%20Issuing%20CA%2001%20-%20xsign.crt
Importing this cert into your browser is browser specific (on Chrome for Linux, I found it as settings->Security and Privacy->Manage Certificates->Authorities)
Once the IM cert has been imported, your cloud shells should work again.Good luck all!
-
Muhammad Anas Ansari 1 Reputation point
2022-08-03T06:39:15.99+00:00 The possible reason of the failure is that you need to configure your network setting to enable sending https and WebSockets request.