Hosting
Browser console
Reach a server when SSH cannot: how the VNC and serial consoles work.
When to use it
A firewall rule locked you out, the network stack is misconfigured, the machine is stuck at boot, or you need to watch a reboot. The console gives you the screen (VPS) or the serial line (dedicated) directly, independent of the guest’s network.
How it is done
- 1
You click Open console
The DevSewa console asks the control plane for a console ticket. The hosting engine checks the server belongs to your application and issues a signed, single-use ticket that expires in 60 seconds. - 2
The browser connects
Your browser opens a WebSocket to the hosting engine’s public console endpoint and presents the ticket. Nothing else identifies the session — no cookie, no server id in the URL. - 3
The engine bridges
For a VPS the VNC display is bound to the hypervisor’s loopback only. The engine opens an SSH channel to the host and forwards that loopback port into the WebSocket. For a dedicated server it attaches to the controller’s serial-over-LAN session instead. - 4
noVNC renders it
The console page runs noVNC in the browser. When you close the tab the channel closes; a ticket can never be reused.
What never crosses the edge
The DevSewa console and this site never proxy console traffic and never hold a VNC password. The bridge lives in the hosting engine; the hypervisor’s VNC port is not reachable from anywhere else.
Route
POST
/v1/applications/{id}/hosting/servers/{server_id}/console-ticketconsole→ 201 {
"kind": "vnc",
"ws_url": "wss://hosting.api.devsewa.com/console/ws?ticket=…",
"expires_in": 60,
"single_use": true
}
→ 501 { "detail": "hosting_backend_501: console_unavailable" }