PD DigitalOcean Droplets can offer customers a browser SSH terminal from a running service. Enable the module-wide console setting and the package’s console control; one does not override the other.

Prepare an eligible service

Use an already provisioned running server and review whether browser-terminal access suits your offering. The optional console uses PD’s hosted relay while connected. Direct SSH remains a separate access method through the server’s connection details and key.

The console uses the module-generated service key. A separately saved team public key does not replace that key or establish console eligibility; check that the generated service key is available. Do not remove a customer’s working key to investigate the console.

Enable the two controls

1. Open PD Modules → DigitalOcean Droplets → Settings.
2. Turn on Enable the in-browser SSH console and save.
3. Open Packages → Packages → your package for the offering attached to the service.
4. Enable Client: Console and save the package.
5. Your customer opens an eligible running service in the client area and check for Open console on the service’s Information tab.
6. Open a session, confirm it reaches the intended server and close it after use.

If the console is absent

Check the module-wide switch, the actual service’s package control, the running/setup state and generated-key availability. A suspended service is not a way to test normal customer console access. Do not reinstall the operating system to investigate a missing button.

If a session cannot connect

Separate button visibility from SSH reachability. Check the service state, relevant firewall access and the displayed console error. Compare with direct SSH access if appropriate; a functioning direct connection helps narrow the problem but does not prove the browser path is healthy.

Keep server keys and session tokens out of any recording or attachment.

See the PD DigitalOcean Droplets Blesta guide for related tasks, or explore the module.