Network Configuration#

To connect Sherpa Attended Robot, Sherpa Unattended Robot, and Sherpa Coordinator to Sherpa Orchestrator, outbound connections from client machines to the Orchestrator need to be allowed: HTTPS 443 or HTTP 80 if explicitly enabled. Web interface users need access to the same address.

The Orchestrator needs access to the selected database: MariaDB/MySQL on port 3306 or PostgreSQL on port 5432. These ports can be changed in the database and connection settings. Port 1433 is not used by the Orchestrator's supported databases. For automatic license activation, also allow outbound HTTPS on port 443 to api.licenses.sherparpa.ru. Use offline activation for an isolated network.

Robots and Coordinator normally initiate API requests to the Orchestrator. When VNC screen viewing is used, orchestrator-vnc-proxy initiates a separate TCP connection to the VNC server on the Robot machine. Open the Robot's actual VNC port (often 5900) for the proxy. This access is not needed without VNC.

For HTTPS in the Docker distribution, place orchestrator.crt and orchestrator.key in ./nginx/config/certs/ under the installation directory. This directory is mounted in the nginx container as /etc/nginx/certs/. Sherpa Orchestrator accepts TLS 1.2 and TLS 1.3.