nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bitbucket Git Submodules with SSH Keys and valid permissions are NOT cloning

Bartosz Solowiej

I have a valid id_rsa.pub ssh-key copied into my Bitbucket user settings. I can clone any top-level repo that I have access to.

I can also validate that my id_rsa.pub works by running:

ssh -vT git@bitbucket.org
[...]
Authenticated to bitbucket.org ([104.192.143.2]:22).
debug1: channel 0: new [client-session]
debug1: Entering interactive session.
debug1: pledge: network
debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
logged in as **REDACTED**.

BUT when I clone a top-level repo with submodules and run:

git submodule update --init --recursive"

# I see many "Permission denied (publickey") messages to repos I also have permission to

Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I can clone my submodules over ssh individually, NO PROBLEM. Just when the top level repo attempts to update all the submodules, it fails.

What is going on?

((( I do not want to use https for submodules. )))

Accepted answers

All comments

Ana Retamal

Hi Bartosz! Are you still experiencing this issue? If you are, please give us more info so we can continue helping you:

- Are you using Bitbucket Server or Cloud?

- Where are you cloning the repositories from? Where are you cloning them to?

Best regards,

Ana

unknown

I'm not the reporter but I have this issue. I'm using bitbucket cloud and cloning repositories to the my local e: drive.

git version 2.16.2.windows.1

cmd line: git clone --recurse-submodules git@bitbucket.org:orgname/reponame.git

unknown

Solved it, if anyone else comes looking make sure your ssh key does not have a passphrase.

Paul Russell_6fqib9

Surely having a passphrase on an ssh key is considered best practice.

I don't think this is the genuine root cause of this issue.

Pelle van der Heide

Found this too, make sure you connect to the submodule repo with the right user (git@bitbucket.org)

When no username is given ssh uses the current user, who has no permissions on bitbucket.org

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

bitbucket

git

submodule

ssh-key