I'm trying to get around a hospital firewall.

I can SSH into my devbox on Port 443:

ssh -L 8080:devbox:443 root@devbox -p 443

But I can't actually get the devbox to load in my browser. When I go to localhost:8080 I get the following error:

SSH-2.0-OpenSSH_4.3 Protocol mismatch.

When I ssh -V I get the following:

devbox: OpenSSH_4.3p2, OpenSSL 0.9.8e-fips-rhel5 01 Jul 2008

local machine: OpenSSH_6.2p2, OSSLShim 0.9.8r 8 Dec 2011

I'm assuming that this difference is what's causing the protocol mismatch. Can anyone suggest how to resolve the mismatch?

closed as off-topic by kce, mdpc, Falcon Momot, Michael Hampton Aug 14 '14 at 20:30

This question appears to be off-topic. The users who voted to close gave this specific reason:

  • "Questions must be relevant to professional system administration. Server Fault is dedicated to professional system and network administrators. End user and enthusiast questions are off-topic (contact your system administrator or hire a professional to help you out). Please see the Help Center for more information." – kce, mdpc, Falcon Momot, Michael Hampton
If this question can be reworded to fit the rules in the help center, please edit the question.

  • You are asking the very people that administrator those firewalls how to circumnavigate them? Perhaps you should review what is on-topic here. If you need access to your development machine you should work with your operations people to make that happen. – kce Aug 13 '14 at 17:01
  • On what port is your https web server running on your devbox, if your SSH runs on port 443? – Tero Kilkanen Aug 13 '14 at 19:39

Thats..... strange, You're creating an ssh tunnel to port 443 on the remote machine (devbox) but you've clearly got sshd listening on port 443 (Which is https by default), so when you point your browser at localhost:8080, you understandably get the sshd server Whats more, its pretty impossible for you to have a webserver listening on port 443, given thats what sshd is listening on.

Perhaps you meant this:

ssh -L 8080:devbox:80 root@devbox -p 443
  • That works for http stuff, but not for https, which is what I need. Since I'm using 443 for sshd, does that mean it's impossible for me to access any https content? – jawns317 Aug 13 '14 at 16:46
  • Would a multiplexer like sslh work in this case? – jawns317 Aug 13 '14 at 16:51
  • > does that mean it's impossible for me to access any https content on port 443? Yes. Usually ssh would run on port 22 and https on port 443. However, you could run https on port 4443 (for example) – GeoSword Aug 14 '14 at 7:17

You are creating a tunnel to your sshd port. This gives you the error, when trying to do http to your ssh server.

Change your tunnel to point to the ip and port of your web server.

Not the answer you're looking for? Browse other questions tagged or ask your own question.