Closed pradeeps24 closed 7 years ago
Hi there! The WinRM dependencies within Vagrant were updated in the 1.9.2 release. The updated WinRM version fixes this split
error and produces a helpful error if the auth header cannot be properly parsed or is missing. Please upgrade and see if the problem still persists. Thanks!
Hey there,
I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks! 😄
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
We are behind a corporate proxy. Unsetting proxy makes vagrant unable to connect AWS. Setting proxy throws this error.
Vagrant version: Vagrant 1.9.1 (Same for any Version)
Host operating system: AWS Windows 2012R2
Guest operating system: AWS Windows 2012R2
Vagrantfile:
Debug output (Some output are masked like aws secret key, subnet, ami id, security group, system ip, etc)
Expected behavior
EC2 Instance should be launched and connected with WinRM
Actual behavior
WinRM connection fails through Vagrant Ruby WinRM