Auvik's Remote Browser feature allows you to securely access the web interface of supported network devices through the Auvik collector without requiring direct network access from your workstation.
You can use Remote Browser to access web-enabled devices such as:
- Routers
- Switches
- Firewalls
- Wireless controllers
- Access points
- NAS devices
- Other devices with HTTP or HTTPS management interfaces
Before you begin
Ensure the following requirements are met:
- Pop-up blockers are disabled or configured to allow pop-ups from Auvik.
- The device's web interface is enabled.
- The Auvik collector can reach the device on the management port.
- The management port is configured in Auvik's HTTP or HTTPS service.
- Firewalls or ACLs allow communication between the collector and the device.
Note: Remote Browser uses the assigned collector to establish the connection. If the collector cannot reach the device, Remote Browser will not be available.
Launch a Remote Browser Session
- Navigate to the device dashboard.
- Hover over Remote Management.
- Click Remote Browser.
- Select the HTTP or HTTPS port you want to connect to.
- Click Start.
A new browser window opens, allowing you to interact with the device's web interface as though you were connected directly to the network.
Available Ports
The Remote Browser port list is populated from ports configured under Auvik's HTTP and HTTPS services.
If the port you want to use isn't listed:
- Navigate to Inventory > Services.
- Open the HTTP or HTTPS service.
- Add the required management port to the service configuration.
- Allow time for the collector to validate connectivity to the port.
- Return to Remote Browser and try again.
Note: If multiple services are configured to monitor the same port, duplicate entries may appear in the port selection list.
Troubleshooting Missing Ports
If the device's management port is configured in Auvik but does not appear in the Remote Browser port list, the collector may be unable to reach the service.
To verify connectivity:
- Navigate to Inventory > Services.
- Open the HTTP or HTTPS service used by the device.
- Locate the device in the service inventory.
- Review the Last Status Code column.
Common status codes
| Status Code | Meaning |
|---|---|
| 200 OK | The collector successfully reached the web service. |
| 301/302 Redirect | The service is responding but redirecting requests. |
| 401 Unauthorized | The service is reachable but requires authentication. |
| 403 Forbidden | The service is reachable but access is denied. |
| Timeout / No Response | The collector cannot reach the service. |
If the status is anything other than a successful response, verify:
- The web interface is enabled on the device.
- The configured port is correct.
- The collector can route to the device.
- Firewall rules allow HTTP or HTTPS traffic between the collector and the device.
- Any source IP restrictions on the device permit connections from the collector.
- SSL/TLS settings on the device are supported by the device's web server.
Troubleshooting Remote Browser Connections
If Remote Browser fails to launch or connect:
Verify pop-up permissions
Remote Browser opens in a separate browser window. Ensure your browser is not blocking pop-ups from Auvik.
Verify collector connectivity
The collector must be able to establish a direct connection to the device's web service. Test connectivity by reviewing the device's HTTP or HTTPS service status in Auvik.
Verify the correct management port
Many devices use non-standard management ports instead of:
- HTTP: 80
- HTTPS: 443
Confirm the device's management port matches the port configured in Auvik.
Verify source IP restrictions
Some devices limit management access to approved IP addresses or subnets. Ensure the collector's IP address is included in any management access control lists.
Limitations
Some legacy web interfaces use absolute URLs rather than relative URLs when generating page content.
In these cases, portions of the interface may not load correctly when accessed through Remote Browser unless the device is reachable from your local network.
This behavior is determined by the device's web application and cannot be corrected within Auvik.
Security Considerations
Remote Browser provides access through the Auvik collector and does not bypass device authentication. Users must still authenticate using valid credentials configured on the target device.
For security best practices:
- Restrict management interfaces to trusted networks.
- Use HTTPS whenever available.
- Limit administrative access using role-based accounts.
- Restrict management access through firewall rules and ACLs where appropriate.