Network Connectivity Test network-connectivity-test

The Network Connectivity Test is a Cloud Manager diagnostic tool that lets you validate Advanced Networking and VPN configuration before you enable Advanced Networking on your environments and before you go live. Use it to verify that the hosts and ports AEM must reach, including internal or private endpoints, are reachable over the same connectivity path Advanced Networking will use.

The test runs from the egress proxy infrastructure that belongs to your program’s Advanced Networking setup, not from an Author or Publish pod. It uses the same outbound network path AEM uses when Advanced Networking is active. That design is especially useful for VPN scenarios: you can confirm DNS resolution, network routing, firewall rules, and service availability for private or on-premises systems before you go live.

For background on provisioning VPN, dedicated egress IP, or flexible port egress, see Configuring Advanced Networking for AEM as a Cloud Service.

When to Use This Tool when-to-use

Prerequisites prerequisites

How to Run a Test how-to-run-a-test

Input Fields input-fields

Steps test-steps

Understanding Results understanding-results

The tool reports several dimensions. Together they describe whether the target is reachable from Advanced Networking and how HTTP-aware checks behaved.

DNS Resolution dns-resolution

Port Open port-open

HTTP Connectivity http-connectivity

An HTTP/HTTPS request is attempted on every port. The tool always tries HTTPS first, then falls back to HTTP. If neither works, the result is mapped to a short, readable error message (see the table below).

Success Outputs

Classified Error Outputs

Reachability reachability

Multiple DNS Resolvers multiple-dns-resolvers

If your Advanced Networking infrastructure defines more than one DNS resolver:

Troubleshooting troubleshooting

The following scenarios pair what you are likely to see in the tool with steps to narrow down the cause. For full Copy to clipboard JSON that illustrates the same situations, see Example Outputs.

DNS Resolution Failed dns-failed

Output

The hostname did not resolve using your Advanced Networking DNS settings, so the tool cannot test the port. In the results view, DNS resolution shows an error string, and Reachability reports that DNS failed:

DNS Resolution: error: "DNS resolution error: ..."
Reachability: "Unreachable: DNS resolution failed"

Recommendations

DNS Works but the Port Is Not Accessible dns-ok-port-blocked

Output

The tool can resolve the host, but TCP to the port does not succeed. A summary often looks like this:

DNS Resolution: ips: ["10.0.1.50"]
Port Open: No
Reachability: "Unreachable: Port not accessible"

Recommendations

Test Shows Reachable but AEM Does Not Connect reachable-but-aem-fails

Output

The connectivity check itself succeeds. A condensed summary often looks like this:

Port Open: Yes
Reachability: "Reachable"

That outcome means the path from Advanced Networking to the host and port you tested is open. It does not guarantee that AEM application traffic is using that path: when your code runs, service logs may still show no requests from the egress IP you expect.

Recommendations

HTTP Shows an Error but Port Is Open http-error-port-open

Output

TCP succeeds, but the HTTP/HTTPS probe still reports a failure. A summary often looks like this:

Port Open: Yes
HTTP Connectivity: error: "Connection error: ..." or "Both HTTPS and HTTP failed. ..."
Reachability: "Reachable"

Recommendations

Request Timeout timeout

Output

{ "error": "Request timeout" }

Recommendations

Example Outputs example-outputs

Successful HTTPS Test (e.g., Internal API on Port 443) example-output-successful-https

{
  "resolvers": [
    {
      "name": "default",
      "dns_resolution": {
        "ips": ["10.0.1.50"]
      },
      "port_open": true,
      "http_connectivity": {
        "protocol": "https",
        "status_code": 200,
        "reason": "200 OK"
      },
      "reachability": "Reachable"
    }
  ]
}

Successful Non-HTTP Service Test (e.g., Database on Port 5432) example-output-successful-non-http

{
  "resolvers": [
    {
      "name": "default",
      "dns_resolution": {
        "ips": ["10.0.1.50"]
      },
      "port_open": true,
      "http_connectivity": {
        "error": "Not an HTTP/HTTPS service",
        "note": "The service appears to be a non-HTTP service (e.g., database, message queue, or custom TCP). Use the port_open and reachability fields to verify connectivity."
      },
      "reachability": "Reachable"
    }
  ]
}

DNS Resolution Failure example-output-dns-resolution-failure

{
  "resolvers": [
    {
      "name": "default",
      "dns_resolution": {
        "error": "DNS resolution error: dial udp 10.0.0.2:53: i/o timeout"
      },
      "port_open": false,
      "http_connectivity": {
        "error": "DNS resolution failed"
      },
      "reachability": "Unreachable: DNS resolution failed"
    }
  ]
}

Port Not Accessible (Firewall / Service Down) example-output-port-not-accessible

{
  "resolvers": [
    {
      "name": "default",
      "dns_resolution": {
        "ips": ["10.0.1.50"]
      },
      "port_open": false,
      "http_connectivity": {
        "error": "Connection error: dial tcp 10.0.1.50:443: i/o timeout"
      },
      "reachability": "Unreachable: Port not accessible"
    }
  ]
}

Important Notes important-notes

What This Test Does Not Do what-this-test-does-not-do

Response Time response-time

HTTP vs Non-HTTP Services http-vs-non-http-services

The tool attempts an HTTP/HTTPS connection on every port. For non-HTTP services (for example, PostgreSQL on port 5432, MySQL on 3306, SFTP on 22, Redis on 6379), the HTTP check can fail with a connection error—this is expected. Rely on Port open and Reachability to confirm connectivity for those services.

Related Information related-information