Gitlab Troubles

I was trying to rest the the SSH key login features of Gitlab when I hit a snag. The problem resides in my setup, I am using a reverse proxy like all of us plebeians are since we cannot afford to have decent internet at all here in Australia and with our ever decreasing IPv4 space, I am lucky to have an IPv4 address at all.

Some ISP's are now placing people on NAT straight away, I knew the practice was common in mobile phones and in Asia. The total breaking of TCP/IP and the odd connection behaviour clients will have with double NAT.

Any case I just plainly resorted to just using other authentication methods, because to get it working required a bit of magical hackery (including double nat's), there is no low level port forward SSH reverse proxy like the is for HTTP, perhaps there should be. Having multiple SSH hosts that can be reached behind a singular SSH port that forwards the connection to the right host - not just the jump host.