Socket

Fleetbase uses SocketCluster for real-time bidirectional communication — live driver location updates on the map, order status changes pushed to the console without polling, and real-time events delivered to the Navigator app. Navigate to Admin → System Settings → Socket to monitor the connection.

Connection Monitor

The Socket page displays a live event log from the SocketCluster server. Events appear as they are received, with timestamps and color-coded output. This view is read-only — SocketCluster configuration is managed at the infrastructure level and cannot be changed from this page.

Configuration

SocketCluster is configured via environment variables set in docker-compose.override.yml under the socket service:

services:
  socket:
    environment:
      SOCKETCLUSTER_OPTIONS: '{"origins":"https://console.yourdomain.com"}'

The origins value is a comma-separated list of allowed WebSocket origins. In production, restrict this to your exact console domain to prevent connections from unauthorized origins.

The API container connects to SocketCluster using these variables (set under the application service):

Testing

Click Test Socket Connection to publish a test message through SocketCluster from the API container. A success response confirms the API can reach the SocketCluster server and publish events. If the test fails, check that:

• The socket container is running (docker compose ps socket)
• SOCKETCLUSTER_HOST and SOCKETCLUSTER_PORT in the application container match the socket container's actual hostname and port
• No internal firewall rule is blocking container-to-container traffic on port 38000

Troubleshooting

WebSocket connections refused in the browser The origins list in SOCKETCLUSTER_OPTIONS must exactly match the Origin header sent by the browser, including the protocol — https://console.yourdomain.com, not just yourdomain.com. A mismatch causes the SocketCluster server to reject the upgrade request.

Events not appearing in real time If the event log is empty but the connection test passes, the issue is likely an origins mismatch on the browser side. Check the browser console for WebSocket errors and compare the reported origin against your SOCKETCLUSTER_OPTIONS value.