“vagrant” will damage your computer. | macOS v12 (Monterey) #13132

“vagrant” will damage your computer. | macOS v12 (Monterey) #13132

17

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

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?

Share

1

  • 2

    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

    – geertjanknapen

    yesterday

8 Answers
8

Reset to default

Highest score (default)

Trending (recent votes count more)

Date modified (newest first)

Date created (oldest first)

21

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.

Share

New contributor

Elhassan Baazizi is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

0

13

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.

Share

5

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.

Share

1

  • 1

    This worked for me as well (macOS Monterey version 12.6.3), thanks! ❤️

    – Olive

    yesterday

1

Running

brew install hashicorp/tap/hashicorp-vagrant

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

Share

1

I reinstalled Vagrant, and then it all works again…

Share

New contributor

Kleppo is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

1

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

Share

New contributor

maurinaz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

0

I just ran brew update && brew upgrade.
It upgrades all your brew packages, but you know, might as well.
While I were on it, also upgraded macOS to Ventura.

Be safe and stay hydrated.

Share

New contributor

Christoffer Mossberg is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

0

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

brew install hashicorp/tap/hashicorp-vagrant

Solved my problem

Share

New contributor

eerenyilmaz is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

Your Answer

Draft saved
Draft discarded

Post as a guest

Required, but never shown


By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged

or ask your own question.

Leave a Reply

Your email address will not be published. Required fields are marked *