CC @bcmills maybe?

Show your git config and ssh setup?
also, go get -v -x ... output please.

You need either an insteadOf clause in your .gitconfig or a personal access token in your .netrc. See #26134 (comment).

Duplicate of #26134

I don't think this is a duplicate of #26134, because I do have this in my gitconfig:

[url "ssh://git@github.com/"]
        insteadOf = https://github.com/

go get -v -x ... output:

mkdir -p /Users/arieroos/Workspace/go/pkg/mod/cache/vcs # git3 https://github.com/Private-Org/go-commons
# lock /Users/arieroos/Workspace/go/pkg/mod/cache/vcs/4371bddb1b5a61a8f85ece4f86eaa40bbac4cc02925be418880bcce25aafa433.lock# /Users/arieroos/Workspace/go/pkg/mod/cache/vcs/4371bddb1b5a61a8f85ece4f86eaa40bbac4cc02925be418880bcce25aafa433 for git3 https://github.com/Private-Org/go-commons
cd /Users/arieroos/Workspace/go/pkg/mod/cache/vcs/4371bddb1b5a61a8f85ece4f86eaa40bbac4cc02925be418880bcce25aafa433; git ls-remote -q origin
3.141s # cd /Users/arieroos/Workspace/go/pkg/mod/cache/vcs/4371bddb1b5a61a8f85ece4f86eaa40bbac4cc02925be418880bcce25aafa433; git ls-remote -q origin
# get https://github.com/Private-Org/go-commons
# get https://github.com/Private-Org/go-commons: 404 Not Found (1.131s)
# get https://proxy.golang.org/github.com/@v/list
# get https://proxy.golang.org/github.com/@v/list: 410 Gone (1.423s)
go: module github.com/Private-Org/go-commons: git ls-remote -q origin in /Users/arieroos/Workspace/go/pkg/mod/cache/vcs/4371bddb1b5a61a8f85ece4f86eaa40bbac4cc02925be418880bcce25aafa433: exit status 128:
        git@github.com: Permission denied (publickey).
        fatal: Could not read from remote repository.
        
        Please make sure you have the correct access rights
        and the repository exists.

and what happens if you do:

cd /Users/arieroos/Workspace/go/pkg/mod/cache/vcs/4371bddb1b5a61a8f85ece4f86eaa40bbac4cc02925be418880bcce25aafa433; git ls-remote -q origin

@seankhliao That command runs successfully. It asks for my private key passphrase and the lists all the refs in the repo.

I also downgraded my project go version to 1.17, which gave the same issue. However, I don't get this issue with 1.16. So it seems that the go get changes between 1.16 and 1.17 might have something to do with this.

@arieroos , I've been fighting with a similar problem and this is what worked for me:

git@github.com: Permission denied (publickey) tells you that go get is not using a password nor a ssh key.

Whilst commands like git fetch, git pull worked for me on the same repository because I was using an ssh key set up in ~/.ssh/config (as alias), it looked as if go get did not take any configuration from ~/.ssh/config.

So next; I checked out why my ssh key was not used. Looking around, I found out that go get needed the key to be added to the ssh-agent. Hence,

• I listed the keys added to the agent with ssh-add -l
• I verified that the key I had to use for the authentication was not added to the agent
• I added the key: ssh-add ~/.ssh/<your_private.key>
• And bingo! go get worked!

I hope this helps.

@al-villalba That worked! Thanks a million!

https://go.dev/doc/go1.17#password-prompts

go doesn't look at (or care about) ssh, it's up to git the user to ensure https://git/repo is translated into something that can be fetched automatically

It's not about what method to use for authentication, ssh or https. It's about how to use ssh+key, as this method is the preferred method for corporate private repositories and often is the only one.

Don't take me wrong, but if I can login to a remote machine with ssh, copy files remotely with scp, fetch content from private repositories with git fetch, using my keys set up in ~/.ssh/config, I will expect go get will be able to download using ~/.ssh/config. And this doesn't seem to be the case.

It's about how to use ssh+key, as this method is the preferred method for corporate private repositories and often is the only one.

Ah! In that case, I think #49515 is probably a better fit. See specifically #49515 (comment) for details.

https://go.dev/doc/go1.17#password-prompts

Ah. I missed that when I originally read the release notes.
Thanks everyone for your help!