---
title: Edge Server Overview
description: Tour of the ControlCom Edge Server local web UI: signing in, the Overview dashboard, and how Health, Tools, Settings, and Local Commands fit together.
source: https://documentation.controlcomtech.com/build/edge-server/web-interface/overview
---

# Edge Server Overview

Every ControlCom Edge Server ships with a local web UI for monitoring, diagnostics, and on-device configuration. It runs on the same container as the data pipeline and is meant for operators who are physically on the device's network, for example a technician on the plant floor or an integrator running a commissioning visit.

> **Workflow Stage: Collect**

This guide covers the UI's structure and the Overview dashboard. The other pages in this section drill into specific areas:

* [Health](https://documentation.controlcomtech.com/build/edge-server/web-interface/health): live values, client diagnostics, MQTT publisher status, system metrics
* [Tools](https://documentation.controlcomtech.com/build/edge-server/web-interface/tools): MQTT Explorer, Ping, Modbus, BACnet, Live Logs
* [Settings](https://documentation.controlcomtech.com/build/edge-server/web-interface/settings): Security and LoRaWAN configuration
* [Local Commands](https://documentation.controlcomtech.com/build/edge-server/web-interface/local-commands): auth and remote-execution policies for per-command security

## Accessing the UI

Once the Edge Server container is running (see [Getting Started](https://documentation.controlcomtech.com/build/edge-server/getting-started)), open a browser on the same network and navigate to:

```
https://<edge-server-host>:3041
```

Use `localhost` when you're on the same machine. Use the host's LAN address when accessing remotely.

## Signing In

The UI is protected by a local admin account that is separate from your ControlCom Connect cloud account. On a fresh container, sign in with the default credentials below, then change the password from [Settings → Security → Account](https://documentation.controlcomtech.com/build/edge-server/web-interface/settings#security-account).

**Default credentials**

```
Username: admin@local.admin
Password: admin
```

## Overview Dashboard

The Overview page (`/overview`) is the landing page after sign-in. It is designed as a single-glance health check.

**Header**

* The device's friendly name and assigned location (from platform configuration).
* A **Healthy** / **Issues detected** badge that turns amber whenever the MQTT publisher is offline or any client is disconnected.

**Stat cards**

| Card                 | What it shows                                                                                                         |
| -------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Cloud Connection** | MQTT publisher connection state and the cumulative count of items published since startup.                            |
| **Clients**          | Number of connected clients vs. configured clients (for example `3 / 4`), with the names of any disconnected clients. |
| **Variables**        | Total tracked internal variables, with a breakdown by source (per client type plus Internal State Variables).         |
| **System**           | Process uptime plus working-set memory and current .NET thread count.                                                 |

**Quick actions**

* **Configure on Console**: opens the ControlCom Connect cloud console in a new tab. All structural device configuration (adding clients, variables, virtual variables, triggers) lives in the cloud.
* **Open Health**: jumps to the [Health](https://documentation.controlcomtech.com/build/edge-server/web-interface/health) section.
* **Open Settings**: jumps to [Settings](https://documentation.controlcomtech.com/build/edge-server/web-interface/settings).

The dashboard refreshes every 10 seconds. The footer shows the device's unique ID, which you may be asked for during support cases.

## Navigation

The left navigation groups screens by purpose:

* **Overview**: the dashboard above.
* **Health**: live observability into variables, clients, the MQTT publisher, and the host system.
* **Tools**: interactive diagnostics that bypass the production pipeline (MQTT Explorer, Ping/TCP, ad-hoc Modbus, ad-hoc BACnet, live logs).
* **Settings**: admin password, mTLS certificate bundle, LoRaWAN network server, LoRaWAN gateway certificates.
* **Settings → Commands**: per-command authentication and remote-execution policies.