Intranet Tunnel
The tunnel feature exposes a GatewayRuntime service inside the Watchdog network through a Studio-side Broker. Configure the Broker in Studio Web and configure the client in Watchdog Web.
| Role | Page | Purpose |
|---|---|---|
| Studio Broker | Studio Web > Tunnel | Accepts Watchdog client connections and listens on external addresses. |
| Watchdog Client | Watchdog Web > Tunnel | Connects to the Broker and forwards an internal service. |
| Origin address | Watchdog client configuration | Service reachable from the Watchdog host, such as 127.0.0.1:6100. |
| Exposed address | Watchdog client configuration | Address listened on the Broker side, such as 0.0.0.0:8889. |
Studio Broker
| Field or action | Description |
|---|---|
| Enable tunnel | Enable or disable Broker configuration. |
| Broker port | Port used by Watchdog clients to connect to the Broker. |
| Auth token | Must match the Watchdog client auth token. |
| Access key | Must match the Watchdog client access key. Leave both sides empty if not used. |
| Save | Save the form values. |
| Reset | Reload saved configuration. |
| Start server | Start the Broker with the saved configuration. |
| Stop server | Stop the running Broker. |
The "Endpoint information" tab lists bound clients, tunnel IDs, modes, exposed addresses, and bound time.
Watchdog Client
| Action | Description |
|---|---|
| Enable tunnel | Global Watchdog tunnel switch. |
| New client | Add a client in the configuration panel. |
| Card/table view | Switch display mode; table view supports batch delete. |
| Activate all / deactivate all | Start or stop all configured clients. |
| Config | Open full client configuration. |
| Field | Description |
|---|---|
| Client name | Required and unique within one Watchdog instance. |
| Enable | Whether this client participates in activation. |
| Tunnel server address | Studio Broker IP or domain. |
| Tunnel server port | Studio Broker port. |
| Auth token | Same as Studio Broker. |
| Access key | Same as Studio Broker. |
| Origin address | Internal service address reachable from Watchdog. |
| Exposed address | Broker-side address exposed to external users. |
| Reconnect interval | Delay before automatic reconnection. |
Joint Debugging Steps
- Save Studio Broker port, auth token, and access key.
- Start the Studio Broker and confirm the status is running.
- Enable tunnel in Watchdog Web.
- Add a Watchdog client with the Studio Broker address and matching credentials.
- Set origin address, for example
127.0.0.1:6100. - Set exposed address, for example
0.0.0.0:8889. - Save and activate the client.
- Check Studio "Endpoint information" for the bound endpoint.
- Access
http://<StudioServerIP>:<exposedPort>from the external network.
Troubleshooting
| Symptom | Suggested action |
|---|---|
| Broker fails to start | Check port occupation, port range, and whether configuration was saved. |
| Client not activated | Check the global Watchdog tunnel switch and saved client configuration. |
| Client disconnected | Check Broker status, address, port, network, and firewall. |
| Connected but not bound | Check access key and exposed port occupation. |
| Endpoint list is empty | Refresh Studio endpoint tab and inspect Watchdog logs for binding errors. |
| External access fails | Check exposed port firewall, origin address reachability, and GatewayRuntime status. |