`vagrant ssh-config` got warning but `vagrant ssh` is still working

Steps to reproduce

vagrant ssh-config got the following warning message:

$ vagrant ssh-config
Host rocky9
  HostName 127.0.0.1
  User vagrant
  Port 2222
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no
  PasswordAuthentication no
  IdentityFile /Users/eliuhy/.vagrant.d/insecure_private_keys/vagrant.key.ed25519
  IdentityFile /Users/eliuhy/.vagrant.d/insecure_private_keys/vagrant.key.rsa
  IdentitiesOnly yes
  LogLevel FATAL
  PubkeyAcceptedKeyTypes +ssh-rsa
  HostKeyAlgorithms +ssh-rsa

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.

but vagrant ssh works as expected:

$ vagrant ssh

This system is built by the Bento project by Chef Software
More information can be found at https://github.com/chef/bento

Use of this system is acceptance of the OS vendor EULA and License Agreements.
Last login: Thu Aug 21 02:38:10 2025 from 10.0.2.2
[vagrant@vbox ~]$

Version Information

  • vagrant: 2.4.8
  • virtualbox: 7.1.12

Host

  • macOS Sequoia 15.6

Hi @eliu ,

I am not too sure, why this would happen, but one guess maybe that when the ssh-config was checked the machine was not ready, I can look further if you have debug logs available, you can get them by passing the debug flag when running vagrant up like vagrant up --debug

Cheers!

Since new users are not allowed to upload files for the moment, here is the debug message i posted into gist: