Remote access8 min
WebSSH sessions
Open a browser terminal over the private overlay and recover from transient transport loss.
Outcome
A persistent browser SSH session without publishing port 22.
Before you start
- An online device with SSH
- Valid SSH credentials
- SSH reachable from the overlay path
Create the connection
- 1Open WebSSH and choose New connection.
- 2Select the device or its assigned overlay address.
- 3Confirm port, username and authentication method.
- 4Save it with a device-and-role name.
- 5Choose Connect.
Operational note: Wantastic provides the path; it cannot enable a stopped SSH daemon.
Use and resume the terminal
- 1Confirm the prompt identifies the expected host.
- 2Start with hostname, uptime and ip route.
- 3Allow automatic stream recovery after a brief transport interruption.
- 4Use manual Reconnect only when recovery does not restore the stream.
- 5Close finished sessions.
Operational note: Use tmux, screen or a service manager for long-running work.
Verify the result
The prompt identifies the host.
Commands return in the browser.
No public SSH rule is needed.
Transport recovery resumes or offers a clear reconnect action.
Common issues
Connection refused.
Likely cause
sshd is stopped, bound elsewhere or on a different port.
Fix
Check SSH locally, its listen address and port, then update WebSSH.
Authentication fails.
Likely cause
Username, key/password or sshd policy does not match.
Fix
Test the same identity locally and replace the saved credential deliberately.
Output freezes.
Likely cause
The WebSocket or underlying network was interrupted.
Fix
Wait for recovery, use Reconnect, and start a new shell only if the prior process ended.