Studio Web Manual
Studio Web manages projects, development runtime control, tunnel Broker configuration, and Watchdog connections.
Login and Overview
Open http://<Studio-server-IP>:5100, then enter the Studio 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. After login, Studio uses a JWT Bearer for protected requests. Users do not need to obtain a key or enter a token manually.
The RSA challenge only adds protection to the login or bootstrap password field. Bearer tokens, password-change requests, project packages, and other traffic still have no TLS protection over plain HTTP, so use HTTPS on public or untrusted networks.
| Area | Description |
|---|---|
| Current project | Project currently running in the Studio development runtime. |
| Tunnel service | Studio Broker status, endpoint count, and port. |
| Watchdog | Saved Watchdog service health. |
| Gateway version | Runtime version and update status. |
| Recent projects | Quick entry to recently maintained projects. |
Projects
| Operation | Description |
|---|---|
| New project | Create a local project. |
| Import project | Import a ZIP project package. |
| Start/stop runtime | Start a project in the development runtime or stop the current runtime. |
| Export | Download a project ZIP. |
| Upload | Publish a project to a configured Watchdog. |
| Plugin management | Enable, disable, or inspect project plugins. |
| Download from gateway | Pull a project package from Watchdog into Studio. |
Before uploading, test the target Watchdog connection, check plugin status, and create a backup on the target gateway.
Tunnel Broker
| Field | Description |
|---|---|
| Enable tunnel | Enable Studio Broker configuration. |
| Broker port | Port used by Watchdog clients. |
| Auth token | Must match the Watchdog client. |
| Access key | Must match the Watchdog client. |
| Start/stop server | Start or stop the Broker. |
| Endpoint information | View bound Watchdog clients and exposed addresses. |
Watchdog Connections
| Field | Description |
|---|---|
| Service name | Display name in Studio. |
| Service address | Watchdog host without port. |
| Service port | Watchdog port, usually 6200. |
| Username/password | Watchdog credentials. |
The service address may be a device IP over plain HTTP, for example host 192.168.1.20 and port 6200. Studio automatically uses the Watchdog one-time password challenge and a Bearer session; it does not use Basic Authentication.
Use "Test" after saving a service. Backup restore changes the target gateway project, so confirm rollback plans before restoring.
Troubleshooting
| Symptom | Suggested action |
|---|---|
localhost works but the IP does not | Verify the 0.0.0.0:5100 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. |
| Watchdog is offline | Check its IP, port, credentials, remote management, firewall, and service logs. |