If you are on server's terminal, can you connect to your system from server?
You haven't told your linux distribution of your server. I am assuming it is debian based.
Open server's terminal and run
if still it does not restart it, now run
what is output of it.
These all commands you need to run on server's terminal.

If you are not able to connect to server using ssh then you can not run these commands on server's command prompt from your system.
You need to open server's terminal physically and run these commands there.

gives this error:
while this doesn't give any results.
I used to be able to connect like this, this morning I used to restart the ssh and ever since then this hasn't worked.

How do I physically open the terminal?

I'm really sorry to ask but I've still not managed to get this sorted. Would you mind talking me through doing this from the very beginning? I'm more than happy to pay for your help but I'm so desperate to get this sorted.

Thank you

Hi,

as far as I can tell you still haven't answered questions that you've been asked. First off what distro is this? The output of the following command should provide that information
Evo2.

I'm sorry I'm not being to be awkward I don't know what distro it is. This is the first time I've ever used this before so don't know how to find out. I know that it was set up using AWS EC2 and runs Ubuntu.

I opened the Terminal then typed that in but it said: -bash: lsb_release: command not found Should I be doing something before I try to type that?

Try

That just gave me this: cat: /etc/*release*: No such file or directory

Sorry to be so dumb but can we go right back to the beginning as I'm sure I'm doing something wrong.

If I open Terminal what should be the first thing I should do?

I'm more than happy to pay for help to get this fixed but I really need to get it sorted asap as my boss keeps asking about when they can see the changes and I can't upload anything at all at the moment

I don't get what's all this hasle..

Unfortunatly, you've looked yourself out because the new port is firewalled...

Basically, you modified the port on which sshd service is running but you did not allow that port to accept connections on the server..

That is why you get "Connection refused" when trying to acces port 22 (which the firewall allows the connection but the port is unbinded and a reject is sent by the system -- it resembles a closed port) and you get a "Request timeout" when accesing port 1993 because the firewall simply drops all packets to that port and gives no further answer ..

The only way to fix this is by gaining acces to the server itself because SSH is now out of the question.. If you have such access or have any other means to gain such access to a terminal on the server, well, then we can help..

Thank you, I have access to the AWS console if that helps. I'm happy to try anything....

It should help but I'm not familiar with it and can't really help you out because of this.. Basically search if it can access the server's file-system and allows you to do a restart, then you're golden... just modify the SSH service back to port 22 and restart the server.. Or maybe it can directly modify the firewall? Or restart services (thus not needing a full restart of the (virtual) server).. I don't know exactly what AWS Console can do but any of these should be fine..

Go to your EC2 AWS Console, under NETWORK & SECURITY click on Security Group, It will show up the security group you saw before. Click on it, it will show a split screen where the one is above has 2 tabs: Details and Inbound. Go to Inbound, in port range input 22 and source the ip you want to allow incoming access to instance. Don't forget to apply changes.
http://docs.aws.amazon.com/gettingst...ity-group.html

I've now managed to connect using FileZilla, but if I type into the terminal I get this error:

How do I use ./deploy.sh livesite to connect via SSH?

Because still the port 22 is not opened on your server. You need to open it using AWS console what mentioned in above url.

So does that mean that I have to have port 22 open then in order to use SSH? Or do you just mean that port 22 has to be open on the server (not in the sshd_config file?

You need to open port 22 in the ec2 Security Group. Also need to open the same port on the EC2 instance's firewall.