hashicorp/vagrant · error · VagrantPlugins::CommandRDP::Errors::RDPUndetected

RDP connection information for this machine could not be det

Error message

RDP connection information for this machine could not be detected. This is typically caused when we can't find the IP or port to connect to for RDP. Please verify you're forwarding an RDP port and that your machine is accessible.

What it means

`vagrant rdp` could not determine where to point the RDP client: `get_rdp_info(machine)` returned nil. Detection depends on the machine exposing an RDP endpoint (a forwarded port for guest 3389 or an addressable network IP), so a guest without either cannot be connected to. The error is raised before any client launch is attempted.

Source

Thrown at plugins/commands/rdp/command.rb:43

          @argv                = @argv.take(split_index)
        end

        # Parse the options and return if we don't have any target.
        argv = parse_options(opts)
        return if !argv

        # Check if the host even supports RDP
        raise Errors::HostUnsupported if !@env.host.capability?(:rdp_client)

        # Execute RDP if we can
        with_target_vms(argv, single_target: true) do |machine|
          if !machine.communicate.ready?
            raise Vagrant::Errors::VMNotCreatedError
          end

          machine.ui.output(I18n.t("vagrant_rdp.detecting"))
          rdp_info = get_rdp_info(machine)
          raise Errors::RDPUndetected if !rdp_info

          # Extra arguments if we have any
          rdp_info[:extra_args] = options[:extra_args]

          machine.ui.detail(
            "Address: #{rdp_info[:host]}:#{rdp_info[:port]}")
          machine.ui.detail("Username: #{rdp_info[:username]}")

          machine.ui.success(I18n.t("vagrant_rdp.connecting"))
          @env.host.capability(:rdp_client, rdp_info)
        end
      end

      protected

      def get_rdp_info(machine)
        rdp_info = {}
        if machine.provider.capability?(:rdp_info)

View on GitHub (pinned to 35f3160f4a)

Solutions

Forward the RDP port in the Vagrantfile: `config.vm.network "forwarded_port", guest: 3389, host: 33389`, then `vagrant reload`
Or attach a private network with a static IP (`config.vm.network "private_network", ip: "192.168.33.10"`) and RDP to that address
Verify the machine is running and the communicator works (`vagrant status`, `vagrant ssh`) before retrying

Example fix

# before
Vagrant.configure('2') do |config|
  config.vm.box = 'my-windows-box'
end
# vagrant rdp  ->  RDPUndetected

# after
Vagrant.configure('2') do |config|
  config.vm.box = 'my-windows-box'
  config.vm.network 'forwarded_port', guest: 3389, host: 33389
end

Defensive patterns

Strategy: validation

Validate before calling

fwd = machine.config.vm.networks.any? { |type, opts| type == :forwarded_port && opts[:guest] == 3389 }
priv = machine.config.vm.networks.any? { |type, _| type == :private_network }
abort 'RDP needs forwarded guest port 3389 or a private network IP' unless fwd || priv

Try / catch

begin
  command.execute
rescue Vagrant::Errors::RDPUndetected
  warn 'no RDP endpoint detected; run: vagrant port'
  exit 1
end

Prevention

Always declare an RDP forwarded port or private-network IP for Windows guests
Wait until the machine communicator is ready before invoking rdp
Gate `vagrant rdp` on a successful `vagrant port --guest 3389` lookup in scripts

When it happens

Trigger: No `config.vm.network "forwarded_port", guest: 3389, host: <port>` and no private/public network IP on the machine; the machine exists but address resolution via the communicator fails so get_rdp_info returns nil.

Common situations: Windows boxes that do not pre-forward 3389; NAT-only networking where the guest IP is unknown to Vagrant; running `vagrant rdp` immediately after `vagrant up` before the machine is fully reachable.

Related errors

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