Message "The requested URL returned error: 401" Is Displayed
Symptom
When a user attempts to clone code using HTTPS in CentOS, the message The requested URL returned error: 401 is displayed.
Analysis
An old Git version is installed in CentOS.
Solution
Run git --version to check the Git version. CentOS 6.5 usually has the Git 1.7.1 in-built.
- Uninstall the in-built Git 1.7.1.
# yum remove git
- Download the latest version from the Git website and add Git to the environment variables.
# wget https://github.com/git/git/archive/version.tar.gz # tar zxvf version.tar.gz # cd git-version # make configure # ./configure --prefix=/usr/local/git --with-iconv=/usr/local/libiconv # make all doc # make install install-doc install-html # echo "export PATH=$PATH:/usr/local/git/bin" >> /etc/bashrc # source /etc/bashrc
Troubleshooting FAQs
- Private Key Is Lost
- SSH Key Already Exits
- Git Keeps Asking for Passphrase During Code Clone via SSH
- Password Incorrect During Code Clone via HTTPS
- Committed Files Cannot Be Found in the Cloud Repository
- Message "pathspec XXX did not match any files" Is Displayed
- Message "Transport Error: cannot get remote repository refs. XXX.git: cannot open git-upload-pack" Is Displayed
- Message "syntax error near unexpected token `newline'" Is Displayed
- Message "unable to auto-detect email address" Is Displayed
- Message "fatal:Authentication failed" Is Displayed
- Message "'origin' does not appear to be a git repository" Is Displayed
- Message "You are not allowed to push code to protected branches on this project" is Displayed
- Message "Not a git repository" Is Displayed
- Message "src refspec master does not match any" Is Displayed
- Message "destination path 'XXX' already exists and is not an empty directory" Is Displayed
- Message "The requested URL returned error: 401" Is Displayed
- Code Push Fails
- Code Pull Fails
- Message "fatal: refusing to merge unrelated histories" Is Displayed
- Message "SSL certificate problem" Is Displayed
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
more