1. Question: I need to use https link
:: Of course the method on the third floor is possible, but the answer is not what you asked
:: The answer on the fourth floor is obviously that I didn’t even read the question clearly. Since I asked for a password, it’s obviously a private project
:: The answer on the first floor should be in the right direction. I haven't completely investigated it yet and suspect that it is still a https jump problem. Now I change the method of displaying the account name and password to log in and bring the account name into https://uid@urlpath. The value has been obtained (the difference is that the account number is different, and according to the analysis, it is believed that the email address will be converted to display the account number first. However, due to the https connection problem, it is estimated that this layer of login dialogue cannot be converted, so directly enter the real account)
1. Question: I need to use https link
:: Of course the method on the third floor is possible, but the answer is not what you asked
:: The answer on the fourth floor is obviously that I didn’t even read the question clearly. Since I asked for a password, it’s obviously a private project
:: The answer on the first floor should be in the right direction. I haven't completely investigated it yet and suspect that it is still a https jump problem. Now I change the method of displaying the account name and password to log in and bring the account name into https://uid@urlpath. The value has been obtained (the difference is that the account number is different, and according to the analysis, it is believed that the email address will be converted to display the account number first. However, due to the https connection problem, it is estimated that this layer of login dialogue cannot be converted, so directly enter the real account)
I have encountered a similar problem recently. I guess it is a problem with the curl library. Can you try installing the curl openssl dev library?
Public or private repo, if it is private, the clone address is different.
First add the ssh key to github, and then try sudo clone.
Check method to see if it is private
2. git version. Check your git version. https must be git version 1.7 or above. 401 error occurs in 1.6
You can try git clone some publice projects. If successful, determine whether it is a problem with your own project or with git itself
Clone does not require a password, it is just a copy command
You only need to enter your password when you push
I have encountered this problem. As everyone from LS said, it is probably a version issue.
I just uninstalled git and compiled and installed the latest version
PS Please
git clone git@github.com:git/git.git
uninstall the original git first. . .http://blog.csdn.net/zhaozhi406/article/details/30506153 User name and password to create a file
Problem solved