I'm no longer able to log into my Linode web server from work. I can still log into the server from home with no issues. I've opened up my '/var/log/auth.log' file and this is what I get when the work logins fail:

Jan 10 10:27:30 bender sshd[3196]: fatal: Write failed: Connection reset by peer [preauth]
Jan 10 10:27:32 bender sshd[3198]: fatal: Write failed: Connection reset by peer [preauth]
Jan 10 10:27:33 bender sshd[3200]: fatal: Write failed: Connection reset by peer [preauth]
Jan 10 10:27:35 bender sshd[3202]: fatal: Write failed: Connection reset by peer [preauth]
Jan 10 10:27:36 bender sshd[3204]: fatal: Write failed: Connection reset by peer [preauth]
Jan 10 10:27:37 bender sshd[3206]: fatal: Write failed: Connection reset by peer [preauth]
Jan 10 10:27:39 bender sshd[3208]: fatal: Write failed: Connection reset by peer [preauth]
Jan 10 10:27:40 bender sshd[3210]: fatal: Read from socket failed: Connection reset by peer [preauth]
Jan 10 10:27:41 bender sshd[3212]: fatal: Write failed: Connection reset by peer [preauth]
Jan 10 10:27:43 bender sshd[3214]: fatal: Write failed: Connection reset by peer [preauth]

This is multiple attempts; I tried to have the errors stand-out in the log file.

My Google-foo has failed and I don't really know where to go from here. Any ideas?

I'm running:
Ubuntu 12.04.1 LTS (GNU/Linux 3.6.5-linode47 i686)

Let me know if you need any further information about the system.

Thank you!

I just had a chat with our IT team. They were blocking secure connections. Doh!

Thanks anyways!

If they simply block port 22, you can configure SSH on your Linode to use port 443 instead. Port 443 is expected to have encrypted data, as it is used for HTTPS to banks and such. This worked for me a while back. If they inspect the packets to see if you are using the SSH protocol and block those, as later happened for me as well, of course it won't work.

In such cases you can use corkscrew for SSH over HTTP:

http://en.wikipedia.org/wiki/Corkscrew_%28program%29

James

Mmmmmm. Love it!

_________________
/ Peter

I wrote a TCP over HTTP proxy years ago, the big question is does Corkscrew support communicating solely over GET/POST, or does it require CONNECT, which is commonly disabled on proxies?

My work in that area was limited in that I had the restriction (due to who I was doing the work for) that the server side had to run on port 80 with an existing web server already on port 80. Basically, I had to work through the existing webserver. I ended up implementing both the client and server side in PHP. Downstream was good, because I could have the client do a never-ending GET, and that worked, but the upstream direction didn't work so well, because PHP refused to give me access to the POST until the client had finished, so I had to keep making periodic POST requests to actually read the data.