DEF-049 — Live Vehicle Tracking: socket.io server returns 503 — real-time tracking non-functional

Admin Panel
Critical severity
Functionality
New
Defect DEF-049 — Severity: Critical · Status: New
Published

2026-06-17

DEF-049 — Live Vehicle Tracking: socket.io server returns 503 — real-time tracking non-functional

Summary

The Live Vehicle Tracking page (/admin/vehicle-tracking) attempts to connect to a socket.io server for real-time vehicle location updates. The socket.io endpoint returns HTTP 503 Service Unavailable on every connection attempt, and the client continuously retries — generating 6+ error entries in the console within seconds of page load. Without a working socket.io connection, no live vehicle locations can be received or displayed, making the Live Vehicle Tracking feature entirely non-functional.

Environment

  • URL: https://project6.dxtserver.com/drivelink_new/public/admin/vehicle-tracking
  • Module: Admin Panel — Live Vehicle Tracking
  • Date Reported: 2026-06-17
  • Browser: Chromium (Playwright)
  • Testing Phase: Admin Panel — Section 18: Live Vehicle Tracking (test case LT-06)

Console Errors (at page load)

Failed to load resource: the server responded with a status of 503 (Service Unavailable)
  @ https://project6.dxtserver.com/socket.io/?EIO=4&transport=polling&t=PxNTbqh
Failed to load resource: the server responded with a status of 503 (Service Unavailable)
  @ https://project6.dxtserver.com/socket.io/?EIO=4&transport=polling&t=PxNTcI3
Failed to load resource: the server responded with a status of 503 (Service Unavailable)
  @ https://project6.dxtserver.com/socket.io/?EIO=4&transport=polling&t=PxNTcyp
Failed to load resource: the server responded with a status of 503 (Service Unavailable)
  @ https://project6.dxtserver.com/socket.io/?EIO=4&transport=polling&t=PxNTdsT
[...continues retrying]

The client-side socket.io library keeps retrying the connection, logging a new 503 error every ~1-2 seconds.

Steps to Reproduce

  1. Log in to the Admin Panel.
  2. Navigate to Live Tracking (/admin/vehicle-tracking).
  3. Open browser DevTools → Console.
  4. Observe: multiple 503 Service Unavailable errors for socket.io/?EIO=4&transport=polling appear immediately and continue every few seconds.

Expected Behaviour

  • The socket.io server should be running and accepting connections.
  • Once connected, vehicle locations should stream to the map in real time.
  • The Active Vehicles count should reflect currently active drivers.

Actual Behaviour

  • socket.io endpoint returns 503 Service Unavailable.
  • The client retries indefinitely, generating continuous errors.
  • Active Vehicles count shows 0 and “No active vehicles” regardless of real-world driver activity.
  • The map renders correctly but no live vehicle data is ever received.

Impact

  • The Live Vehicle Tracking feature is completely non-functional — its primary purpose (real-time location monitoring) cannot be achieved.
  • The 503 errors retry continuously, degrading browser performance for the duration the page is open.
  • Admins monitoring vehicle locations receive no real-time data.

Severity

Critical — Core feature of the Live Tracking page is entirely broken due to server infrastructure issue.

Priority

Critical

Status

New

Reported By

QA / Testing Team