Log In
Sign Up

Web SSH Console: SSH via Browser, No Client Required

No PuTTY. No client install. No VPN. The Web SSH Console opens a fully encrypted terminal to any server on your gateway in one click — gated behind HTTPS and mandatory two-factor authentication.
30-Day Free Trial
Request a Demo
Works in any modern browser

0

Client software to install

100%

Sessions logged & recorded

2FA

Required on every session

Why it matters

What Is a Web SSH Console? Browser-Based SSH Access Explained

SSH into any server on your Ezeelogin gateway straight from a browser tab — no dedicated SSH terminal, no private keys on laptops, no extra firewall holes per admin. A Node.js service on the gateway brokers the connection, so every session stays behind the same HTTPS, 2FA, and access-control rules you already enforce.
  • Log in from any machine — shared workstation, tablet, or a laptop that was never issued a key
  • No SSH keys to copy, rotate, or revoke per device
  • Every session inherits your existing Access Control and user-group rules
  • Session activity is recorded the same way as any other Ezeelogin login
Why record sessions

Web SSH Console Prerequisites

The Web SSH Console only activates once these three conditions are met — confirm each before troubleshooting a blank screen or connection error.
  • The web interface must be accessed over HTTPS, with a valid or self-signed SSL certificate installed on the gateway.
  • Two-factor authentication must be enabled (or enforced) for the logging-in user — Web SSH will not open without it.
  • Inbound TCP traffic on the Web SSH port (default 52222) must be open, and your own IP whitelisted if a firewall flags it as anomalous traffic.
Getting started

How to Set Up the Web SSH Console (SSH via Browser)

Four stages, run once on the gateway. Each maps to a section in the full Knowledge Base walkthrough.

01

Install Node.js on the gateway

Install npm, then use n to install a current Node.js version on the jump host. 

				
					apt install npm
npm install -g n
n latest

02

Install module dependencies

Pull in the WebSSH console's Node module dependencies via eztool.php. 

				
					php eztool.php --
-install_node_modules
-node_component webssh

03

Configure port, SSL & 2FA

Set the Node.js binary path and Web SSH port under Settings, install SSL certs, and enable 2FA. 

				
					openssl req -new -days 365 -x509 \
-nodes -newkey rsa:2048 \
-out tls_cert.pem -keyout tls_key.pem

04

Grant access & launch

Enable the Web SSH Console permission for the user group, then open it from the Servers tab. 

				
					Access Control → UserGroup-Action
→ Servers → Web SSH Console ✓
Key benefits

Key Benefits of the Web SSH Console

Zero client install

Open a full terminal session from any browser — no PuTTY, no Terminal app, no per-device setup.

2FA enforced by design

The console simply won't open without two-factor authentication and HTTPS — it's not an optional toggle.

Same access rules everywhere

Web SSH inherits your existing Access Control and user-group permissions, down to the individual server.

Recorded like any other session

Sessions opened through the browser are logged for playback and audit exactly like key- or password-based SSH.

Reachable from anywhere

A shared workstation, a tablet, or a laptop that never had a key on it can all reach a server in seconds.

One gateway, one attack surface

Only the gateway's Web SSH port needs to be reachable — target servers stay off the public internet entirely.

How it compares

Web SSH Console vs. Desktop SSH Clients vs. Open-Source Browser SSH Client Tools

Most teams either install a dedicated SSH client per machine, or self-host an open-source WebSSH tool. Here’s the trade-off.
Capability
Ezeelogin Web SSH Console
Desktop Client (PuTTY / Terminal)
Open-Source WebSSH Tool
No install required on the user's device
✓
✖
✓
Two-factor authentication built in
✓
Depends on setup
Usually not
Inherits centralized access-control rules
✓
✖
✖
Session recording & audit logs
✓
✖
Rarely
Setup effort
Once, on the gateway
Per user, per device
Self-hosted & self-maintained
Common questions

Questions about self-hosted bastion hosts

What is the Web SSH Console in Ezeelogin? It’s a browser-based terminal, built into the Ezeelogin gateway, that lets you SSH into any registered server without installing a dedicated SSH client. A Node.js service on the gateway brokers the connection between your browser and the target server.
Do I need 2FA to use the Web SSH Console? Yes. The Web SSH Console only works if the web interface is accessed over HTTPS and the logging-in user has two-factor authentication enabled or enforced. There is no way to open it without both conditions met.
Which Node.js version is required for Web SSH? Node 19 or above, with npm 6 or later, is recommended. You can check your installed versions with node -v and npm -v on the gateway.
Why is my Web SSH Console showing a blank page? This is most often caused by upgrading from an Ezeelogin version below 7.4.0 without resetting the gateway user’s password, or by a certificate/permission issue on the .pem files. Resetting the password from the GUI and confirming the .pem files are readable by the web-server user resolves most cases.
Can I use Web SSH without a valid SSL certificate? A self-signed certificate is enough — the feature simply requires SSL/HTTPS to be present. Generate one with OpenSSL and point Ezeelogin’s config files at it, or install a certificate you already have.

Give your team browser-based SSH access today

Set up the Web SSH Console on your gateway in under 20 minutes — 2FA and session recording included, no extra licensing.
30-Day Free Trial
Request a Demo
Trusted by hosting companies managing millions of servers since 2009.