Cannot push to Git repository on Bitbucket

Question

I created a new repository and I m running into a strange error  I ve used Git before on Bitbucket but I just reformatted and now I can t seem to get Git to work   After doing a commit  I had to add my email and name to the globals  but then it committed just fine    When I try to use the command  git push origin master   it doesn t work  I get this message     git push origin master Permission denied  publickey   fatal  Could not read from remote repository   Please make sure you have the correct access rights and the repository exists    I m at a loss here   My friend whom I m sharing this repository with  accessed it fine and pushed to it just fine  but I can t seem to get it to work

User · Answer

I got this very same error for one repository - suddenly, all other ones were and still work fine when I'm trying to push commits. The problem appeared to be with the SSH key (as you already know from the previous comments) - on bitbucket go to View Profile then click Manage Account.

On the left hand side click on the SSH Keys then add the one that you have on your system under ~/.ssh/ directory.

If you don't have one generated yet - use the instructions from one of the posts, but make sure that you either use the default id_dsa.pub file or custom named one, with later requiring the -i option with the path to the key when you connect i.e.

ssh -i ~/.ssh/customkeyname username@ip_address

Once you've added your local key to your account at bitbucket, you'll be able to start interacting with your repository.

User · Answer

Git has changed some of its repo instructions - check that you have connected your local repo to the Git cloud - check each of these steps to see if you have missed any  Git documentation https   docs github com en free-pro-team latest github authenticating-to-github connecting-to-github-with-ssh  if you prefer following documentation - it is far more detailed and worth reading to understand why the steps below have been summarised  My Git Checklist -  The master branch has changed to main If you have initialised your repo and want to start from scratch  un-track git with  rm -rf  git which recursively removes git Check you re not using  quot Apple Git quot   Type which git it should say  usr local bin git - if you are install git with Homebrew  brew install git Configure your name and email address for commits  be sure to use the email address you have registered with Github     git config --global user name  quot Your Name quot   git config --global user email  quot you example com quot    Configure git to track case changes in file names    git config --global core ignorecase false  If you have made a mistake you can update the file  ls -a to locate file then  open  gitignore and edit it  save and close   Link your local to the repo with an SSH key  SSH keys are a way to identify trusted computers  without involving passwords  Steps to generate a new key   Generate a new SSH key by typing ssh-keygen -t rsa -C  quot your email example com quot  SAVE THE KEY You ll be prompted for a file to save the key  and a passphrase  Press enter for both steps leaving both options blank  default name  and no passphrase   Add your new key to the ssh-agent  ssh-add    ssh id rsa Add your SSH key to GitHub by logging into Github  visiting Account settings and clicking SSH keys  Click Add SSH key  You can also find it by clicking your profile image and the edit key under it in the left nav   Copy your key to the clipboard with the terminal command  pbcopy  lt     ssh id rsa pub  In the Title field put something that identifies your machine  like YOUR NAME s MacBook Air  In the Key field just hit cmd   V to paste the key that you created earlier - do not add or remove and characters or whitespace to the key  Click Add key and check everything works in the terminal by typing  ssh -T git github com  You should see the following message  Hi YOUR NAME  You ve successfully authenticated  but GitHub does not provide shell access     Now that your local machine is connected to the cloud you can create a repo online or on your local machine  Git has changed the name master for a branch main  When linking repos it is easier to use the HTTPS key rather than the SSH key  While you need the SSH to link the repos initially to avoid the error in the question  Permission denied  publickey   fatal  Could not read from remote repository   Please make sure you have the correct access rights and the repository exists   Follow the steps you now get on your repo - GitHub has added an additional step to create a branch  time of writing Oct 2020    to create a new repository on the command line echo  quot   testing-with-jest quot   gt  gt  README md git init git add README md git commit -m  quot first commit quot  git branch -M main git remote add origin      use HTTPS url not SSH  git push -u origin main  to push an existing repository from the command line git remote add origin  use HTTPS url not SSH  git branch -M main git push -u origin main   If you get it wrong you can always start all over by removing the initialisation from the git folder in your local machine  rm -rf  git and start afresh - but it is useful to check first that none of the steps above are missed and always the best source of truth is the documentation - even if it takes longer to read and understand

User · Answer

Just need config file under    ssh directory ref   https   confluence atlassian com bitbucket set-up-ssh-for-git-728138079 html add bellow configuration in config file  Host bitbucket org  IdentityFile    ssh  lt privatekeyfile gt

User · Answer

