Closed lcreid closed 7 years ago
Solution A, which is easy but transmits the file over regular HTTP, which is open to various hacks:
vagrant box remove jadesystems/rails5
vagrant box add --insecure
rm Vagrantfile
vagrant init jadesystems/rails5
vagrant up
Solution B, which is more secure, is to figure out which certificate you're missing on your machine, download it, and use it for the vagrant box add
. I can't tell you which certificate you might need, as I don't have a Windows system configured like yours to test against.
vagrant box remove jadesystems/rails5
vagrant box add --cacert your-certificate-file
rm Vagrantfile
vagrant init jadesystems/rails5
vagrant up
Solution C, which is also more secure, is to add the certificate to your certificate directory as described in one of the answers to http://stackoverflow.com/questions/32937994/vagrant-up-not-working-on-windows.
User reported "Error: SSL certificate problem: unable to get local issuer certificate" when bringing up a box. http://stackoverflow.com/questions/32937994/vagrant-up-not-working-on-windows describes one possible cause and a couple of fixes.
There are a number of reports of this symptom on the Internet. It seems like people's certificate authorities/chains/whatever change often enough that people run into grief with the fact that vagrant downloads stuff over HTTPS.