Web Setup

RemoteConsoleSSH works directly in your web browser with no installation required. This is the fastest way to get a terminal session running, and it is ideal for quick access from a desktop or laptop where you do not have the native app installed.

Requirements

A modern web browser: Chrome (recommended), Firefox, Safari, or Edge
An SSH-enabled remote machine (see prerequisites)
Network connectivity to the remote machine

💡

Tip

Chrome delivers the best experience due to its superior WebSocket performance and clipboard API support. Safari works but may have minor rendering differences in the terminal.

Getting Started

There is no installation step for the web version. Open the RemoteConsoleSSH web app in your browser and you are ready to go.

Open the web app

Navigate to the RemoteConsoleSSH web app URL in your browser. Bookmark it for quick access in the future.

Set a PIN code

On first launch, you will be prompted to create a PIN. This PIN protects your saved connections within the browser session. It is hashed before being stored in the browser's local storage.

ℹ️

Info

The web version does not support biometric authentication (Face ID / Touch ID / fingerprint). PIN is the only available unlock method. If you need biometric security, use the iOS or Android native app.

Add a connection

Click the "+" button to add a new SSH connection. Enter the same details as the native apps:

Name — A label for the connection
Hostname or IP — The remote machine's address
Port — SSH port (default: 22)
Username — Your user account on the remote machine
Authentication — Password or SSH key (paste the private key into the text field)

Connect

Click the connection to initiate the SSH session. Accept the host key on first connection, and you will see a terminal prompt.

uname -a

Run a command to verify everything is working.

Limitations Compared to Native Apps

The web version provides the same core SSH terminal experience, but some features are not available due to browser platform constraints:

Feature	Native Apps (iOS / Android)	Web
SSH Terminal	Full support	Full support
tmux Sessions	Full support	Full support
SFTP File Transfer	Full support	Full support
Authentication	PIN + Biometrics	PIN only
Voice Control	Full support	Not available
SSH Key Import	Paste or file picker	Paste only
Session Persistence	Survives app restart	Lost when tab closes
Secure Storage	OS Keychain / Keystore	Browser local storage
Background Connections	Brief background execution	Tab must remain open

Key differences explained

No biometric authentication — Browsers do not expose Face ID or fingerprint APIs for app-level authentication. You will use your PIN every time you open the web app.

No voice control — The Web Speech API has limited browser support and does not provide the reliability needed for terminal command interpretation. Voice control is exclusive to the native apps.

SSH key import is paste-only — The native apps let you pick a key file from your device's file system. In the browser, you will need to copy your private key and paste it into the text field. This works fine but requires an extra step.

Sessions do not persist across tab closures — If you close the browser tab or navigate away, the SSH connection is terminated. When you reopen the web app, you will need to reconnect. If tmux is running on the server, you will reattach to your existing session and no work is lost.

⚠️

Browser Storage

The web app stores connection details and your PIN hash in the browser's local storage. Clearing your browser data (cache, cookies, local storage) will erase all saved connections. This storage is also not encrypted at the hardware level like the native apps' keychain/keystore. Avoid saving connections on shared or public computers.

No background connections — Unlike the native apps, which can briefly maintain connections in the background, the browser will suspend or close the WebSocket connection if the tab is not active for an extended period. Keep the tab visible and active during your session.

Best Use Cases for the Web Version

The web version is the right choice when:

Quick access from a desktop — You are at a workstation that does not have the native app and need to SSH into a server quickly.
Shared or borrowed devices — You do not want to install software on a machine you do not own. Just open the browser, connect, and close the tab when done.
Supplementing native apps — You use the iOS or Android app as your primary client but occasionally need terminal access from your laptop.
tmux session management — Start a session on your phone, then pick it up on the web when you sit down at your desk. tmux makes cross-device session continuity seamless.

💡

Tip

For the best experience on desktop, consider using Chrome's "Install as App" feature (available in Chrome's menu as "Install RemoteConsoleSSH"). This opens the web app in its own window without browser chrome, giving it a native-app feel with keyboard shortcuts that do not conflict with browser shortcuts.

Web-Specific Tips

Keyboard Shortcuts

When using the web version on a desktop with a physical keyboard, you have direct access to all terminal keys without needing a toolbar. Standard terminal shortcuts work as expected:

Ctrl+C — Interrupt the current process
Ctrl+D — Send EOF / logout
Ctrl+Z — Suspend the current process
Ctrl+L — Clear the terminal screen
Tab — Autocomplete commands and paths
Up/Down arrows — Navigate command history

ℹ️

Info

Some keyboard shortcuts (like Ctrl+W to close a tab) are intercepted by the browser before they reach the terminal. The terminal toolbar provides buttons for these conflicting shortcuts so you can still send them to the remote shell.

Clipboard Access

The web terminal supports copy and paste:

Copy: Select text in the terminal, then use Ctrl+C (when no process is running) or right-click and choose Copy.
Paste: Use Ctrl+V or right-click and choose Paste. Your browser may ask for clipboard permission on first use — grant it for a smooth experience.

Multiple Tabs

You can open multiple browser tabs to connect to different servers simultaneously, or even open multiple terminal sessions to the same server. Each tab operates independently.

Troubleshooting

Connection fails immediately

Verify the remote machine's SSH server is running and reachable from your network.
Check that your browser is not blocking WebSocket connections (some corporate proxies or browser extensions do this).
Try disabling browser extensions temporarily to rule out interference.

Saved connections disappeared

Your browser's local storage may have been cleared. This happens if you clear browsing data, use incognito/private mode, or if a browser cleanup tool runs automatically.
Connections stored in private/incognito windows are deleted when the window closes.

Terminal rendering looks wrong

Ensure your browser is up to date. Chrome, Firefox, Safari, and Edge all receive frequent updates that improve WebSocket and rendering performance.
Try zooming the page to 100% (Ctrl+0 / Cmd+0) if the terminal font looks misaligned.
If characters appear garbled, verify the server's locale is set to UTF-8.

Session disconnects when tab is inactive

This is expected browser behavior. Keep the tab visible and active during your session. Using tmux on the server ensures you can reattach after any disconnection.