![]() I am using Ubuntu so the steps are for Ubuntu. Creating SSH keys (if you don't have it already) If you don't have it, create it using the next section else jump to the section after this one. If you are using Windows or macOS, you should take a hint and check how to do the same on your operating system.įirst check if you already have SSH keys: ls ~/.ssh/id_rsa.pub I am using Linux so the steps are best followed on Linux. In other words, to push a code from your local system to your remote GitLab repository, you must create an SSH key-pair and add the public key to your GitLab profile. GitLab has changed its policy and it now expects you to use your own SSH key to authenticate with your GitLab repository. Now, should it not be automatically using HTTPS? No! Not anymore. It expects to have a secure connection between your system and your repository. Why do I say that? Because your GitLab repository is using HTTPS. The main line that gives some clue about the root cause of this error is this one: remote: HTTP Basic: Access denied Handling "remote: HTTP Basic: Access denied" Error With GitLab If you are facing a similar issue, let me show you how to fix this error. ![]() Here's what the error looked like: git push -u origin master It gave me a fatal error saying "Authentical failed for xyz repository". I created a new repository on the GitLab web interface and I went on to push the directory I had on my personal system.Įverything was fine until I tried to push the code to remote repository on GitHub. So, the other day I thought of using my long-forgotten GitLab account for storing and tracking all the customization I make to the Linux Handbook website.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |