Watchdog Web Manual
Watchdog Web supervises GatewayRuntime and provides project package management, runtime logs, backups, tunnel clients, and runtime settings.
Login and Dashboard
Open http://<gateway-IP>:6200, then enter the Watchdog username and password. The packaged host officially supports plain HTTP IP access and does not require a localhost URL or a browser secure context.

The page automatically obtains a two-minute, one-time RSA-OAEP-SHA256 public-key challenge and encrypts the password before submission. Watchdog then issues an opaque Bearer session valid for eight hours. Logout revokes the current session, and a Watchdog restart invalidates all in-memory sessions.
The RSA challenge only adds protection to the login or bootstrap password field. Bearer tokens, password-change requests, project packages, backups, and other traffic still have no TLS protection over plain HTTP, so use HTTPS on public or untrusted networks.

| Area | Description |
|---|---|
| Status banner | Watchdog status, GatewayRuntime status, uptime, version, process ID, current project, and last error. |
| Start failure count | Should normally be 0. |
| Health check interval | Interval used by Watchdog to check GatewayRuntime. |
| API port | GatewayRuntime API port checked by Watchdog. |
| Restart/stop gateway | Runtime control actions that require confirmation. |
| Live logs | Recent logs for startup, stop, and error inspection. |
Projects


| Operation | Description |
|---|---|
| Upload | Upload .zip or .db project files. |
| Apply | Apply a non-current project as the current GatewayRuntime project. |
| Download | Download a project package. |
| Delete | Delete non-current projects. |
| Batch delete | Delete selected non-current projects. |
Create a backup before applying a different project in production.
Logs and Backups

| Control | Description |
|---|---|
| Lines | Read 50, 100, 200, or 500 log lines. |
| Auto refresh | Keep refreshing logs while troubleshooting. |
| Export | Export current logs to a text file. |

| Operation | Description |
|---|---|
| Create backup | Create a backup of the current project. |
| Restore | Restore a backup as the current project. |
| Delete / batch delete | Remove backup files. |
| Max count | Comes from Watchdog settings. |
Tunnel



| Field | Description |
|---|---|
| Enable tunnel | Global Watchdog tunnel switch. |
| Client name | Unique client name. |
| Broker host/port | Studio Broker address and port. |
| Auth token/access key | Must match Studio Broker. |
| Origin address | Internal service reachable from Watchdog. |
| Exposed address | Broker-side external address. |
| Reconnect interval | Reconnect delay in seconds. |
Settings


| Group | Fields |
|---|---|
| Account security | Username, change password. |
| Gateway runtime | Auto start gateway, arguments, API port, health check interval, API timeout, max start failures. |
| Backup strategy | Max backup count. |
| Security | Allowed origins. |
After changing runtime settings, return to the dashboard and observe at least one health check cycle.
Troubleshooting
| Symptom | Suggested action |
|---|---|
localhost works but the IP does not | Verify the 0.0.0.0:6200 listener, remote management, plain HTTP permission, and firewall. |
The page reports an importKey error | Clear browser and proxy caches and redeploy the complete current static assets. The current login path does not use subtle.importKey. |
| The login challenge is invalid | Submit again to obtain a new challenge. A challenge expires after two minutes and can be used only once. |
| The page returns to login after restart | The in-memory Bearer session was invalidated; log in again. |