Connecting to MemShell SSH

SSH Client

MemShell is accessed over SSH so an SSH client is required to connect to the MemShell server and from there your server.

Connecting from Windows
If you are using Windows, we recommend PuTTY. See Using PuTTY on Windows for instructions on how to connect to your server.

Connecting from Linux
For UNIX and Linux systems we recommend the OpenSSH SSH client (installed using the system's package manager). Please see the Using OpenSSH on Linux section for instructions on how to connect to your server.

Connecting to your server with MemShell

Logging into your server via MemShell is a two stage process. The first stage is logging into the MemShell server and from there the second is logging into your server. These two steps are required because the Memset MemShell server enforces authentication and secure communication across the internet.

Both of these stages require several pieces of information. The first stage; logging into the MemShell server, requires all of the following for SSH Client Configuration:

Host Nameshell.memset.comor shell-du.memset.com
Port22
UserNameThe name of your server (e.g. memseaa1)
PasswordThe password given when MemShell was enabled

This information is all available on the ‘’’MemShell Settings’’’ page in your Memset account for the server you wish to log into. This page can be located at:

Account Overview -> Services -> Server / Miniservers -> Manage -> MemShell Settings

The password will be displayed when MemShell is enabled for the server. If you no longer have that password simply reset the password using the Password Reset section at the bottom of the Settings page. The new password is instantly updated and can be reset as many times as you want.

The second stage is logging into your server. This will require a valid username and password that you have configured on your server.

N.B. You may receive a "Selected hunt group is busy" error message after authentication. This means that either you are already connected, or an existing connection has not timed-out yet. Please either close the other connection or wait 5 minutes and try again.

Last updated 15 March 2017, 07:43 GMT