Translated from 日本語 • View original I was living a comfortable Git life with TortoiseGit and GitHub, but one day I suddenly couldn't pull.
It seems that communication with GitHub via port 22 is no longer possible.
Why?
Speaking of number 22, it is an SSH port. Since the server on AWS is also ssh, the internal network
It is unlikely that it is closed somewhere. I wonder if they were banned from GitHub?
Even if I am a paid plan user, is that possible? ?
In the end, although the cause was unknown, we responded by changing the environment to communicate via port 443.
TortoiseGit and the Git client are installed assumptions.
The installation method is also well organized for:
Steps to Translate TortoiseGit to Japanese\ - Switch
ssh clients
Right-click to open the context menu and open TortoiseGit settings from there.
Select the network in the left pane and change the ssh client displayed in the right pane if it is not:
C:\Program Files (x86)\Git\bin\ssh.exe
- Recreate the key
If you're using TortoiseGit, you're probably setting up a TortoisePlink.exe that would be standard for your SSH client
It seems that the passphrase is automatically set on the certificate and cannot be reused by other ssh clients, so I will recreate it.
$ ssh-keygen -t rsa -C "email address"
your public key on GitHub
Go to the GitHub site and copy and paste the contents of the public key (*.pub) you created earlier.
- Create an SSH configuration file
Create the following file:
C:\Users\[Users]\.ssh\config
Inside
Modify the key path appropriately.
You should now be able to interact with GitHub via port 443.
Try it.
Reference: How to push to github.com even if the SSH port does not pass through