Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How do I run go get on a private repo

I have two Go repos. One called foo - which is a package, and one called bar - which pulls in foo as a dependency.

Because of Go's archaic (a more appropriate description is probably against community guidelines) package management system, you have to specify the full domain name of a package that you pull in - so in my file ``, I have:

import ""

I initially had an issue where I was getting this output

go get reading 403 Forbidden
server response: Access denied. You must have write or admin access.

After looking up the output, several sites told me to run the following to force a connection via SSH:

git config --global url."".insteadOf ""

When I run `go get` to pull in the foo dependency, I now get a slightly different error:

go: downloading v0.1.0
go get verifying module: reading 410 Gone
server response:
not found: reading 403 Forbidden

It does seem to be finding and accessing my foo repo because the latest tag in it is 0.1.0, but the go get command is still failing due to a 403. I know for certain that I don't lack permissions on my SSH key, because I use that SSH key to push to/pull from Bitbucket all the time.



1 answer

1 accepted

3 votes
Answer accepted

Resolved. I had to restart the SSH agent in order for the .gitconfig change to take effect.

I was then faced with the following issue:

main.go:5:2: verifying module: reading 410 Gone

This is something that I'd addressed before - for those facing the same issue,  it's just a matter of exporting a variable to prevent Go from looking up the repo in - as follows:

export GOPRIVATE=""

Suggest an answer

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

Calling any interview participants for Bitbucket Data Center

Hi everyone,  We are looking to learn more about development teams’ workflows and pain points, especially around DevOps, integrations, administration, scale, security, and the related challeng...

477 views 5 4
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you