SSH into networked server remotely

sshturnkey-linuxweb-server

I have setup a virtual server running MediaWiki (a TurnKey appliance). I have got the server up and running and have assigned it a static IP address on the local network.

I have also assigned the server a public IP address by setting up a DMZ host on the router. The router is a Draytek Vigor 2820.

I have tried using SSH/SFTP/FTP to access the server remotely but they all timeout. The turnkey appliance comes with Shell in a box as standard and that works fine.

I have checked the firewall using the webmin interface and port 22 is allowed.

Am I missing any vital steps?

For reference the appliance product page can be seen here: http://www.turnkeylinux.org/mediawiki

Update:

The public ip address fails when I ping it from the remote location (any remote location) and a port test shows port 22 as closed. I presume this narrows the problem down to the router?

Best Answer

"I'm unsure how to open port 22 for multiple servers."

If you want to run multiple servers/applications on the same/overlapping standard port number assignments, then you will need multiple routable IP addresses for access to each across the Internet.

Related Solutions

Ssh – How to automate SSH login with password

Don't use a password. Generate a passphrase-less SSH key and push it to your VM.

If you already have an SSH key, you can skip this step… Just hit Enter for the key and both passphrases:

$ ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.

Copy your keys to the target server:

$ ssh-copy-id id@server
id@server's password:

Now try logging into the machine, with ssh 'id@server', and check-in:

.ssh/authorized_keys

Note: If you don't have .ssh dir and authorized_keys file, you need to create it first

to make sure we haven’t added extra keys that you weren’t expecting.

Finally, check to log in…

$ ssh id@server

id@server:~$

You may also want to look into using ssh-agent if you want to try keeping your keys protected with a passphrase.

SSH – Bad Owner or Permissions on ~/.ssh/config

I needed to have rw for user only permissions on config. This fixed it.

chmod 600 ~/.ssh/config

As others have noted below, it could be the file owner. (upvote them!)

chown $USER ~/.ssh/config

If your whole folder has invalid permissions here's a table of possible permissions:

Path	Permission
.ssh directory (code)	0700 (drwx------)
private keys (ex: `id_rsa`) (code)	0600 (-rw-------)
`config`	0600 (-rw-------)
public keys (*.pub ex: `id_rsa.pub`)	0644 (-rw-r--r--)
`authorized_keys` (code)	0644 (-rw-r--r--)
`known_hosts`	0644 (-rw-r--r--)

Sources:

openssh check-perm.c
openssh readconf.c
openssh ssh_user_config fix_authorized_keys_perms

Best Answer

Related Solutions

Ssh – How to automate SSH login with password

SSH – Bad Owner or Permissions on ~/.ssh/config

Related Topic