1. Automox
  2. Configuring Automox
  3. Agent Installation & Setup

Automox Agent Self-Test Fails During Installation

Avatar
Brendan
Updated:

Issue

During agent installation, the post-install self-test fails with the following message:

Initiating agent self test...
- 'C:\Program Files (x86)\Automox\amagent.exe selftest' failed.
{"summary":"Self Test Failed (2/3) - 2.3.34","results":[
{"test_name":"inventory module test","test_status":"Succeeded","test_execution_time":"0s"},
{"test_name":"RTT connection test","test_status":"Failed",
"test_error_message":"failed to reach server: Get \"https://rtt.automox.com/.well-known/jwks.json\": 
context deadline exceeded (Client.Timeout exceeded while awaiting headers)","test_execution_time":"10.0106929s"},
{"test_name":"Kiosk connection test","test_status":"Failed",
"test_error_message":"Get \"https://api.automox.com/v1/live\": 
read tcp 10.194.4.237:61392->003e166.117.254.71:443: wsarecv: 
A connection attempt failed because the connected party 
did not properly respond after a period of time, or established 
connection failed because connected host has failed to respond.",
"test_execution_time":"1m26.8961258s"}],"passed":false}
Error: exit 4

This indicates that the agent cannot reach the Automox RTT or API endpoints during the installation self-test. Often you will encounter one or the other.

Environment

  • Operating System: Windows Desktop and Server

  • Automox Agent Version: 2.3.34 or later

  • Network Requirements: Outbound HTTPS (TCP 443) access to Automox domains

Cause

The agent self-test fails when outbound network access to Automox cloud services is blocked or intercepted by a firewall, proxy, or security inspection device.
Affected endpoints include:

  • https://rtt.automox.com

  • https://api.automox.com

Resolution

Step 1: Test Connectivity to Automox Endpoints

Run the following commands to verify connectivity. Successful output should return HTTP/2 200 and a valid JSON response.

Option 1: Using PowerShell or Command Prompt (with curl installed)

curl -vk https://rtt.automox.com/.well-known/jwks.json
curl -vk https://api.automox.com/v1/live

Expected Output Example

* Host rtt.automox.com:443 was resolved.
* IPv6: (none)
* IPv4: 166.117.254.67, 166.117.56.92
*   Trying 166.117.254.67:443...
* Connected to rtt.automox.com (166.117.254.67) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
* (304) (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Change cipher spec (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=rtt.automox.com
*  start date: Sep 23 12:20:20 2025 GMT
*  expire date: Dec 22 12:20:19 2025 GMT
*  issuer: C=US; O=Let's Encrypt; CN=R12
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://rtt.automox.com/.well-known/jwks.json
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: rtt.automox.com]
* [HTTP/2] [1] [:path: /.well-known/jwks.json]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET /.well-known/jwks.json HTTP/2
> Host: rtt.automox.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/2 200
< content-type: application/json
< vary: Origin
< date: Tue, 28 Oct 2025 13:11:46 GMT
< content-length: 421
< x-envoy-upstream-service-time: 0
< server: istio-envoy
<
{"keys":[{"alg":"RS256","e":"AQAB","kid":"1","kty":"RSA","n":"u4R9YNAYweGm5RGyvrNC3ZpR1HN0EOKIgR05idwnExeUp1aqnSZ9YLy2Pg1AptsvB9_zxziRJYr7r_wYbra6Kvvef5EB1EWheGb2hyDOnyKHfW6QrUQXoQnurHWzGbqheQG4ow0Q9l3f1JnPPCsCloSnP3Qy2MqqYE28IUF7p5lLESXX37ttPHN1i-lPSB9gmfnD599RHPPchrX0T0CxmYc17Z4SsSQLROt0V0kvgxokPGtIDVYg-d4uV3YX_50uv4f88_kK95Nit0vOYoF7EmYRNL0DpgihBORF59bEatKxeIllbsa7QeNj3oEDbvf2b5DVIm6v02MX6AiGH-I_Kw","use":"sig"}]}
* Connection #0 to host rtt.automox.com left intact

If the connection fails or times out, confirm that outbound HTTPS (TCP 443) traffic to these domains is allowed.

Option 2: Using a browser, navigate directly to the target URL

Open a browser of your choice, and enter the URL into the address bar. On success, you will see a form of the following response per URL:

https://rtt.automox.com/.well-known/jwks.json

https://api.automox.com/v1/live

Step 2: Verify Network Configuration

Ensure that the following are not blocking traffic:

If your organization uses a proxy, confirm it is configured in the Automox Agent settings or system environment variables.

Step 3: Retry Agent Installation

After confirming connectivity, re-run the Automox Agent installer. The post-install self-test should now pass successfully.

Additional Notes

If the issue persists:

  • Verify DNS resolution for rtt.automox.com and api.automox.com returns valid IPs.

  • Contact your network administrator to ensure these endpoints are not restricted.

  • Review the Automox Agent Installation Log located in: C:\Windows\Temp\

Articles in this section

See more
Was this article helpful?
0 out of 1 found this helpful