We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There seems to be an incompatibility with the latest version of vagrant (2.2.16). Downgrading Vagrant to 2.2.10 fix all problems. More info here
vagrant Up
vagrant halt
vagrant up
vagrant reload
Actual behavior: [What actually happens]
The second time running vagrant up or vagrant reload there is a faliure in the SSH athentication:
Waiting for machine to boot. This may take a few minutes... default: SSH address: 127.0.0.1:2222 default: SSH username: vagrant default: SSH auth method: private key default: Warning: Connection reset. Retrying... default: Warning: Authentication failure. Retrying... default: Warning: Authentication failure. Retrying...
Reproduces how often: [What percentage of the time does it reproduce?]
All times
Trellis 1.8.0: February 12th, 2021 macOS 11.4
The text was updated successfully, but these errors were encountered:
To downgrade,
brew remove vagrant curl -O -L https://raw.githubusercontent.com/Homebrew/homebrew-cask/d81815ea27a778a312fa0e2bbef0d78f9767f45b/Casks/vagrant.rb brew install --cask vagrant.rb
Stack overflow
Then I also needed to run
sudo vagrant plugin expunge --reinstall
And also chown .vagrant.d which was owned by root (maybe from installing Vagrant from the downloaded installer.)
sudo chown -R mikekilmer:staff /Users/mikekilmer/.vagrant.d/
I forget what the {whoami} syntax is.
{whoami}
Sorry, something went wrong.
Looks like hashicorp/vagrant#12344 was the problem.
2.2.17 was released which fixes that. So looks like either <2.2.15 or >2.2.17 should work.
I'm going to close this issue since there's not much Trellis itself can do and the latest version of Vagrant should fix it.
No branches or pull requests
Description
There seems to be an incompatibility with the latest version of vagrant (2.2.16). Downgrading Vagrant to 2.2.10 fix all problems. More info here
Steps to reproduce
vagrant Up
vagrant halt
vagrant up
vagrant reload
Actual behavior: [What actually happens]
The second time running
vagrant up
orvagrant reload
there is a faliure in the SSH athentication:Reproduces how often: [What percentage of the time does it reproduce?]
All times
Versions
Trellis 1.8.0: February 12th, 2021
macOS 11.4
The text was updated successfully, but these errors were encountered: