112 Search results for "ssh"

and proxy servers. When running remote Git commands or SSH, your connection might time out: $ ssh -vT git@github.com > OpenSSH_8.1p1, LibreSSL 2.7.3

open a terminal and type the ssh command. Use the -i flag to provide the path to the key you want to check: $ ssh -T -ai ~/.ssh/id_rsa git@github.com # Connect

API or the command line, you'll authenticate using a token, application, or SSH key. For more information, see "About authentication to GitHub."

captcha verification. Switching cloning methods Switching from cloning via SSH to cloning via HTTPS, or vice versa may improve connectivity. For more information

credentials will cause authentication to fail. Use SSH instead If you've previously set up SSH keys, you can use the SSH clone URL instead of HTTPS. For more information

As a security precaution, SSH keeps track of which hosts it has previously seen. This error means that the server to which you're connecting presented

HTTPS remote URL has some advantages compared with using SSH. It's easier to set up than SSH, and usually works through strict firewalls and proxies. However

min/ SSH into your target GitHub Enterprise Server instance. For more information, see "Accessing the administrative shell (SSH)." ssh -p 122

Stop a codespace Delete a codespace Rename a codespace Rebuild a codespace SSH into a codespace Open a codespace in Visual Studio Code Open a codespace in

Enterprise Server source. The best way to do this is to verify that you can SSH into the instance. Generate an access token with the repo and admin:org scopes