Well have you change anything since it worked last? Anything at all? I noticed that you have the port set to 443. This is fine, but only as long as there's actually a server listening on that port.
Well I don't think I changed anything..
The truth is, that it was 3 o'clock in the morning and I was drunk when I was messing with it - pleased with the fact that I could at least get a connection, I went to bed.
This morning I was trying to get it back on and it didn't work..
//Edit:
So after doing some further testing (I am spending way too much time on this - that's what I hate (and love) about computers... it is somehow working. The problem was, that I had to completely deload the ssh client on the server first. So:
1. no matter what's happening with the firewall, when using port 443 it won't even start -
"the specified address is already in use".2. when the firewall is completely turned off I can go through whatever port
3. when it's on, I have to make an inbound rule for the port I want to run it through.
4. I found some pre-defined rules for ports 80 and 443 that I allowed, but it still didn't work (I had to manually create a rule for port 80)
I created a tunnel for port 443 and RDP - so I was able to remotely connect to the server via 127.0.0.1:443 - which is what I want and need.
Tomorrow I will try to set this up in a real life environment...
I am still not sure why it doesn't allow me to get a SSH through port 443 or why it needs port 80 to be open (when that should be open by default I guess).
Thanks for help lucid.