Troubleshooting
The Container Keeps Restarting
voraus Robot UI checks its configuration and its connections at startup and exits when one of them
fails. Compose restarts it until the cause is fixed. The reason is in the last lines of
docker compose logs voraus-robot-ui:
- Robot Control is not available:
OPCUA_URLdoes not point to a running voraus Robot Control, orvoraus-coreis still starting. The reference file waits for voraus.core to be healthy before it starts voraus Robot UI. If you removed that dependency, add it back. - Error Handler is not available:
OPCUA_ERROR_URLdoes not point to a running Error Handler. To work without the Error Handler, setERROR_HANDLER_ENABLEDto"false". - voraus-parameter is not available:
PARAMETER_SERVER_URLis wrong, or thevoraus-parameterservice was removed without settingPARAMETER_SERVER_ENABLEDto"false", or its version differs from the one in the reference file. The UI only accepts the voraus-parameter version it was built against. - A variable is required: the message names it, see Configuration.
The Page Shows "No Connection"
The browser has lost the WebSocket to the voraus Robot UI container and retries every second until it is back.
- The container is restarting or has stopped. Check
docker compose ps. - The browser is offline.
- A reverse proxy in between does not forward WebSocket upgrades, see Behind a Reverse Proxy.
The 3D Visualization Panel Is Empty
The browser cannot load VORAUS_3D_VISU_BROWSER_URL. Open that URL in a new tab on the same
machine. It has to show voraus 3D Visualization on its own.
The Robot Is Shown, but No Arrows and No Pose Previews
voraus 3D Visualization ignores the messages of the browser because it does not trust the origin.
Add the address your browser shows for voraus Robot UI, scheme, host, and port but no path, to
V3DVISU_POST_MESSAGE_ALLOWED_ORIGINS on the voraus-3d-visu service, see the
voraus 3D Visualization configuration.
http://localhost:3001 on the Docker host is a different origin than http://192.168.1.20:3001
from another computer, and both need an entry if both are used. If VORAUS_3D_VISU_SYNC_ENABLED
is "false", this is expected: voraus Robot UI then sends nothing to voraus 3D Visualization.
The Robot Is Not Shown in voraus 3D Visualization
The server needs VORAUS_3D_VISU_SYNC_URL and the robot files from voraus.core or from a mounted
directory, see Robot Files. While it cannot load the robot, it
serves the UI without it, logs each new reason and retries every five seconds, so a voraus.core
that comes up later is picked up without a restart. Open browser tabs get the jogging arrows and
the pose previews within five seconds after that. The log line looks like this:
WARN 3D visualization sync waiting for the robot package, retrying every 5 s: robot package 'KUKA_KR_10_R900_2' not found in '/robots'; available: VORAUS_INDUSTRIAL_ROBOT
Run docker compose logs voraus-robot-ui to see it; RUST_LOG raises the detail, see
Logging.
With VORAUS_CORE_URL set, voraus 3D Visualization loads the robot model from voraus.core and
only from hosts listed in its V3DVISU_ALLOWED_HOSTS, see the
voraus 3D Visualization configuration.
Without VORAUS_CORE_URL, the folder name under ROBOTS_DIR must match the robot type voraus
Robot Control reports, and the GLB named in <ROBOT_TYPE>.robot.json must exist in the folder.
If the message says the robot type could not be read, your voraus Robot Control does not report
it in its RobotType node; update to voraus.core 2.30.0 or later, or set VORAUS_CORE_URL to
read the robot from voraus.core.