Remote Technician gives you access to a device's embedded web server from anywhere, without a VPN and without direct network access to the customer's site. From there you can do anything the device's own web page allows: restart it, upgrade firmware, view the front panel, change settings.
It requires no special network or firewall configuration and works out of the box.
Remote Technician only exposes the device's own embedded web server. If an operation cannot be performed from the device's web page, it cannot be performed through Remote Technician, and not every device supports every operation.
Opening a Session
Using the sidebar, click Devices, then View devices.
Find the device you want to access.
Click the Remote Technician tab.
Click Open Device Webpage.
A new browser tab opens. It can take a few seconds to connect.
Each session lasts a maximum of 30 minutes. After that you need to start a new one from the UI.
Remote Technician cannot connect if the device is turned off, the device is not on the local network, or the data collection agent is not on the same network as the device. That last one catches people out when the agent is installed on a laptop that has gone home for the night.
Permissions
Two roles control Remote Technician:
Remote Technician Configurer. Can enable or disable Remote Technician for the devices they manage.
Remote Technician User. Can use Remote Technician on devices where it is enabled.
Once a user holds the Configurer role, an enable and disable setting appears on each device.
Restricting Access
For sensitive customers you can restrict Remote Technician by user, by entity, or by install.
Restricting by entity or install overrides the user role. A user who holds the Remote Technician User role still cannot reach a device that has been restricted at the entity or install level.
By user
This stops one person using Remote Technician anywhere, without affecting anyone else. It is the simplest option when the concern is a particular user rather than a particular customer.
Using the sidebar, click Admin, then Manage users.
Find the user and click the pencil icon to edit them.
Click the Permissions tab.
Deselect the Remote Technician User role.
By entity
This blocks every device beneath the entity. This is the recommended way to restrict a whole customer site.
Select the entity you want to restrict.
Using the sidebar, click Admin, then Manage entity.
Click the Settings tab.
Expand the Remote Technician section.
Click the Enabled toggle to disable it.
By install
This blocks every device managed by that install. Entity-level is usually the better choice, but install-level is useful for a specific machine with its own antivirus or network policy constraints.
Using the sidebar, click Installs, then View installs.
Click the install you want to restrict.
Click the Settings tab.
Expand the Remote Technician section.
Click the Enabled toggle to disable it.
If more than one install tracks the same device, disabling Remote Technician on only one of them does not block access. The device stays reachable through any install where it is still enabled. Clustered sites are the common case, so restrict at the entity level instead.
Network Requirements
Remote Technician is outbound only. It needs no inbound firewall rule, no NAT rule, and no port forwarding.
The agent opens a tunnel itself, on demand, only when a session is requested. Transport is HTTPS and secure WebSocket, using an HTTP/1.1 upgrade, over TCP 443. Technicians then reach each device through its own HTTPS subdomain.
Host | Protocol | Port |
| HTTPS / secure WebSocket (HTTP/1.1 upgrade) | 443 |
Two things trip up otherwise-correct allowlists:
Add the nested wildcard explicitly. Some firewall and proxy products do not treat
*.printtrackerpro.comas matching a nested subdomain such asdevice.remotetechnician.printtrackerpro.com. It needs its own entry.WebSocket upgrades must survive the proxy. Outbound TLS on 443 has to permit HTTP
Upgradeheaders and long-lived connections. A proxy that strips the Upgrade header, or kills long connections, breaks Remote Technician while everything else keeps working. That combination is a common and confusing failure.
See DCA Offline or Checking In Late for the full list of hosts the agent needs.
How a Session Is Secured
When an authorized user starts a session:
Web Admin signals the install over gRPC.
The install checks whether remote remediation has been disabled, and returns an error if it has.
The install verifies the MAC address or serial number of the device.
The install opens a persistent outbound TLS connection to the Remote Technician server.
The user's browser completes an OAuth 2.1 PKCE token exchange with that server.
The browser is redirected over HTTPS to the Remote Technician server.
Traffic passes end to end over TLS between the device and the browser.
Note that the signal from Web Admin to the install uses gRPC, while the session tunnel itself is the outbound TLS and WebSocket connection described above. They are different connections.
Restricted cross-origin resource sharing and a strict Content Security Policy are applied to Remote Technician traffic. Together these sharply limit lateral movement a malicious device might attempt, and eliminate cross-site request forgery.
Auditing Sessions
Every session is recorded as an Open Device Webpage job. Open any job of that type in the Jobs tab and you will find a Remote Technician Log at the bottom containing the complete HTTP access logs for that session.
This is what to reach for when a customer asks who accessed a device and what they did.
Device Compatibility
Remote Technician works with nearly all devices regardless of manufacturer, but some devices have web servers that do not follow standard web protocols, and those can misbehave. For the known cases and their workarounds, see Remote Technician Troubleshooting.
Related Articles
Remote Technician Troubleshooting
DCA Offline or Checking In Late
Settings Inheritance: How Entity and Device Settings Work