Well, you certainly solved it for me. Although what I did was open that file, then set the last ping date to a date far in the future.
The date stamp in the file was 1518199687 I changed that to the year 2022, so now it looks like this: 2218199687 ..and the problem went away. I did not even need to restart the machine or remove/reinstall anything. On Monday, 1 December 2014 21:19:12 UTC, Dave Hildebrandt wrote: > > Hi gang, > > So I was getting this message: > > bash$ vagrant status > Vagrant hasn't been able to verify your usage of 'vagrant-vmware-fusion' in > over two weeks. Please connect to the internet to allow Vagrant to verify > your license. If you don't verify the license within 4 to 6 weeks, you will > be locked out. > Current machine states: > > chef not created (vmware_fusion) > ... > > I am online. It's probably some sort of interaction with the corporate > proxy, but setting http_proxy to http://ourproxy:port is not effective. > > I found a file ~/.vagrant.d/data/last-ping-vagrant-vmware-fusion which > contained a large integer in text form. It was there after uninstalling > the plugin. So I moved it aside and reinstalled the plugin and its > license. I no longer get the error message. However, the last-ping file is > not there. > > Have I solved a problem or just delayed it for a few weeks? > > -d > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/8d8472b5-37d6-46a4-be2c-3651fe0c2d28%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
