Discover MoveIt Pro Deployments on a Network
MoveIt Pro's discovery server lists the default deployment and named instances on a computer. Use the reported web UI port to open the frontend served by that deployment. The browser frontend remains paired with the backend that served the page and does not support retargeting from within the web interface.
How discovery works
Every computer that runs moveit_pro run starts a small instance discovery server on port 3205. It answers GET http://<host>:3205/instances with the default deployment and every recorded named instance. Each entry includes its name, web UI and backend ports, and running state.
Query a host directly to inspect its deployments:
curl http://<host>:3205/instances
Manage the server explicitly when needed:
moveit_pro discovery status
moveit_pro discovery up
moveit_pro discovery down
Pass --no-discovery to moveit_pro run to skip starting it.
The discovery response is unauthenticated and reveals deployment names, ports, and running state. Expose port 3205 only on trusted networks. On firewalld-based systems (Fedora, RHEL), allow discovery with:
sudo firewall-cmd --add-port=3205/tcp
Do not expose a plaintext web UI port directly on an untrusted network. Use an SSH tunnel or trusted HTTPS ingress as described in Remotely Connecting to the Web Interface.
Opening a deployment's web interface
For named instances on the local computer, list the recorded frontend URLs:
moveit_pro run --list-instances
Open the URL reported for the running instance. The default deployment uses http://localhost.
For a deployment on another computer, read its ui_port from the discovery response and tunnel that port over SSH. This example maps the remote UI port to local port 8080:
ssh -L 8080:localhost:<ui-port> <user>@<host>
Keep the SSH session open and browse to http://localhost:8080. To operate a different deployment, open that deployment's own frontend URL or create a tunnel to its UI port.