My problem is that I can t push or fetch from GitLab However I can clone via HTTP or via SSH I get this error when I try to push Permission denied publickey fatal Could not read from remote repository From all the threads I ve looked here is what I have done Set up an SSH key on my computer and added the public key to GitLab Done the config --global for username and email Cloned via SSH and via HTTP to check if it would resolve the issue Done the ssh -T git gitlab com command If you have any insight about how to resolve my issue it would be greatly appreciated

I was facing this issue because of ssh-agent conflicts on Windows-10 If you are using Windows-10 as well then please go through my detailed solution to this here If you are not on windows-10 then please check if your ssh-agent is running correct private key is added to your ssh-agent correct public key is added to your github account You are able to clone so this step should be fine

Another issue that can cause this behaviour is when you have a setup with 2 possible HOME -locations I m using a PC where some of my documents are stored locally and some of them are stored on a network drive Some applications think C Users lt MyUserName gt is my home others think that U is the home Turns out ssh-keygen put my private key under C users lt MyUserName gt and that ssh -T and ssh -v also look there So everything seems to work fine except that git clone git push and others look for a key in U Which fails so I get the aforementioned error It took me an hour to find out but in the end the solution was simple I copied everything from C Users lt MyUserName gt ssh to U ssh

I had the same problems It has been fixed after I re-generate the ssh key inside ssh folder without naming it keep it as id rsa pub Then add it again to gitlab ssh key Everything working fine now

I found the solution in gitlab help To create a new SSH key pair 1 Open a terminal on Linux or macOS or Git Bash WSL on Windows 2 Generate a new ED25519 SSH key pair ssh-keygen -t ed25519 -C email example com 2 1 Or if you want to use RSA ssh-keygen -o -t rsa -b 4096 -C email example com 3 Next you will be prompted to input a file path to save your SSH key pair to use the suggested path by pressing Enter 4 Once the path is decided you will be prompted to input a password to secure your new SSH key pair It s a best practice to use a password but it s not required and you can skip creating it by pressing Enter twice 5 Copy your public SSH key to the clipboard by using one of the commands below depending on your Operating System macOS pbcopy lt ssh id ed25519 pub WSL GNU Linux requires the xclip package xclip -sel clip lt ssh id ed25519 pub Git Bash on Windows cat ssh id ed25519 pub clip 6 Navigating to SSH Keys and pasting your public key in the Key field 7 Click the Add key button I hope it can help some of you

I know I m answering this very late and even StackOverflow confirmed if I really want to answer I m answering because no one actually described the actual problem so wanted to share the same The Basics First understand that what is the remote here Remote is GitLab and your system is the local so when we talk about the remote origin whatever URL is set in your git remote -v output is your remote URL The Protocols Basically Git clone push pull works on two different protocols majorly there are others as well - HTTP protocol SSH protocol When you clone a repo or change the remote URL and use the HTTPs URL like https gitlab com wizpanda backend-app git then it uses the first protocol i e HTTP protocol While if you clone the repo or change the remote URL and uses the URL like git gitlab com wizpanda backend-app git then it uses the SSH protocol HTTP Protocol In this protocol every remote operation i e clone push amp pull uses the simple authentication i e username amp password of your remote GitLab in this case that means for every operation you have to type-in your username amp password which might be cumbersome So when you push pull clone GitLab GitHub authenticate you with your username amp password and it allows you to do the operation If you want to try this you can switch to HTTP URL by running the command git remote set-url origin lt http-git-url gt To avoid that case you can use the SSH protocol SSH Protocol A simple SSH connection works on public-private key pairs So in your case GitLab can t authenticate you because you are using SSH URL to communicate Now GitLab must know you in some way For that you have to create a public-private key-pair and give the public key to GitLab Now when you push pull clone with GitLab GIT SSH internally will by default offer your private key to GitLab and confirms your identity and then GitLab will allow you to perform the operation So I won t repeat the steps which are already given by Muhammad I ll repeat them theoretically Generate a key pair ssh-keygen -t rsa -b 2048 -C My Common SSH Key The generated key pair will be by default in ssh named id rsa pub public key amp id rsa private key You will store the public key to your GitLab account the same key can be used in multiple or any server accounts When you clone push pull GIT offers your private key GitLab matches the private key with your public key and allows you to perform Tips You should always create a strong rsa key with at least 2048 bytes So the command can be ssh-keygen -t rsa -b 2048 https gitlab com help ssh README generating-a-new-ssh-key-pair General thought Both the approach have their pros amp cons After I typed the above text I went to search more about this because I never read something about this I found this official doc https git-scm com book en v2 Git-on-the-Server-The-Protocols which tells more about this My point here is that by reading the error and giving a thought on the error you can make your own theory or understanding and then can match with some Google results to fix the issue

