Troubleshooting Remote Browser (HTTPS) Connectivity Issues

Overview

Auvik’s Remote Browser feature depends on successful HTTPS connectivity between the collector and the target device. When Remote Browser fails, the issue is typically related to connectivity, TLS negotiation, certificate validation, or device configuration.

This article outlines how to validate HTTPS connectivity directly from the Auvik collector.

Symptoms

• Remote Browser fails to open for specific devices
• HTTPS connection times out or is refused
• Page fails to load after connection
• Works for some devices but not others

Step 1: Test HTTPS Connectivity from the Collector

Run the following command from the Auvik collector:

curl -v https://<deviceIP>/

If Certificate Errors Occur

If you see certificate validation errors, retry using:

curl -vk https://<deviceIP>/

This ignores certificate validation and helps determine whether the issue is related to trust versus connectivity.

If Using a Non-Standard HTTPS Port

Adjust the command to include the port:

curl -vk https://<deviceIP>:<port>/

Optional: Test Using Hostname (If Applicable)

If the device is typically accessed via hostname, test using the hostname instead of the IP address:

curl -v https://<hostname>/

This helps validate DNS resolution and Server Name Indication (SNI) behavior.

What to Validate

• DNS resolution: Errors such as Could not resolve host indicate DNS issues
• Connection establishment: Confirms basic network reachability
• TLS handshake: May reveal unsupported TLS versions, cipher mismatches, or HTTPS misconfiguration
• Certificate output: Identifies trust, expiration, or hostname mismatch issues

Common Outcomes

• Connection timeout/refused → Likely firewall, routing, or port issue
• TLS handshake failure → May indicate TLS version/cipher mismatch or device HTTPS misconfiguration
• Certificate warnings/errors → Self-signed, expired, or mismatched certificate

Common Root Causes

• TCP/443 (or custom HTTPS port) blocked between collector and device
• HTTPS service disabled or misconfigured on the device
• TLS version or cipher incompatibility
• Invalid or untrusted SSL certificate
• DNS resolution issues (for hostname-based access)

Best Practices

• Use consistent HTTPS ports across devices
• Deploy valid certificates where possible
• Ensure collector DNS resolution is reliable
• Test connectivity directly from the collector during troubleshooting

Summary

HTTPS failures impacting Remote Browser are best diagnosed using curl from the collector. The verbose output provides visibility into DNS resolution, TCP connectivity, TLS negotiation, and certificate behavior, allowing rapid identification of the root cause.