Get the ssh done as in the Atlassian tutorial and make sure the private key is being pasted in the profile  not in the repository

User · Answer

I had this issue and I thought I was crazy  I have been using SSH for 20 years  and git over SSH since 2012    but why couldn t I fetch my bitbucket repository on my home computer   well  I have two bitbucket accounts and had 4 SSH keys loaded inside my agent  even if my  ssh config was configured to use the right key   when ssh was initializing the connection  it was using them in order loaded into the agent  so I was getting logged into my personal bitbucket account   then getting a Forbidden error trying to fetch the repo  makes sense   I unloaded the key from the agent  ssh-add -d    ssh personal rsa  then I could fetch the repos       Later I found out I can force it to use the specified identity only   Host bitbucket org-user2      HostName bitbucket org      User git      IdentityFile    ssh user2      IdentitiesOnly yes   I didn t know about that last option IdentitiesOnly  from the bitbucket documentation itself  https   blog developer atlassian com different-ssh-keys-multiple-bitbucket-accounts

User · Answer

Two small clarifications that might save someone the confusion I went through  1 - Connection URLs differ for HTTPS and SSH When connecting via https  you use https   your account name bitbucket org owner-account repo-name git  however when connecting via SSH  the account name is always  quot git quot  ssh   git bitbucket org owner-account repo-name git  Attempting to connect to SSH with your account name in front will lead to the error the original poster received  This is how you can do the test connecting to git   then mistakenly try with your username and see an error  2 - SSH Keys via team accounts will be deprecated in 2017 If you are setting up SSH keys on team accounts  they recommend switching them to personal accounts  A useful tip to avoid e

User · Answer

Just try   git remote add origin  lt HTTP URL gt

User · Answer

I solved this by removing the remote using command   git remote remove origin   and then tried to add remote using https url instead of ssh  git remote add origin httpsUrl   It asks for github credentials  Enter credentials and then try pushing to git using   git push origin master

User · Answer

I am using macOS and although i had setup my public key in bitbucket the next time i tried to push i got  repository access denied  fatal  Could not read from remote repository  Please make sure you have the correct access rights and the repository exists   What i had to do was Step 2  Add the key to the ssh-agent as described in Bitbucket SSH keys setup guide and especially the 3rd step    macOS only  So that your computer remembers your password each time it restarts  open  or create  the    ssh config file and add these lines to the file  Host   UseKeychain yes  Hope it helps a mac user with the same issue

User · Answer

This error also shows up when the repository does not exist  I tried all the answers until I saw the repo name was missing a dash

User · Answer

This error also occurs if you forgot adding the private key to ssh-agent  Do this with   ssh-add    ssh id rsa

User · Answer

I found the git command line didnt fancy my pageant generated keys  Windows 10    See my answer on Serverfault

User · Answer

