9

Here's a transcript so far:

$ sbt new lagom/lagom-scala.g8
[info] Loading global plugins from /Users/abrahma/.sbt/1.0/plugins
[info] Set current project to lagomlife (in build file:/Users/abrahma/Bitbucket/Practice-Scala/LagomLife/)
[info] Set current project to lagomlife (in build file:/Users/abrahma/Bitbucket/Practice-Scala/LagomLife/)

ssh://git@github.com/lagom/lagom-scala.g8.git: Auth fail

I've verified authentication with GitHub:

$ ssh -T git@github.com
Hi agam! You've successfully authenticated, but GitHub does not provide shell access.

Also verified that I can access the repo in question (i.e. I can do the following, in a separate location):

git clone ssh://git@github.com/lagom/lagom-scala.g8.git

Edit: fwiw I'm able to work around whatever the root cause is here:

git clone ssh://git@github.com/lagom/lagom-scala.g8.git
g8 file:///Users/abrahma/tmp/lagom-scala.g8
agam
  • 5,064
  • 6
  • 31
  • 37

3 Answers3

6

I ran into this problem as well, and solved it by removing the following from my ~/.gitconfig:

[url "git@github.com:"]
  insteadOf = https://github.com/
earldouglas
  • 13,265
  • 5
  • 41
  • 50
  • 2
    This worked for me, just annoying because I had to add that to my `.gitconfig` file to get other Go processes to work properly. – Powers Oct 12 '20 at 15:40
1

Are you using OpenSSH 7.8 or newer, and have you recently created your private key?

If so you might be running into the issue described in “Invalid privatekey” when using JSch aka jsch#129.

The root cause was discovered to be the ssh private key mismatch.

The question has a workaround to convert the key file to an older format if that's the error you're seeing.

Eugene Yokota
  • 94,654
  • 45
  • 215
  • 319
0

You need to add your SSH key to the agent:

ssh-add ~/.ssh/id_rsa
benwaffle
  • 322
  • 1
  • 3
  • 12