Windows agent startup throws Unexpected HTTP response status code 200
search cancel

Windows agent startup throws Unexpected HTTP response status code 200

book

Article ID: 393647

calendar_today

Updated On:

Products

Automic SaaS

Issue/Introduction

When attempting to start a Windows agent to point to SaaS Automic system, the agent will not start.  The agent log show something like:

U02000379 Initiating connection to server 'saasurl.example.com:443' using WebSocket URI: 'wss://saasurl.example.com:443/agent'.
U02000438 Number of trusted certificates loaded from 'Windows Certificate Store': '##'.
U02000484 This agent trusts '##' certificates when creating a JCP connection.
U02000313 Communication error with partner 'saasurl.example.com:443', error: 'Unexpected HTTP response status code 200'.
U02000074 Connecting to system 'AUTOMIC' is not possible.
          Initial connection with endpoint not possible. Please check your configuration.

Turning on a tcp/ip=9 trace shows the following:

1      U02000438 Number of trusted certificates loaded from 'Windows Certificate Store': '##'.
1                adding ### certificates from the default trust manager
1      U02000484 This agent trusts '###' certificates when creating a JCP connection.
1      U02000313 Communication error with partner 'saasurl.example.com:443', error: 'Unexpected HTTP response status code 200'.
1      U00045014 Exception 'java.util.concurrent.ExecutionException: "java.net.http.WebSocketHandshakeException"' at 'java.util.concurrent.CompletableFuture.reportGet()'.
1      U00045015 The previous error was caused by 'java.net.http.WebSocketHandshakeException: "null"' at 'jdk.internal.net.http.websocket.OpeningHandshake.resultFrom()'.
1      U00045015 The previous error was caused by 'jdk.internal.net.http.websocket.CheckFailedException: "Unexpected HTTP response status code 200"' at 'jdk.internal.net.http.websocket.OpeningHandshake.checkFailed()'.
1      U02000074 Connecting to system 'AUTOMIC' is not possible.
1                Initial connection with endpoint not possible. Please check your configuration.
1                Change state from CONNECTING to FINISHED

Environment

Automic SaaS
Windows agent

Resolution

The network team should run a trace on the outgoing traffic from the agent server.  They can then see if there is a problem with the traffic getting out or coming back from the Automic SaaS server.

If there is a bypass the IPS system, this should be checked to be sure that all SaaS Domains are allowed.