Skip to content

Commit cdaae58

Browse files
authored
Merge pull request #1798 from abarqawi/patch-14
Update web-socket-is-closed-or-could-not-be-opened.md
2 parents 07b6f48 + f1aeff7 commit cdaae58

1 file changed

Lines changed: 6 additions & 4 deletions

File tree

support/azure/azure-container-instances/connectivity/web-socket-is-closed-or-could-not-be-opened.md

Lines changed: 6 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,11 +1,11 @@
11
---
22
title: Error - Web socket is closed or could not be opened
33
description: Learn how to resolve the (Web socket is closed or could not be opened) error. This error prevents you from connecting to your container from a virtual network.
4-
ms.date: 12/28/2023
4+
ms.date: 02/24/2025
55
author: tysonfms
66
ms.author: tysonfreeman
77
editor: v-jsitser
8-
ms.reviewer: v-leedennis
8+
ms.reviewer: albarqaw, v-weizhu, v-leedennis
99
ms.service: azure-container-instances
1010
ms.custom: sap:Connectivity
1111
#Customer intent: As an Azure administrator, I want to learn how to resolve the "Web socket is closed or could not be opened" error so that I can successfully deploy an image onto a container instance.
@@ -22,10 +22,12 @@ When you try to connect to your container from the Azure portal, you receive the
2222
2323
## Cause
2424

25-
Your firewall blocks access to port 19390. This port is required to connect to Container Instances from the Azure portal when container groups are deployed in virtual networks.
25+
Your firewall or corporate proxy blocks access to port 19390. This port is required to connect to Container Instances from the Azure portal when container groups are deployed in virtual networks.
2626

2727
## Solution
2828

29-
Allow ingress to TCP port 19390 in your firewall. At a minimum, make sure that your firewall gives access to that port for all public client IP addresses that the Azure portal has to connect to.
29+
To resolve this error, allow ingress to TCP port 19390 in your firewall. At a minimum, make sure that your firewall gives access to that port for all public client IP addresses that the Azure portal has to connect to.
30+
31+
In some scenarios where the corporate proxy blocks port 19390, allow this port for corporate proxy, and then verify the traffic by using the **Network** tab in the browser developer tools.
3032

3133
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]

0 commit comments

Comments
 (0)