Vagrant-trellis-cert doesn't play nice with Trellis CLI?

trellis
,
22

2.9.10, but I get the same problems as @aitor again

23

have everything working again able to up-down multiple times with trellis CLI and vagrant and trust certs by downgrading vagrant from the latest (2.2.16) to 2.2.10

2 Likes
24

Good work! thank you.

Uninstall Vagrant: https://www.vagrantup.com/docs/installation/uninstallation

2.2.10 installer:
https://releases.hashicorp.com/vagrant/2.2.10/

Github issue:

1 Like
25

Excellent, thank you

26

Posted some more info here: https://github.com/roots/trellis/issues/1303#issuecomment-876698425

1 Like
27

Hi there, I just bumped into this error with a fresh clone of trellis, but without using trellis new:

➜ trellis git:(dev) ✗ vagrant trellis-cert trust
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.

It’s the first time using the new ‘bento/ubuntu-22.04’ box, could it be related somehow?
I’m on Vagrant 2.2.18

Thanks

28

That error message suggests a few things to try, have you done those? What were the results?

Additionally, does vagrant ssh work?

29

Yes I did, vagrant status results in:

Current machine states:

default                   running (parallels)

The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.

And vagrant ssh is also working fine.
I tried destroying the VM and rebuilding it with the same result.

30

Since there’s been a lot of replies and issues about this, I’ll try and summarize things:

  1. this is almost certainly not related to Trellis or trellis-cli
  2. my assumption is it’s related to the Vagrant plugin (and/or in combination with Vagrant itself)
  3. @TangRufus is the author of that plugin and his reply still stands: Vagrant-trellis-cert doesn't play nice with Trellis CLI? - #16 by TangRufus
31

Yeah could be, but I thought it was strange since I enable SSL on all of my local projects and this is the first one that failed to import the certificates with the vagrant trellis-cert trust .
So I know the plugin normally works for me, also with trellis-cli.

32

Don’t waste time on the vagrant plugin. Let’s focus our energy on Add certificate install and uninstall commands by swalkinshaw · Pull Request #311 · roots/trellis-cli · GitHub

33

Hmm, I also have the same timeout when booting the box for the 2nd time by the way:

Running command => vagrant up
Bringing machine 'default' up with 'parallels' provider...
==> default: Checking if box 'bento/ubuntu-22.04-arm64' version '202301.20.0' is up to date...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 0: shared
    default: Adapter 1: hostonly
==> default: Clearing any previously set network interfaces...
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 10.211.55.9:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default: Warning: Host appears down. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...
    default: Warning: Authentication failure. Retrying...

EDIT: I just downgraded to the 'bento/ubuntu-20.04' box and the issue is gone.
I also noticed that I wasn’t able to upload JSON files in ubuntu-22.04 even though I defined them in the upload_mimes filter.

34

@Twansparant those look unrelated? Feel free to open separate threads or bugs please.

Note: that authentication failure is just a Vagrant issue which can happen occasionally. Not a Trellis one.