Open basictheprogram opened 2 years ago
What OS are you running vagrant on? What troubleshooting have you done?
Hi to all :slightly_smiling_face:
I am also having this issue, when running vagrant on Ubuntu, with Vagrant 2.3.1 and VirtualBox 6.1. Currently, I am using the workaround described in this Stackoverflow thread.
@Xav83 I'm assuming this is what you ran:
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
Where did you run this?
@pauby Yes, this is the line I ran in the Powershell terminal, in the Windows Virtual Machine launch via Vagrant (i don't know if this is really clear :sweat_smile:).
I've just brought this box up in Windows 10 21H2, Hyper-V and Vagrant 2.3.3 and didn't see this issue.
Could it be an Ubuntu issue? Thinking out loud, could it be that it doesn't have the (old) ciphers that Windows Server 2012 R2 uses for WinRM?
I get the same output above running the commands from my work which has started using a self-signed certificate through a proxy.
I can make vagrant itself use the certificate with the SSL_CERT_FILE and CURL_CA_BUNDLE variables; I just copied vagrant's embedded pem file to a location and appended the self-signed cert to it and had the above variables point to the file.
But I've not found a way to get powershell scripts inside the created VM to use include the certificate to let it download.
I added the config.vm.box_download_ca_cert variable in the Vagrantfile, but that didn't do anything with regards to the behavior of the powershell scripts; there's a chance they're ignoring the system certificates (using something like the certifi pypy package) and also the chance that the variables above don't do anything to make the VM's system store use the additional cert.
@slycordinator This sounds very much like a Vagrant issue and not limited to the use of this box?
I agree. I was just giving a possibility for what's going on above.
But since the creation of the vm includes creating a shared folder, a workaround could be have a script that looks in the shared folder for a specially-named pem file and adds it to the windows store if it's present (and the user copies the key to the shared folder).
On Fri, Apr 21, 2023, 7:38 PM Paul Broadwith @.***> wrote:
@slycordinator https://github.com/slycordinator This sounds very much like a Vagrant issue and not limited to the use of this box?
— Reply to this email directly, view it on GitHub https://github.com/chocolatey-community/chocolatey-test-environment/issues/67#issuecomment-1517630637, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQN7DTP4CVQYWLGTHMG6KETXCJPQXANCNFSM5WI4I6GA . You are receiving this because you were mentioned.Message ID: <chocolatey-community/chocolatey-test-environment/issues/67/1517630637@ github.com>
As it's not related to the Box, fixing a Vagrant issue in the Box doesn't feel like the correct place.
If this is a Vagrant issue, it should be raised with Vagrant to fix.
Just started having this problem today.