<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=371845) </details> <!--IssueSummary end--> Link the doc and describe what is wrong with it. The document is here https://gitlab.cern.ch/help/user/ssh.md One common use case for gitlab is working on a remote server. The doc on ssh is critically lacking in this regard. This command did not work for me no matter what I tried. ssh git@gitlab.cern.ch -T After nearly a 90 minutes of pulling my hair out because I followed the instructions exactly, generating multiple (and multiple types of) ssh keys, I finally found the following command, from this page https://hsf-training.github.io/analysis-essentials/git/07-gitlab.html ssh git@gitlab.cern.ch -T -p 7999 It works perfectly and I have no problems now. In hindsight it's an obvious thing to do, but I am not a cryptographer, a network specialist, or a computer scientist really in any regard. But for someone who is, hopefully the person responsible for writing the help document, it would be so simple to add a note or a line that says "hey, do this if you're working from a remote connection instead of your laptop." <!-- Don't edit below this line -->