Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vagrant setup - some installers have found SSL / TLS warnings preventing them to set it up #3776

Open
rowasc opened this issue Sep 27, 2019 · 0 comments

Comments

@rowasc
Copy link
Contributor

commented Sep 27, 2019

This issue https://github.com/ushahidi/platform/pull/3485/files mentions an error that can happen for some users, specifically they run into an issue where Vagrant cannot be installed and it needs to be installed with the --insecure flag.
This isn't something I want to add as-is, I'd like to understand why it happens to them first and what solution to offer depending on that.

My suggestion so far, considering the comments in the PR


To being with, I'd add the following (before instructing them to run with --insecure)

  • Before you continue: check that you are running the latest (stable) version of vagrant
    • To check this run vagrant version , It will tell you if you are in the latest version of vagrant or not.
    • If you are not in the latest vagrant, please update/replace vagrant with the latest version
      Depending on the specific error regarding SSL (ie is it reporting a self signed certificate? or is it saying it's unable to find the local issuer certificate? )
    • After updating vagrant, clean up the local vagrant directories (ie .vagrant in your project's directory , ~/.vagrant/tmp ) and try again .
  • Other things to check and fix if necessary : Virtualbox is up to date

If that doesn't work, a user can start looking into why the issue is happening for them specifically. This stackoverflow answer might help as a general starting point https://stackoverflow.com/a/42209673
although it'll be environment/situation specific in the end to fix it.
There's also the relatively new config config.vm.box_download_ca_cert which can be useful if we know the box url and can check with curl -v <box url> to see what certificate is being used to fetch it and wether or not that's working
pinging @\tuxpiper about this: for some reason I cannot figure out the box url for homestead, it seems to have changed and I can only access the html view https://app.vagrantup.com/laravel/boxes/homestead-7/versions/0.2.1 , do you know how that would be done now?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.