48

Today morning suddenly I started getting this popup whenever I ran Vagrant up in my Mac.

Enter image description here

VirtualBox version 7.0.4 r154605 (Qt5.15.2).
macOS v12 (Monterey), MacBook Pro (Retina, 15-inch, Mid 2015)

Ubuntu LTS Settler Version Homestead Version Branch Status
20.04 11.x 12.x main Development/Unstable
20.04 11.x 12.x release Stable

What's wrong here?

lagbox
  • 48,571
  • 8
  • 72
  • 83
Jigar
  • 3,055
  • 1
  • 32
  • 51
  • 4
    This usually happens when the software does not come from the App store or some authorization was revoked. I don't know exactly why it happens, but if you're sure you can 'trust' the software you could bypass the mallware protection by right-clicking the software causing the alert. `Get Info` -> `General (expand it)` -> and check `Override Malware Protection`. [Guide](https://iboysoft.com/news/remove-will-damage-your-computer-error-mac.html) – geertjanknapen Apr 26 '23 at 07:23
  • You can [download the macos bianry from hashicrop site](https://developer.hashicorp.com/vagrant/downloads?product_intent=vagrant) and install it. This fixed the issue for me. – Thilina Hasantha Apr 29 '23 at 06:37

7 Answers7

54

I also had the same issue after upgrading to macOS v13.3.1 (Ventura. 22E261).

Try the following:

  1. brew reinstall --cask vagrant
  2. vagrant plugin update

Then the problem will be solved.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Elhassan Baazizi
  • 556
  • 5
  • 3
38

The previous fixes look correct. The error itself is due to the signing key being revoked on April 24th, 2023.

Hashicorp did this due to the CircleCI data breach. Details are available at Security Alert: HashiCorp Response to CircleCI.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Joe W.
  • 1,442
  • 14
  • 9
12

I had the same error message on macOS v11.7.6 (Big Sur. 20G1231).

After downloading and reinstalling the AMD64 installer from Vagrant and running

vagrant plugin update
vagrant plugin repair

in the terminal, everything worked as before.

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Lutz Grätz
  • 121
  • 2
  • 6
  • Worked here for Monterey 12.6.3 as well. One difference - the warning screen from op's screenshot said "ruby" would damage my computer, instead of vagrant. Obviously vagrant uses ruby, so an update from the AMD64 installer fixed it. – JDev518 Apr 27 '23 at 18:05
  • One other note - if your version of Vagrant isn't too far behind the current version, ```vagrant plugin update``` and ```vagrant plugin repair``` isn't necessary, at least it wasn't for me from v2.3.1 -> v2.3.4 – JDev518 Apr 27 '23 at 18:09
4

Running

brew install hashicorp/tap/hashicorp-vagrant

in your CLI will update to latest vagrant and fixes the issue.

Dan E
  • 167
  • 1
  • 11
  • Only this one worked for me, simply installing vagrant was throwing: `Error: The following directories are not writable by your user: /usr/local/bin` – serg May 01 '23 at 23:51
4

For those who are getting a SHA-256 mismatch, you can try to run brew untap vagrant and brew tap vagrant and retry the upper commands:

brew reinstall --cask vagrant

vagrant plugin update
Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
maurinaz
  • 41
  • 1
1

I reinstalled Vagrant, and then it all works again...

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
Kleppo
  • 11
  • 1
0

I had same issue without upgrading or update macos or anything. Try it;

brew install hashicorp/tap/hashicorp-vagrant

Solved my problem

desertnaut
  • 57,590
  • 26
  • 140
  • 166
eerenyilmaz
  • 11
  • 1