VVV: Broken Key Forwarding and GitHub host verification failure

In order to add the custom site, I read I just need set repo https://github.com/Varying-Vagrant-Vagrants/vvv-wordpress-default.git with provision for a default WordPress website.

Now, I just want to customize the provision, adding other actions specific for my work (such install plugins, themes, XML data, so on). So, I made my own private repository where I did the thing I need and everything could be all fine, except for the fact that I have an error when the provisioner tries to clone a private repository because he cannot authenticate. Unfortunately, I need that this would be in a private repository and not a public one.

Expected Behavior

I expect me one of these things:

  • ask me the username or password in order to make the authentication
  • give me the ssh key of vagrant and ask me to add into my Github/Bitbucket account
  • use the private key of my local host (and not vagrant one) that should be already added in my Github/Bitbucket account

Current Behavior

This is the error if I try to write the git URL for ssh connection (that is git@github.com:ecc/ecc.git)

==> default: Host key verification failed.
==> default: fatal: Could not read from remote repository.

Instead, this is the error if I put the https URL for git repository:

==> default: fatal: could not read Username for 'https://github.com': No such device or address

Possible Solution

Try to connect ssh with the private key of the local host machine, not vagrant one, I don’t know if it’s possible and how to do that.

Steps to Reproduce (for bugs)

  1. Clone https://github.com/Varying-Vagrant-Vagrants/vvv-wordpress-default.git into a private repository
  2. Add new custom site into vvv-config.yml from the private repository
  3. Make vagrant provision

Your Environment

  • VVV version: 2.0.0
  • Vagrant version: 1.9.0
  • VM Provider name: VirtualBox
  • VM Provider version: 5.1.22
  • Operating System and version: MacOS 10.12.5

About this issue

  • Original URL
  • State: closed
  • Created 7 years ago
  • Comments: 20 (8 by maintainers)

Most upvoted comments

For reference:

  • Use SSH not HTTPs for GitHub URLs
  • Test with the very latest VVV on the develop branch, it has a lot of fixes that haven’t made it to master yet
  • Verify you’re on the latest version, that includes the branch you’re using
  • Update Vagrant itself. Halt your VMs, uninstall Vagrant then install the latest version ( 2.0 at time of writing )
  • Verify your SSH Agent is running and active. You can’t forward SSH keys if there’s nothing to forward on to the VM
  • Include the relevant terminal output, even when trying new suggested solutions

As a final note, don’t fork the default site repo, use or fork the custom site repo

Thanks @tomjn It works now by updating vagrant version to latest one (I had 1.9.6). It works even if I remove the trusted-hostsutility 😃 So the solution might be for all: update vagrant version at least to 2.0