Not sure whether there’s another issue at play here, but these self-signed SSL steps never used to give me issues prior to using Trellis CLI… Since changing to the CLI running
vagrant trellis-cert trust produces the following error:
Importing certificates... The provider for this Vagrant-managed machine is reporting that it is not yet ready for SSH. Depending on your provider this can carry different meanings. Make sure your machine is created and running and try again. Additionally, check the output of `vagrant status` to verify that the machine is in the state that you expect. If you continue to get this error message, please view the documentation for the provider you're using.
Furthermore, after the error,
trellis up never behaves the same again, producing an endless loop of:
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...
trellis down produces:
Running command => vagrant halt ==> default: Attempting graceful shutdown of VM... default: Guest communication could not be established! This is usually because default: SSH is not running, the authentication information was changed, default: or some other networking issue. Vagrant will force halt, if default: capable. ==> default: Forcing shutdown of VM...
Is as if something breaks on the SSH side of things either after running
vagrant plugin install vagrant-trellis-cert or
vagrant trellis-cert trust…
Is there perhaps a different way I should be adding vagrant plugins when using the CLI? Is there some kind of workaround?