Skip to main content

Verify the installation

Verify the runtime before exposing it through a gateway or treating the installation as recoverable. Complete these checks after the first start and after significant deployment changes.

Check container health​

From the repository root, inspect the production stack:

docker compose --env-file .env -f compose/docker-compose.yml ps

The unified app, database, and Redis services should be running, and services with health checks should become healthy. Riviamigo's app health check verifies its Redis-backed secure-session store, so it remains unhealthy if Redis is unreachable or rejects the configured password. If a service is restarting or unhealthy, inspect its recent logs before changing configuration:

docker compose --env-file .env -f compose/docker-compose.yml logs --tail=200

For one service, append its Compose service name to the logs command.

For a secure-session failure, inspect the Riviamigo logs for secure_session_store.unavailable and confirm the app and Redis containers use the same current REDIS_PASSWORD; do not expose either password in a terminal, ticket, or log. Correct the configuration and restart through your normal deployment workflow. The app must become healthy before attempting owner or vehicle setup.

Check the private origin​

Open http://localhost:8080 from the host. The login or first-owner setup screen should load; use a host firewall and authenticated gateway before exposing it remotely.

If the page does not load:

  1. Confirm the web and API services are healthy.
  2. Confirm another process is not occupying the configured origin port.
  3. Review the web and API logs.
  4. Recheck required values in Configuration.

Create and confirm the first owner​

The first completed account setup becomes the installation owner. After signing in:

  • Confirm the session survives a normal page refresh.
  • Open Settings and confirm owner-only administration surfaces are available.
  • In Settings → Account, confirm the password form shows its live 12-character requirement before attempting a change. A completed password change signs out every browser session; sign in again with the replacement password.
  • Do not create additional users until the first owner and access boundary are verified.

Confirm Rivian connectivity​

Follow Rivian account setup, then confirm:

  • The connected vehicle appears in the vehicle selector.
  • Current vehicle status eventually appears after Rivian authentication succeeds.
  • Sleeping vehicles are allowed time to report; missing immediate telemetry is not automatically an installation failure.
  • Persistent authentication or MFA errors are handled through the Rivian connection flow rather than by repeatedly restarting the entire stack.

Verify the gateway before remote use​

After local verification, configure the authenticated HTTPS gateway described in Secure deployment. From the final public address, confirm:

  • HTTPS is valid.
  • Authentication is required before Riviamigo is reachable.
  • Normal API requests succeed after sign-in.
  • Live vehicle updates do not show WebSocket connection failures.
  • Host firewall rules and the authenticated gateway protect port 8080 from direct public access.

Establish a recovery baseline​

Once the installation is healthy and connected, follow Backup and restore to create and verify the first recovery package. A running dashboard without a tested recovery package is not a complete installation.