hashicorp/vagrant · warning

The key `paranoid` is deprecated. Please use `verify_host_ke

Error message

The key `paranoid` is deprecated. Please use `verify_host_key`. Supported
values are exactly the same, only the name of the option has changed.

What it means

config.ssh.paranoid is the old name for config.ssh.verify_host_key: in finalize! the paranoid value is copied into verify_host_key, and during validation any truthy paranoid setting prints this deprecation warning. Supported values are exactly the same; only the option name changed.

Source

Thrown at plugins/kernel_v2/config/ssh_connect.rb:145

            if !File.file?(path)
              errors << I18n.t(
                "vagrant.config.ssh.private_key_missing",
                path: raw_path)
            end
          end
        end

        if @config
          config_path = File.expand_path(@config, machine.env.root_path)
          if !File.file?(config_path)
            errors << I18n.t(
              "vagrant.config.ssh.ssh_config_missing",
              path: @config)
          end
        end

        if @paranoid
          machine.env.ui.warn(I18n.t("vagrant.config.ssh.paranoid_deprecated"))
        end

        if !@connect_timeout.is_a?(Integer)
          errors << I18n.t(
            "vagrant.config.ssh.connect_timeout_invalid_type",
            given: @connect_timeout.class.name)
        elsif @connect_timeout < 1
          errors << I18n.t(
            "vagrant.config.ssh.connect_timeout_invalid_value",
            given: @connect_timeout.to_s)
        end

        if !@connect_retries.is_a?(Integer)
          errors << I18n.t(
            "vagrant.config.ssh.connect_retries_invalid_type",
            given: @connect_retries.class.name
          )
        elsif @connect_retries < 0

View on GitHub (pinned to 35f3160f4a)

Solutions

1. Rename the key: `config.ssh.paranoid = X` becomes `config.ssh.verify_host_key = X` with the same value
2. Remove the line entirely if the default host key verification is acceptable
3. Search the project for other deprecated ssh options while you are at it (grep -n paranoid Vagrantfile)

Example fix

# before
config.ssh.paranoid = true
# after
config.ssh.verify_host_key = true

# Preflight lint before running Vagrant
grep -n "paranoid" Vagrantfile && echo "rename paranoid to verify_host_key"

When it happens

Trigger: A Vagrantfile containing `config.ssh.paranoid = ...` with any truthy value (the UNSET default resolves to false and stays silent).

Common situations: Vagrantfiles written for older Vagrant versions; copy-pasted snippets from old tutorials or team wikis; upgrades to current Vagrant releases.

Related errors

• The box you're attempting to add has no available version th
• The provider for this Vagrant-managed machine is reporting t
• The provider for this Vagrant-managed machine is reporting t
• The provider for this Vagrant-managed machine is reporting t
• Vagrant is configured to generate a random keypair and inser

AI-assisted analysis of hashicorp/vagrant@35f3160f4a (2026-08-21). Data as JSON: /api/errors/cc2ddf35767340ee. Report an issue: GitHub.