Skip to content

Commit 7b5e5d1

Browse files
committed
Learn Editor: Update troubleshoot-resource-bridge.md
1 parent 2ae623d commit 7b5e5d1

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

articles/azure-arc/resource-bridge/troubleshoot-resource-bridge.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -96,8 +96,14 @@ When trying to deploy Arc resource bridge, you might see an error that contains
9696

9797
If you receive an error that contains `Not able to connect to https://example.url.com`, check with your network administrator to ensure your network allows all of the required firewall and proxy URLs to deploy Arc resource bridge. For more information, see [Azure Arc resource bridge network requirements](network-requirements.md).
9898

99-
### .local not supported
99+
### Http2 server sent GOAWAY
100+
101+
When trying to deploy Arc resource bridge, you might receive an error message similar to:
100102

103+
`"errorResponse": "{\n\"message\": \"Post \\\"https://region.dp.kubernetesconfiguration.azure.com/azure-arc-appliance-k8sagents/GetLatestHelmPackagePath?api-version=2019-11-01-preview\\u0026releaseTrain=stable\\\": http2: server sent GOAWAY and closed the connection; LastStreamID=1, ErrCode=NO_ERROR, debug=\\\"\\\"\"\n}"`
104+
This occurs when there is a firewall or proxy with SSL/TLS inspection enabled blocking http2 calls from the machine used to deploy the resource bridge. Please work with your network administrator to disable the SSL/TLS inspection to allow http2 calls from the management machine.
105+
106+
### .local not supported
101107
When trying to set the configuration for Arc resource bridge, you might receive an error message similar to:
102108

103109
`"message": "Post \"https://esx.lab.local/52b-bcbc707ce02c/disk-0.vmdk\": dial tcp: lookup esx.lab.local: no such host"`

0 commit comments

Comments
 (0)