Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

submodule update fails with ssh, but clone works


I am able to clone a repository with ssh just fine.

git clone

However, when this same repo is included as a submodule in another project, I get a Permission Denied (public key) error.

Here is the exact output I get 

$ git submodule update
Cloning into '/Users/me/code/my-project/utils'... Permission denied (publickey).
fatal: Could not read from remote repository.
Please make sure you have the correct access rights
and the repository exists.
fatal: clone of 'ssh://' into submodule path '/Users/me/code/my-project/utils' failed
Failed to clone 'utils'.

I want to re-iterate that I definitely have access to the repository and am able to clone the repository via ssh without any problems. This ONLY happens when the repository is included as a submodule in another project.

This is the content of my .gitmodules file
[submodule "utils"]
= utils
url = ssh://

I've tried everything I can think of.

  • Deleted all ssh keys
  • Regenerated keys (and added to Bitbucket account)
  • I've run ssh -T (it works)

I am on macOS Monterey (12.1).
git version 2.32.0 (Apple Git-132)

I followed the ssh setup instructions multiple times.

1 answer

1 accepted

1 vote
Answer accepted

I found out that I needed to specify the user for the submodule command.

There are two ways to do this (maybe more?)


The First way: specify the user in the url 

Change the value of the url field in the .gitmodules so it includes the username

url = ssh://


The Second Way: specify the user in ~/.ssh/config

    User git

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,495 views 3 10
Read article

Atlassian Community Events