VNC#
Using VNC#
VNC (Virtual Network Computing) is a remote desktop technology. It allows you to view the robot's computer screen and control it using a mouse and keyboard through a browser.
How it works#
User's browser
│ WebSocket (port 6080-6100)
▼
orchestrator-vnc-proxy (websockify)
│ TCP (VNC port, usually 5900)
▼
VNC server on the robot's computer
The user clicks a button → the Orchestrator creates a proxy connection via websockify → the browser connects to the robot's screen.
Setup#
1. Each robot must have a VNC server#
Install a VNC server on the robot's computer.
- Password and port configuration is done in the Assistant settings, on the "Execution/VNC Server" tab
Fields to fill in the Assistant:
- Robot VNC Port
- VNC Password
- Checkbox "Start VNC server when robot starts"
- Checkbox "Automatically start VNC server when Unattended robot starts"
Make sure the VNC server is running, its actual port is open in the firewall on the robot's computer, and the VNC password is set.
2. Fill in VNC data in the robot card#
In the Orchestrator, open the robot card (edit) and fill in the fields:
| Field | Description | Example |
|---|---|---|
| Machine IP | Robot computer address and VNC port. Specify the port explicitly to reach the intended server | 192.168.1.100:5900 |
| Machine Login | Login for VNC (if the VNC server requires it) | admin |
| Machine Password | Password for the VNC server on the robot (do not confuse with the Orchestrator password or Windows account password!) | vnc_pass_123 |
| VNC RA2 server key SHA-256 fingerprint | Trusted fingerprint of the VNC server's public key: 32 pairs of hexadecimal digits separated by colons | AA:BB:... (32 pairs) |
Where to get the password: The password is set when the VNC server is installed on the robot's computer. This is a separate VNC password, NOT the Windows user password and NOT the account password in the Orchestrator.
The VNC password must be at most 128 characters and 255 UTF-8 bytes, with no spaces or other whitespace characters.
Where to get the fingerprint: Copy it from the VNC settings of Sherpa RPA running under the same Windows account as ProcessAgent. Confirm it with the robot administrator through a trusted channel before saving the robot card. Update the stored fingerprint if the VNC server key changes.
3. User access permissions#
The user role must have VNC (access_vnc) permission with Read and Update rights:
- Go to the Roles section
- Select the required role
- Find the access_vnc field and check the Read and Update boxes
- Save
(If you do not have rights to edit roles, contact the administrator)
Using VNC#
Method 1: Connect to the robot from the table#
- Go to the Robots section
- In the row of the required robot, click the monitor icon (rightmost column)
- A new tab will open with the robot's screen
If the robot card has an address, password, and trusted server key fingerprint, connection starts automatically. If the fingerprint is missing, the form opens, but connection cannot proceed without it. The browser verifies the server key before sending credentials.
Method 2: Connect manually via VNC Viewer#
Open in browser:
https://YOUR_ORCHESTRATOR/main/vnc-viewerFill in the form:
Field What to enter VNC Server (host:port) Robot IP address and VNC port (e.g., 192.168.1.100:5900)Password VNC password Server key SHA-256 fingerprint Trusted fingerprint from the robot's VNC settings: 32 pairs of hexadecimal digits separated by colons Login (optional) Login, if required by the VNC server
If the fingerprint is missing, malformed, or does not match the server key, the connection is stopped. Do not bypass this check; confirm the correct fingerprint with the robot administrator.
Disconnecting#
- Click the red "Disconnect" button in the upper left corner
- Or simply close the browser tab
The proxy service will automatically stop and free the port.
VNC environment variables (.env)#
| Variable | Default | Description |
|---|---|---|
VNC_HOST |
orchestrator-vnc-proxy |
Address of the VNC proxy service |
VNC_PORT |
5000 |
VNC proxy API port |
VNC_LOG_LEVEL |
INFO |
Logging level |
VNC_START_PORT |
6080 |
Starting port for proxy connections |
VNC_MAX_PORTS |
100 |
Maximum number of simultaneous connections |
Port list#
| Port | Purpose |
|---|---|
| 5000 | VNC proxy API (internal, container-to-container) |
| 6080-6100 | WebSocket proxy for VNC sessions (browser → websockify) |
| 5900 | Standard VNC server port on the robot |
Possible issues#
| Problem | Cause | Solution |
|---|---|---|
| Monitor icon is gray | No access_vnc permission | Grant permissions in the Roles section |
| "VNC proxy API not found" | orchestrator-vnc-proxy not running | Check the status of the vnc container docker-compose ps |
| "VNC security error: incorrect password" | Wrong VNC password | Check the Machine Password field in the robot card |
| "A trusted VNC server fingerprint is required" | Fingerprint is missing | Add the trusted fingerprint to the robot card or connection form |
| "The VNC server identity does not match the trusted fingerprint" | The server key changed or another server was selected | Check the robot address and confirm the new fingerprint through a trusted channel before connecting |
| "VNC server not responding" | Robot is off or VNC is not running | Check the robot and the VNC server on it |
| Black screen after connecting | Robot screen is locked | Check whether the graphical session is active |