Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Cannot Commit; Any ideas on how to resolve?

ddspell
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 30, 2024

I created a new repo.


I successfully cloned via ssh.
Made some changes locally.
Committed them.
Tried to push, but it failed.

I've done some troubleshooting, but I'm not sure how to resolve.

I did this...
GIT_SSH_COMMAND="ssh -vvv" git push

<snip>

debug1: Server accepts key

At this point, all good.

debug1: Sending command: git-receive-pack 'me/scripts.git'
debug2: channel 0: request exec confirm 1
debug3: send packet: type 98
SSH_MSG_CHANNEL_REQUEST

debug2: channel_input_open_confirmation: channel 0: callback done
debug2: channel 0: open confirm rwindow 2097152 rmax 32768
debug3: receive packet: type 99
SSH_MSG_CHANNEL_SUCCESS

debug2: channel_input_status_confirm: type 99 id 0
debug2: exec request accepted on channel 0
debug2: channel 0: rcvd ext data 13
debug3: receive packet: type 98
SSH_MSG_CHANNEL_REQUEST

debug1: client_input_channel_req: channel 0 rtype exit-status reply 0
debug3: receive packet: type 96
SSH_MSG_CHANNEL_EOF

debug2: channel 0: rcvd eof
debug2: channel 0: output open -> drain
debug3: receive packet: type 97
SSH_MSG_CHANNEL_CLOSE

debug2: channel 0: rcvd close
debug2: channel 0: chan_shutdown_read (i0 o1 sock -1 wfd 4 efd 6 [write])
debug2: channel 0: input open -> closed
debug3: channel 0: will not send data after close
debug2: channel 0: obuf_empty delayed efd 6/(13)
Unauthorized

Not sure why I'm unauthorized.
I own the repo.

Any ideas how to resolve?

1 answer

1 accepted

1 vote
Answer accepted
Patrik S
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
September 3, 2024

Hey @ddspell ,

and welcome to the Community!

Checking internally for your account I've noticed that you don't have any SSH keys added to your account. This means the key you're using was probably added directly to the repository or to the project that repository belongs to.

SSH keys added to the repository or project (known as Access Keys) only provide read access to the repository (learn more on Difference between Repository, Project and Workspace Access keys). This would explain why you were able to clone successfully, but the push was not authorized. 

In that case, you'd have to add your SSH key to your user profile instead by navigating to your Personal Bitbucket Settings > SSH Keys.

The same key cannot be added simultaneously as an access key and a user key. If you want to add the same key to your user profile, you'd first need to remove it as the access key on the repo/project level.

I hope that helps! Let me know in case you have any questions.

Thank you, @ddspell !

Patrik S

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
TAGS
AUG Leaders

Atlassian Community Events