hashicorp/vagrant · error · VagrantPlugins::CommunicatorWinRM::Errors::WinRMInvalidTransport
%{transport} is not a supported WinRM transport.
Error message
%{transport} is not a supported WinRM transport. What it means
Error "%{transport} is not a supported WinRM transport." thrown in hashicorp/vagrant.
Source
Thrown at plugins/communicators/winrm/shell.rb:233
@logger.info(" - Transport: #{@config.transport}")
client = ::WinRM::Connection.new(endpoint_options)
client.logger = @logger
client
end
def connection
@connection ||= new_connection
end
def endpoint
case @config.transport.to_sym
when :ssl
"https://#{@host}:#{@port}/wsman"
when :plaintext, :negotiate
"http://#{@host}:#{@port}/wsman"
else
raise Errors::WinRMInvalidTransport, transport: @config.transport
end
end
def endpoint_options
{ endpoint: endpoint,
transport: @config.transport,
operation_timeout: @config.timeout,
user: @username,
password: @password,
host: @host,
port: @port,
basic_auth_only: @config.basic_auth_only,
no_ssl_peer_verification: !@config.ssl_peer_verification,
retry_delay: @config.retry_delay,
retry_limit: @config.max_tries }
end
def elevated_usernameView on GitHub (pinned to 35f3160f4a)
When it happens
Trigger: Thrown at plugins/communicators/winrm/shell.rb:233 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of hashicorp/vagrant@35f3160f4a (2026-08-21).
Data as JSON: /api/errors/f3146f50af0f42a1.
Report an issue: GitHub.