Writing this for those just getting started with Git and BitBucket on Windows  amp  who are not as familiar with Bash  since this is both a common issue and a high ranking Google result when searching for the error message within the question    For those who don t mind HTTPS and who are looking for a quick fix  scroll to the bottom of this answer for instructions under FOR THE LAZY  For those looking to solve the actual problem  follow the instructions below   Fixing the SSH issue as fast as possible  This is a set of instructions derived from the URL linked to by VonC   It was modified to be as resilient and succinct as possible    Don t type the   or any lines that do not begin with    the   means this is something you type into GitBash   Open GitBash   Set your global info if you haven t already     git config --global user name  Your Name    git config --global user email  you example com    Check for OpenSSH     ssh -v localhost OpenSSH 4 6p1  OpenSSL      See something like that    Yes  Continue  No  Skip to the FOR THE LAZY section or follow the linked article from VonC    See if you have generated the keys already     ls -a    ssh id     If there are two files  you can skip the next step     ssh-keygen   Leave everything as the defaults  enter a passphrase   You should now see results with this command     ls -a    ssh id     Check for an existing config file     ls -a    ssh config   If you get a result  check this file for erroneous information   If no file exists  do the following     echo  Host bitbucket org   gt  gt     ssh config   echo   IdentityFile    ssh id rsa   gt  gt     ssh config   Confirm the contents     cat    ssh config  Host bitbucket org  IdentityFile    ssh id rsa    The single space before  IdentityFile  is required    Check you are starting the SSH agent every time you run GitBash     cat    bashrc    If you see a function called start agent  this step has already been completed  If no file  continue  If there is a file that does not contain this function  you re in a sticky situation   It s probably safe to append to it  using the instructions below  but it may not be  If unsure  make a backup of your  bashrc before following the instructions below or skip ahead to FOR THE LAZY section    Enter the following into GitBash to create your  bashrc file     echo  SSH ENV  HOME  ssh environment   gt  gt     bashrc   echo     gt  gt     bashrc   echo    start the ssh-agent   gt  gt     bashrc   echo  function start agent     gt  gt     bashrc   echo      echo   Initializing new SSH agent        gt  gt     bashrc   echo        spawn ssh-agent   gt  gt     bashrc   echo       usr bin ssh-agent   sed  s  echo  echo    gt       SSH ENV      gt  gt     bashrc   echo      echo succeeded   gt  gt     bashrc   echo      chmod 600      SSH ENV      gt  gt     bashrc   echo             SSH ENV     gt   dev null   gt  gt     bashrc   echo       usr bin ssh-add   gt  gt     bashrc   echo      gt  gt     bashrc   echo     gt  gt     bashrc   echo  if   -f      SSH ENV       then   gt  gt     bashrc   echo              SSH ENV     gt   dev null   gt  gt     bashrc   echo       ps -ef   grep    SSH AGENT PID    grep ssh-agent   gt   dev null        gt  gt     bashrc   echo          start agent    gt  gt     bashrc   echo          gt  gt     bashrc   echo  else   gt  gt     bashrc   echo      start agent    gt  gt     bashrc   echo  fi   gt  gt     bashrc   Verify the file was created successfully  yours should only differ where  yourusername  appears      cat    bashrc SSH ENV  c Users yourusername  ssh environment    start the ssh-agent function start agent       echo  Initializing new SSH agent           spawn ssh-agent      usr bin ssh-agent   sed  s  echo  echo    gt     SSH ENV       echo succeeded     chmod 600    SSH ENV            SSH ENV    gt   dev null      usr bin ssh-add    if   -f    SSH ENV      then           SSH ENV    gt   dev null      ps -ef   grep   SSH AGENT PID    grep ssh-agent   gt   dev null              start agent        else     start agent  fi    Close GitBash and re-open it  You should be asked for your passphrase  for the SSH file you generated earlier   If no prompt  you either did not set a passphrase or GitBash isn t running the  bashrc script  which would be odd so consider reviewing the contents of it    If you are running this on a Mac OS X    bashrc isn t executed by default -  bash profile is  To fix this  put this snippet in your  bash profile     -s    bashrc     amp  amp  source    bashrc   If you didn t enter a passphrase  you would have seen something like this when starting GitBash   Initializing new SSH agent    succeeded Identity added   c Users yourusername  ssh id rsa   c Users yourusername  ssh id rsa    And the following should return results     ssh-add -l   However  if you get the following from ssh-add -l   Could not open a connection to your authentication agent    It didn t spawn the SSH agent and your  bashrc is likely the cause   If  when starting GitBash  you see this   Initializing new SSH agent    sh exe     No such file or directory   That means you forgot to escape the   with a   when echoing to the file  ie  the variables were expanded    Re-create your  bashrc to resolve this   Verify the agent is running and your keys have been added     ssh-add -l   Should return something similar to this   2048 0f 37 21 af 1b 31 d5 cd 65 58 b2 68 4a ba a2 46  Users yourusername  ssh id rsa  RSA    Run the following command to get your public key     cat    ssh id rsa pub    it should return something starting with  ssh-rsa           Click the GitBash window icon Click Edit Click Mark Highlight the public key using your mouse  including the leading ssh-rsa bit and the trailing    youremail yourdomain com bit  Right-click the window  performs a copy  Paste your public key into Notepad  Delete all the newlines such that it is only a single line  Press CTRL A then CTRL C to copy the public key again to your clipboard    Configure your private key with BitBucket by performing the following steps    Open your browser and navigate to the BitBucket org site Login to BitBucket org Click your avatar  top-right  Click Manage Account Click SSH Keys  under Security on the left-hand menu  Click Add Key Enter Global Public Key for the Label Paste the public key you copied from Notepad   A Global Public Key entry should now be visible in your list of keys    Return to GitBash cd into the directory containing your project Change your origin to the SSH variation  it will not be if you ran the FOR THE LAZY steps    Check your remotes     git remote -v   Switch to the SSH url     git remote set-url origin git bitbucket org youraccount yourproject git   Check things are in working order     git remote show origin   You should see something like this   Warning  Permanently added the RSA host key for IP address       to the list of known hosts    remote origin   Fetch URL  git bitbucket org youruser yourproject git   Push  URL  git bitbucket org youruser yourproject git   HEAD branch  master   Remote branch      master tracked   Local ref configured for  git push       master pushes to master  fast-forwardable    DONE   You can opt to use HTTPS instead of SSH   It will require you to type your password during remote operations  it s cached temporarily after you type it once    Here is how you can configure HTTPS   FOR THE LAZY  You should fix the SSH issue as described by VonC  however  if you re in a rush to commit and don t have the tools time knowledge to generate a new public key right now  set your origin to the HTTPS alternative    gt  https   accountname bitbucket org accountname reponame git   Using a GUI tool such as TortoiseGit or command line tools   Here is the documentation of this alternative origin URL   Command line to add an origin if one does not exist   git remote add origin https   accountname bitbucket org accountname reponame git   Command line to change an existing origin   git remote set-url origin https   accountname bitbucket org accountname reponame git   NOTE  your account name is not your email   You may also want to set your global info   git config --global user name  Your Name  git config --global user email  you example com    Then try your push again  no need to commit again   git push origin master

