You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: support/azure/azure-container-instances/connectivity/web-socket-is-closed-or-could-not-be-opened.md
+6-4Lines changed: 6 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,11 +1,11 @@
1
1
---
2
2
title: Error - Web socket is closed or could not be opened
3
3
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
5
5
author: tysonfms
6
6
ms.author: tysonfreeman
7
7
editor: v-jsitser
8
-
ms.reviewer: v-leedennis
8
+
ms.reviewer: albarqaw, v-weizhu, v-leedennis
9
9
ms.service: azure-container-instances
10
10
ms.custom: sap:Connectivity
11
11
#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
22
22
23
23
## Cause
24
24
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.
26
26
27
27
## Solution
28
28
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.
30
32
31
33
[!INCLUDE [Azure Help Support](../../../includes/azure-help-support.md)]
Copy file name to clipboardExpand all lines: support/azure/azure-kubernetes/connectivity/insufficientsubnetsize-error-advanced-networking.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: InsufficientSubnetSize error code
3
3
description: Learn how to fix an InsufficientSubnetSize error that occurs when you deploy an Azure Kubernetes Service (AKS) cluster that uses advanced networking.
Copy file name to clipboardExpand all lines: support/azure/azure-kubernetes/create-upgrade-delete/error-code-poddrainfailure.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,7 +1,7 @@
1
1
---
2
2
title: Troubleshoot UpgradeFailed errors due to eviction failures caused by PDBs
3
3
description: Learn how to troubleshoot UpgradeFailed errors due to eviction failures caused by Pod Disruption Budgets when you try to upgrade an Azure Kubernetes Service cluster.
Copy file name to clipboardExpand all lines: support/azure/azure-kubernetes/create-upgrade-delete/error-code-vhdfilenotfound.md
+7-7Lines changed: 7 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,28 +1,28 @@
1
1
---
2
2
title: Troubleshoot the ERR_VHD_FILE_NOT_FOUND error code
3
-
description: Learn how to troubleshoot the ERR_VHD_FILE_NOT_FOUND error (124) when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
4
-
ms.date: 10/14/2024
3
+
description: Learn how to troubleshoot the ERR_VHD_FILE_NOT_FOUND error (65) when you try to create and deploy an Azure Kubernetes Service (AKS) cluster.
#Customer intent: As an Azure Kubernetes user, I want to troubleshoot the ERR_VHD_FILE_NOT_FOUND error code (or error code OutboundConnFailVMExtensionError, error number 50 - or error code ERR_K8S_API_SERVER_CONN_FAIL, error number 51) so that I can successfully create and deploy an Azure Kubernetes Service (AKS) cluster.
9
9
ms.custom: sap:Create, Upgrade, Scale and Delete operations (cluster or nodepool)
10
10
---
11
-
# Troubleshoot the ERR_VHD_FILE_NOT_FOUND error code (124)
11
+
# Troubleshoot the ERR_VHD_FILE_NOT_FOUND error code (65)
12
12
13
-
This article discusses how to identify and resolve the `ERR_VHD_FILE_NOT_FOUND` error code (error code number 124) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
13
+
This article discusses how to identify and resolve the `ERR_VHD_FILE_NOT_FOUND` error code (error code number 65) that occurs when you try to create and deploy a Microsoft Azure Kubernetes Service (AKS) cluster.
14
14
15
15
## Symptoms
16
16
17
17
When you try to create an AKS cluster, you receive the following error message:
18
18
19
19
> VMExtensionProvisioningError: VM has reported a failure when processing extension 'vmssCSE'.
20
20
>
21
-
> Error message: "Enable failed: failed to execute command: command terminated with exit status=124
21
+
> Error message: "Enable failed: failed to execute command: command terminated with exit status=65
22
22
23
23
## Cause
24
24
25
-
Under rare circumstances, the 124 exit code for the Azure Virtual Machine Scale Set custom script extension (`vmssCSE`) might happen instead of the following error codes:
25
+
Under rare circumstances, the 65 exit code for the Azure Virtual Machine Scale Set custom script extension (`vmssCSE`) might happen instead of the following error codes:
0 commit comments