Monitor the Open VTS server’s CPU, memory, disk usage, uptime, local service manager, and the health of essential platform services.
Last updated August 18, 2026
The Server page provides a central health overview of the Windows server running Open VTS.
It helps the Superadmin verify:
This page is primarily designed for monitoring server health. It does not replace operating-system-level administration, database management, log analysis, or infrastructure monitoring tools.

The top section provides a quick summary of when the server was last checked.
It contains:
The local service-manager agent helps Open VTS perform approved service actions on the server.
Its status can appear as:
When the agent is offline, server metrics and service health may still be visible, but some service actions can become unavailable.
In particular, restarting the Backend requires the local agent to be online.
Select Refresh to request the latest:
The Last check value updates after the latest health request completes.
The Server page includes a safety warning because stopping essential Open VTS services can make the application unavailable.
The interface allows limited Start, Restart, and Reload actions, but the Stop action is intentionally disabled.
This protects the Superadmin from accidentally stopping:
Stopping these services could prevent users from accessing Open VTS or receiving vehicle data.
The four summary cards show the current condition of the server.
Shows the percentage of processor capacity currently being used.
The supporting information can include:
A short temporary increase can be normal during:
Sustained high CPU usage should be investigated.
Shows:
Memory usage can increase as the number of connected vehicles, users, cached records, and background operations grows.
Consistently high memory usage may indicate that the server requires:
Shows the usage of the server’s primary storage drive.
The card displays:
Disk space is especially important because Open VTS stores telemetry, logs, database records, exports, and application files.
Storage usage depends heavily on:
Do not allow the server drive to become completely full. Low disk space can affect database writes, telemetry storage, updates, and overall platform stability.
Shows how long the Windows server has been running since its most recent restart.
A long uptime does not automatically mean that every Open VTS service has been running for the same duration. Each service card displays its own process uptime separately.
The Services section monitors the essential components required by Open VTS.
The monitored services are:
Each service card can show:
The required process, port, and health check were detected successfully.
A Running state indicates that the service appears operational at the time of the latest check.
The expected process or listening port was not detected.
A stopped essential service can affect one or more Open VTS functions.
The service was partially detected, but its complete health check did not pass.
Examples can include:
Open VTS could not complete the verification.
This can happen when a required Windows monitoring command or system tool is unavailable.
The Frontend provides the Open VTS web interface used by Superadmins, Administrators, and Users.
The monitored application port is:
3000
The service card checks:
If the Frontend is unavailable, users may not be able to open the Open VTS web application.
Available actions can include:
The Backend provides the Open VTS API and application logic.
The monitored port is:
4000
The Backend supports operations such as:
The service card checks:
Restarting the Backend temporarily disconnects the current application session and requires the local service-manager agent to be online.
Available action:
A confirmation is displayed before the Backend restart begins.
The Listener receives and processes communication from GPS devices.
Its monitored health or service ports can include:
5055 5005
These are health and service-monitoring ports. GPS devices may communicate through other configured listener ports according to their protocols.
If the Listener is stopped:
Available actions can include:
Nginx acts as the reverse proxy and web gateway for Open VTS.
The monitored ports are:
80 443
Nginx manages normal HTTP and secure HTTPS access to the application.
The health check verifies:
A Degraded state can appear when the process and port state do not match.
Available actions can include:
Reload applies the current Nginx configuration without requiring the same full service restart process.
Use it after an approved configuration or SSL change.

Redis provides fast in-memory storage used by Open VTS for live and temporary operational information.
The monitored port is:
6379
Redis can support:
The health check verifies both:
Available action:
Redis port 6379 should remain private and must not be exposed publicly.
PostgreSQL is the primary relational database used by Open VTS.
The monitored port is:
5432
PostgreSQL stores important platform information such as:
The health check verifies:
Available action:
PostgreSQL port 5432 should remain private and blocked from the public internet.
The Server page provides limited recovery actions for approved services.
Starts a service that is not currently running.
Start is available for:
Stops and starts the selected service through the local service manager.
Restart is available for the monitored services, subject to system availability and safety restrictions.
Use Restart only when:
Reload is available only for Nginx.
Stop is disabled to reduce the risk of locking the Superadmin out of Open VTS.
When an allowed service action is started, Open VTS opens an action-status window.
It can display:
Possible job states include:
After an action completes, the Server page refreshes the health information.
The Recommended Actions section appears when Open VTS detects a stopped or degraded service.
Recommendations can include:
Recommended Actions are generated from the current health checks. They do not mean that the action has already been performed.
Review the service state and warning messages before taking action.
Use the following workflow for a routine server check:
The services work together and should not be treated as isolated components.
A service can appear Running while another dependency is unhealthy.
For example:
Review all service cards together when investigating platform health.
An error message appears when Open VTS cannot retrieve the server overview.
Select Refresh to try again.
Unknown means the server could not complete the required process or port verification.
Check that the required Windows system tools and permissions are available.
When the local agent is offline:
The local service manager should be checked directly on the Windows server.
A dash appears when a system or service metric cannot be obtained.
The Server page is not intended to provide:
Use the appropriate server, database, cloud, or operating-system tools for these activities.
Server screenshots can expose sensitive infrastructure information.
Before publishing screenshots or recordings, hide or replace:
Ports 4000, 5432, and 6379 should remain private and blocked from public access.
Only the required web and GPS device communication ports should be exposed.
Continue to Superadmin Support to review support tickets, requests, and communication associated with the platform.