Skip to content

Commit b89b24f

Browse files
committed
Move section
1 parent fd59b88 commit b89b24f

File tree

1 file changed

+27
-27
lines changed

1 file changed

+27
-27
lines changed

AKS-Arc/network-validation-errors.md

Lines changed: 27 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@ description: Learn how to troubleshoot general network validation errors in AKS
44
author: sethmanheim
55
ms.author: sethm
66
ms.topic: troubleshooting
7-
ms.date: 07/16/2025
7+
ms.date: 07/17/2025
88
ms.reviewer: srikantsarwa
99
ms.lastreviewed: 07/16/2025
1010

@@ -60,6 +60,32 @@ This error indicates that the required URLs are not reachable from the AKS clust
6060

6161
To resolve this error, ensure that the logical network IP addresses have outbound internet access. If there's a firewall, ensure that the [AKS required URLs](aks-hci-network-system-requirements.md#firewall-url-exceptions) are accessible from the Arc VM logical network.
6262

63+
## InternetConnectivityError (in Arc Gateway scenario)
64+
65+
Error: Network validation failed during cluster creation.
66+
67+
### Description
68+
69+
Detailed message: `Not able to connect to https://mcr.microsoft.com. Error returned: action failed after 5 attempts: Get "https://mcr.microsoft.com": proxyconnect tcp: dial tcp 192.168.2.100:40343: connect: connection refused`.
70+
71+
### Causes of failure
72+
73+
- The control plane VM can't reach the Azure Local cluster IP on port **40343**, which is required when Arc Gateway is enabled.
74+
- The firewall or network security rules block traffic between the AKS subnet and the cluster IP.
75+
- Proxy settings are incorrect, or the proxy does not allow connections to `mcr.microsoft.com`.
76+
77+
### Mitigation
78+
79+
To resolve this error, you can take the following steps:
80+
81+
- Ensure that the **AKS subnet has connectivity to the Azure Local Cluster IP on port `40343`**.
82+
- Verify that the Arc Gateway service on the Azure Local Cluster is running and listening on port `40343`.
83+
- Check firewall or NSG rules to ensure that traffic between the AKS VMs and the Cluster IP on `40343` is allowed.
84+
- Confirm that proxy settings (if used) are correct and that the proxy can forward requests to `https://mcr.microsoft.com`.
85+
- Test connectivity to `https://mcr.microsoft.com` from the control plane VM, either directly or via the configured proxy.
86+
87+
For more information, see [Use Azure Arc Gateway with Azure Local](aks-hci-network-system-requirements.md#use-azure-arc-gateway-preview-with-azure-local).
88+
6389
## VMNotReachableError
6490

6591
Error: Network validation failed during cluster creation.
@@ -93,32 +119,6 @@ DNS servers specified in a logical network can't resolve the MOC cloud FQDN or t
93119

94120
To resolve this error, check the DNS servers specified in the logical network so that they can resolve the MOC cloud FQDN or the required URLs.
95121

96-
## InternetConnectivityError (in Arc Gateway scenario)
97-
98-
Error: Network validation failed during cluster creation.
99-
100-
### Description
101-
102-
Detailed message: `Not able to connect to https://mcr.microsoft.com. Error returned: action failed after 5 attempts: Get "https://mcr.microsoft.com": proxyconnect tcp: dial tcp 192.168.2.100:40343: connect: connection refused`.
103-
104-
### Causes of failure
105-
106-
- The control plane VM can't reach the Azure Local cluster IP on port **40343**, which is required when Arc Gateway is enabled.
107-
- The firewall or network security rules block traffic between the AKS subnet and the cluster IP.
108-
- Proxy settings are incorrect, or the proxy does not allow connections to `mcr.microsoft.com`.
109-
110-
### Mitigation
111-
112-
To resolve this error, you can take the following steps:
113-
114-
- Ensure that the **AKS subnet has connectivity to the Azure Local Cluster IP on port `40343`**.
115-
- Verify that the Arc Gateway service on the Azure Local Cluster is running and listening on port `40343`.
116-
- Check firewall or NSG rules to ensure that traffic between the AKS VMs and the Cluster IP on `40343` is allowed.
117-
- Confirm that proxy settings (if used) are correct and that the proxy can forward requests to `https://mcr.microsoft.com`.
118-
- Test connectivity to `https://mcr.microsoft.com` from the control plane VM, either directly or via the configured proxy.
119-
120-
For more information, see [Use Azure Arc Gateway with Azure Local](aks-hci-network-system-requirements.md#use-azure-arc-gateway-preview-with-azure-local).
121-
122122
## Contact Microsoft Support
123123

124124
If problems persist, [collect AKS cluster logs](get-on-demand-logs.md) before you [create a support request](aks-troubleshoot.md#open-a-support-request).

0 commit comments

Comments
 (0)