Local application endpoints
Local service ports, middleware API documentation and URL examples from the updated network map.
Select the service host
Use the IP of the device running the required application. Replace <IP> in the examples below with that device's recorded address. The network map lists the middleware server at 192.168.100.50 and lane middleware at 192.168.100.101–109; select the instance serving the relevant lane or device.
Connect to the host running the required service. Use Chrome or Chromium for browser interfaces, following the tablet setup guide.
Application and service ports
| Application / service | Port | URL pattern |
|---|---|---|
| Middleware API v1 documentation | 5000 | http://<IP>:5000/swagger |
| Middleware API v2 documentation | 5000 | http://<IP>:5000/api/v2/docs |
| UIRM web interface | 5173 | http://<IP>:5173 |
| Local Kiosk | 5174 | http://<IP>:5174 |
| Local Tunnel | 5175 | http://<IP>:5175 |
| Lane Assist WebSocket server | 5176 | ws://<IP>:5176 |
| Lane Assist | 5182 | http://<IP>:5182 |
| Lane Customer Display | 5183 | http://<IP>:5183 |
| Tunnel Welcome Display | 5184 | http://<IP>:5184 |
For example, if the middleware API runs at the map's planned server address, its v2 documentation URL is http://192.168.100.50:5000/api/v2/docs. Both API documentation versions use port 5000; their paths differ.
Port 5176 is the WebSocket service used by Lane Assist. Its ws:// address is a connection endpoint for the application, rather than a normal browser page.
HTTPS and tablet setup
Where the middleware certificate helper is installed, the middleware installer reference documents HTTPS 5443 → local middleware 5000, plus HTTP port 80 for the public CA certificate. Continue to use the tablet certificate setup for those installations.
Network access reference
These are local service endpoints. See the firewall service table for network access planning.