Closed andyinnam closed 4 years ago
This is the error I'm receiving at this point:
PS C:\Users\ainna\DetectionLab\Vagrant> vagrant reload dc --provision
==> dc: Checking if box 'detectionlab/win2016' version '1.6' is up to date...
==> dc: Verifying vmnet devices are healthy...
==> dc: Preparing network adapters...
==> dc: Starting the VMware VM...
==> dc: Waiting for the VM to receive an address...
==> dc: Forwarding ports...
dc: -- 5985 => 55985
dc: -- 5986 => 55986
dc: -- 22 => 2222
==> dc: Waiting for machine to boot. This may take a few minutes...
dc: WinRM address: 127.0.0.1:55985
dc: WinRM username: vagrant
dc: WinRM execution_time_limit: PT2H
dc: WinRM transport: plaintext
==> dc: Machine booted and ready!
==> dc: Setting hostname...
==> dc: Configuring network adapters within the VM...
==> dc: Configuring secondary network adapters through VMware
==> dc: on Windows is not yet supported. You will need to manually
==> dc: configure the network adapter.
==> dc: Enabling and configuring shared folders...
dc: -- C:/Users/ainna/DetectionLab/Vagrant: /vagrant
==> dc: Running provisioner: shell...
dc: Running: scripts/fix-second-network.ps1 as C:\tmp\vagrant-shell.ps1
dc: [13:59] Running fix-second-network.ps1...
dc: [13:59] No VirtIO adapters, moving on...
dc: [13:59]
dc: Setting IP address and DNS information for the Ethernet1 interface
dc: If this step times out, it's because vagrant is connecting to the VM on the wrong interface
dc: See https://github.com/clong/DetectionLab/issues/114 for more information
dc: [13:59] Set IP address to 192.168.38.102 of interface Ethernet1
dc: [13:59] Set DNS server address to 8.8.8.8 of interface Ethernet1
dc: The object is already in the list.
==> dc: Running provisioner: shell...
dc: Running: scripts/provision.ps1 as C:\tmp\vagrant-shell.ps1
dc: [13:59] Setting timezone to UTC...
dc: [13:59] Checking if Windows evaluation is expiring soon or expired...
dc: [13:59] 180 days left until expiration, no need to rearm.
dc: powershell.exe : curl : The underlying connection was closed: Could not establish trust relationship for the
dc: + CategoryInfo : NotSpecified: (curl : The unde...onship for the :String) [], RemoteException
dc: + FullyQualifiedErrorId : NativeCommandError
dc: SSL/TLS secure channel.
dc: At C:\tmp\vagrant-shell.ps1:14 char:1
dc: + curl -userAgent "DetectionLab-$box" "https://ping.detectionlab.networ ...
dc: + ~~~~~~~~~~~~~~~~~
dc: + CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invok
dc: e-WebRequest], WebException
dc: + FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeW
dc: ebRequestCommand
dc:
dc: [13:59] Disabling IPv6 on all network adatpers...
dc: Name DisplayName ComponentID
dc: ---- ----------- -----------
dc: Ethernet1 Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6
dc: Ethernet0 2 Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6
dc: The operation completed successfully.
dc: [13:59] I am domain joined!
dc: [13:59] Provisioning after joining domain...
The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!
powershell -ExecutionPolicy Bypass -OutputFormat Text -file "C:\tmp\vagrant-shell.ps1"
Stdout from the command:
[13:59] Setting timezone to UTC... [13:59] Checking if Windows evaluation is expiring soon or expired... [13:59] 180 days left until expiration, no need to rearm. [13:59] Disabling IPv6 on all network adatpers...
Name DisplayName ComponentID
Ethernet1 Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6 Ethernet0 2 Internet Protocol Version 6 (TCP/IPv6) ms_tcpip6 The operation completed successfully.
[13:59] I am domain joined! [13:59] Provisioning after joining domain...
Stderr from the command:
powershell.exe : curl : The underlying connection was closed: Could not establish trust relationship for the
Ah, I need to update the cert on this host - thanks for the report, will get this fixed ASAP!
In the meantime, you can work around this by commenting out that curl command
Thanks for the quick response! Greatly appreciated. I'll give that a try
Okay, certificate has been updated - this should be fixed now
Just tested and this appears to be fixed. Thanks again for reporting the issue!
Thanks! It appears to be working!
Please verify that you are building from an updated Master branch before filing an issue.
Description of the issue:
Link to Gist Containing Build Logs: