The SSH Tool under Development Tools fails in Chrome Browser but works in Safari

Dhananjay Agarwal 20

When I use the SSH tool under Development Tools in Azure Web Apps, or use the default App Domain link in webapp Overview such as xxxx.eastus2-01.azurewebsites.net, I get the following message:

This site can’t provide a secure connection

xxxx.eastus2-01.azurewebsites.net sent an invalid response.

ERR_SSL_PROTOCOL_ERROR

However, this issue doesn't arise when using Safari. Does anyone know what is causing this and how I can fix this in the Chrome Browser?

1 answer

Divyesh Govaerdhanan 8,345 Reputation points

2025-07-30T23:35:14.7066667+00:00
Hello,

Welcome to Microsoft Q&A,

This could most likely be related to SSL/TLS handshake compatibility, browser-specific caching, or certificate handling. Chrome is stricter about certificate policies and may cache old/broken SSL states.

In Chrome, open this URL: chrome://net-internals/#hsts

Under "Delete domain security policies", enter your domain (xxxx.eastus2-01.azurewebsites.net) and click Delete.

Then clear SSL state:Settings → Privacy and security → Security → Advanced → Manage Certificates → Clear SSL state

Restart Chrome and try again.

If this does not help, please check Chrome extensions (ad blockers, firewalls) or antivirus software (e.g., Avast, Kaspersky) as these can strip SSL headers or block ports (like 443). Try incognito.

Please Upvote and accept the answer if it helps!!
Please sign in to rate this answer.
Dhananjay Agarwal 20 Reputation points

2025-08-03T14:18:16.34+00:00

Thank you for your answer. In my troubleshooting, I had deleted the cookies but didn't close the Chrome browser and reopen it. I also rebooted my machine once before I got your answer. When I got your answer, I tried to validate the issue before following your suggestions. However, the problem was resolved. Not sure what fixed it. Hence, I didn't use your recommendations. I will refer to them when the issue arises again in the future. Thank you for taking the time to respond.

Divyesh Govaerdhanan 8,345 Reputation points

2025-08-03T15:47:44.6966667+00:00

Hi Dhananjay Agarwal,

Thanks for your update, and I’m glad the issue was resolved. Sometimes browser sessions or system reboots do the trick. Even if the exact fix wasn't traced to a specific action, your experience confirms it may be a temporary state, possibly tied to browser caching or SSL negotiation.

If others run into a similar issue, the troubleshooting steps I shared can help isolate the cause and avoid a full reboot. If the issue recurs and those steps help resolve it, feel free to mark the answer as accepted to help others in the community facing the same problem.

Appreciate your engagement, and best of luck with your work on Azure!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Your answer