User · Answer

This is probably caused by having multiple SSH keys in SSH agent  and or BitBucket   Check Atlassian documentation for the workaround for this

User · Answer

Reformatted means you probably deleted your public and private ssh keys  in    ssh    You need to regenerate them and publish your public ssh key on your BitBucket profile  as documented in  Use the SSH protocol with Bitbucket   following  Set up SSH for Git with GitBash    Accounts- Manage Accounts- SSH Keys     Then      Images from  Integrating Mercurial BitBucket with JetBrains software

User · Answer

I found the solution that worked best for me was breaking up the push into smaller chunks   and removing the large screenshot image files  10mb   from the commits  Security wasnt an issue in the end more about limits of bin files

User · Answer

I got this error     Connection to bitbucket org closed by remote host    fatal  Could not read from remote repository    Please make sure you have the correct access rights    Then i tried      git config --global user email  you example com    worked without quotes

User · Answer

I had the same problem  My SSH keys were set correctly   I fixed this problem like this   After creating new project in Bitbucket  use clone  Enter cloning command in terminal and it should clone empty project to your computer  After that you can copy your files to this directory and start committing and pushing to bitbucket

User · Answer

If you are using SourceTree  I m using 2 4 1   I found a simpler way to generate an SSH key and add it to my Bitbucket settings  This solved the problem for me    In SourceTree  go to Preferences  Go to the Accounts tab and select your account  There should be an option to generate and copy an SSH key to clipboard  Once you have copied that  go to Bitbucket in your browser  Go to  avatar  -  Bitbucket settings  Go to SSH keys  Click Add key Paste in the key you copied    I received a confirmation email from Bitbucket that an SSH key had been added to my account   For reference  on macOS  using Terminal  you can use the following command to see the keys generated for your device  This is where the key you generated is stored   ls -la    ssh   As others have stated  this documentation helped me  Use the SSH protocol with Bitbucket Cloud

User · Answer

This might not be the case for everyone but I still make an answer here in case someone is having the same cause  Basically I have two Bitbucket accounts  each have two different public keys  By running ssh -Tv bitbucket org I managed to see that my laptop is sending incorrect key  but since both public keys are registered in bitbucket  the key is still approved  then since the key is linked to another account which does not have access to the repo I m pushing  the push is rejected   So I followed this guide and my issue is gone  https   blog developer atlassian com different-ssh-keys-multiple-bitbucket-accounts

User · Answer

For errors    error  repository access denied   access via a deployment key is read-only  fatal  Could not read from remote repository  Please make sure you have the correct access rights and the repository exists    error  fatal  Could not read from remote repository    error  fatal  Unable to find remote helper for  https    I solved following this steps   First install this dependencies     yum install expat expat-devel openssl openssl-devel   Then remove git     yum remove git git-all   Now Build and install Git on last version  in this case     wget https   github com git git archive v2 13 0 tar gz   tar zxf v 2 13 0 tar gz   cd git-2 13 0    Then for the configure     make configure     configure --with-expat --with-openssl   And finally install like this     make    make install install-doc install-html install-info   that  s it  now configure your repo with https     git remote add origin https   github com  user   repo  git   Verify new remote   git remote -v   if you have configured an ssh key in your remote server you have to delete it

[git] Cannot push to Git repository on Bitbucket

Examples related to git

Examples related to bitbucket

Examples related to git-bash