Studio Watchdog Management
The Studio Watchdog page stores Watchdog service connections. Studio uses these connections to test status, upload projects, download projects, and open backup management.

| Area or action | Description |
|---|---|
| Add gateway service | Open the service configuration panel. |
| Card/list view | View saved Watchdog services. |
| Test | Test Studio-to-Watchdog connectivity. |
| Backup | Open the backup panel for the selected Watchdog. |
| Edit | Update service name, address, port, username, and password. |
| Delete | Delete the saved connection only; it does not delete remote projects or backups. |
Status Meaning
| Status | Description | Suggested action |
|---|---|---|
| Watchdog online | Studio can reach Watchdog and read status. | Upload, download, and backup operations can be used. |
| Watchdog offline | Studio cannot reach Watchdog. | Check address, port, firewall, account, and service status. |
| Gateway running | Watchdog sees GatewayRuntime running. | Create a backup before restore or publish operations. |
| Gateway stopped | Watchdog is online but GatewayRuntime is stopped. | Open Watchdog Web dashboard and logs. |
| Gateway unknown | Watchdog is offline or status read failed. | Restore Watchdog connectivity first. |
Add or Edit Service

| Field | Description |
|---|---|
| Service name | Display name in Studio. Include site or line information. |
| Service address | Watchdog host address without port. Plain HTTP IP is supported, for example 192.168.1.20. |
| Service port | Watchdog Web/API port, usually 6200. |
| Username | Watchdog login username. |
| Password | Watchdog login password. |
After saving, run "Test" immediately. A successful test confirms Watchdog access, not necessarily that GatewayRuntime is healthy.
Studio automatically obtains a Watchdog one-time RSA-OAEP-SHA256 challenge, encrypts the stored password, and exchanges it for a Bearer session. Connection tests, status polling, upload/download, and backup operations use Bearer rather than Basic Authentication. If a Watchdog restart invalidates a cached session, Studio logs in again and retries once.
Backup Panel

| Column or action | Description |
|---|---|
| Name | Backup file name on the target Watchdog. |
| Create time | Backup creation time. |
| Size | Backup size. |
| Restore | Restore this backup as the target project. |
| Delete | Delete this backup from the target Watchdog. |
Restoring a backup changes the remote gateway project. Confirm that a rollback version exists before restoring.
Used by Upload and Download

The upload target list on the Projects page comes from the Watchdog services saved here.

The download source gateway list also comes from these saved Watchdog services.
FAQ
| Symptom | Suggested action |
|---|---|
| Test fails after adding service | Check whether the address accidentally includes a port, whether the port is correct, and whether credentials are valid. |
| Plain HTTP IP cannot be saved or reached | The current version allows it. Verify the 0.0.0.0:6200 listener, remote management, plain HTTP permission, and firewall. |
| The test returns 401 | Check the Watchdog credentials. Persistent 401 responses after automatic re-login normally mean the credentials are invalid. |
| The test returns 403 | Check RemoteManagementEnabled; deployment and process control also require RemoteDeploymentEnabled. |
| Watchdog online but gateway stopped | Open Watchdog Web dashboard and logs for the last error. |
| Backup panel is empty | Confirm backups exist on Watchdog, or check whether reading the backup list failed. |
| Upload target list is empty | Add and save a Watchdog service first. |
| Restore causes runtime errors | Inspect Watchdog logs and restore another known-good backup if needed. |