Two things mainly You must have id rsa pub and id rsa private keys in your ssh folder which should be in your home folder Create it if it isn t there put your keys It wouldn t work If you have named your key files differently Change the permission of the id rsa as chmod 400 ssh id rsa

Nothing worked for me on Windows 10 using Pageant as SSH agent except adding a enviroment variable to windows translated from german Windows 10 so the naming may differ Search for variables Open System Enviroment Variables Click Enviroment Variables button at the bottom Add a new key named GIT SSH and the value C Program Files PuTTY plink exe to the top section User Variables xxx And you re done All thanks go to Benjamin Bortels source https bortels io blog git-in-vs-code-unter-windows-richtig-einstellen

if you are in Linux or macox just try this in terminal ssh-add -l if it return nothing try this ssh-add it must create identity in ssh id rsa after retry ssh-add -l it must return your identity so after retry to clone it s must work NB don t forget to add your ssh key in your profile gitlab thanks

I had the same issue I resolved it by adding a new ssh key ssh-keygen -t ed25519 -C email example com Copy your public SSH key to the clipboard xclip -sel clip lt ssh id ed25519 pub in my case on Linux On gitlab go to settings gt ssh keys and past the new key

[git] Getting permission denied (public key) on gitlab

Step 1: Added a config file in ~/.ssh/config file which looks like

   User git
   Hostname gitlab.com
   IdentityFile ~/.ssh/id_rsa_gitlab
   TCPKeepAlive yes
   IdentitiesOnly yes

Step 2: Just clone the git repo WITHOUT sudo.
Documentation: https://gitlab.com/help/ssh/README#working-with-non-default-ssh-key-pair-paths

Examples related to git

• Does the target directory for a git clone have to match the repo name? • Git fatal: protocol 'https' is not supported • Git is not working after macOS Update (xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools) • git clone: Authentication failed for <URL> • destination path already exists and is not an empty directory • SSL_connect: SSL_ERROR_SYSCALL in connection to github.com:443 • GitLab remote: HTTP Basic: Access denied and fatal Authentication • How can I switch to another branch in git? • VS 2017 Git Local Commit DB.lock error on every commit • How to remove an unpushed outgoing commit in Visual Studio?

Examples related to ubuntu

• grep's at sign caught as whitespace • "E: Unable to locate package python-pip" on Ubuntu 18.04 • How to Install pip for python 3.7 on Ubuntu 18? • "Repository does not have a release file" error • ping: google.com: Temporary failure in name resolution • How to install JDK 11 under Ubuntu? • How to upgrade Python version to 3.7? • Issue in installing php7.2-mcrypt • Install Qt on Ubuntu • Failed to start mongod.service: Unit mongod.service not found

Examples related to ssh

• Starting ssh-agent on Windows 10 fails: "unable to start ssh-agent service, error :1058" • How to solve "sign_and_send_pubkey: signing failed: agent refused operation"? • key_load_public: invalid format • ssh connection refused on Raspberry Pi • Getting permission denied (public key) on gitlab • Verify host key with pysftp • Can't connect to Postgresql on port 5432 • Checkout Jenkins Pipeline Git SCM with credentials? • How to open remote files in sublime text 3 • how to setup ssh keys for jenkins to publish via ssh

Examples related to gitlab

• GitLab remote: HTTP Basic: Access denied and fatal Authentication • How can I switch to another branch in git? • HTTP Basic: Access denied fatal: Authentication failed • Getting permission denied (public key) on gitlab • Delete commit on gitlab • error: RPC failed; curl transfer closed with outstanding read data remaining • ssh : Permission denied (publickey,gssapi-with-mic) • Fix GitLab error: "you are not allowed to push code to protected branches on this project"? • Change Default branch in gitlab • How can I clone a private GitLab repository?