Recommended Requirements (Linux)

1 vCPU or any modern CPU
512+ MB RAM
10 or 100mbps+ Network Card
Your built application will need a public host name or an IP address of your server. e.g. 113.3.2.23 or myserver.mycompany.com
For SSH public port 443 is recommended since it is firewall friendly. As an alternate you can use any port that is reachable by your users.

CentOS, Ubuntu, Red Hat (Most Linux versions have default SSH server)

Below are some sample configuration options. Every setup is different- please work with your network administrator for the optimal security and settings for your environment.

Disable any programs listening on Port 443 or use default port 22.
    Typically apache web server will be listening on this port.
    vi /etc/httpd/conf.d/ssl.conf
    Comment out line #Listen 443
    Restart apache server (/etc/init.d/httpd restart)

Change ssh server listener port to 443
    vi /etc/ssh/sshd_config
    Edit this line in the file ("Port 22" to "Port 443")
    Restart ssh server (/etc/init.d/sshd restart)

Create a new user and change password.
    /usr/sbin/useradd someuser -s /sbin/nologin
    /usr/bin/passwd showmypcuser
    Enter the new password, when prompted.


  Some SSH server installations are configured to refuse the authentication type "password". Often, they only accept "publickey" and "keyboard-interactive". Enable password authentication. E.g., edit /etc/sshd/sshd_config and change the value of "PasswordAuthentication" to "yes", then send a HUP signal to the daemon so that it re-reads its configuration or Restart server or SSH.

Important last Step. Test your SSH server.

Once your server is setup you may test using a Windows SSH client. Get Putty SSH Client
Make sure you are able to connect from a remote location outside your network using the SSH username and password you are providing us.
Once the testing is complete, to secure your system, we can help you with using an identity file instead of password with your setup.

Now you may request your application.