Hi Alvaro I deleted the vagrant.d boxes as mentioned and still am getting the same time out error. ALso downloaded the latest 2.2.4 vagarnt version. Is there a location where i can change the url from https://vagrantcloud.com/hashicorp/precise64 <https://www.google.com/url?q=https%3A%2F%2Fvagrantcloud.com%2Fhashicorp%2Fprecise64&sa=D&sntz=1&usg=AFQjCNEtiOJbwSjVQsVmD04A7SA-XrMJ8Q> to app.vagrantup.com?
Thanks On Tuesday, April 9, 2019 at 9:28:40 AM UTC-7, Alvaro Miranda Aguilera wrote: > > hello > > vagrant cloud moved to app.vagrantup.com > > so seems something is cached in your machine. > > try this > > - upgrade to latest version of vagrant > - delete .vagrant.d/boxes > > try to add the box as > > vagrant box add hashicorp/precise64 > > Thanks > Alvaro > > On Mon, Apr 8, 2019 at 8:17 PM ashkarthik <[email protected] > <javascript:>> wrote: > >> See results for the commands mentioned below: >> MSYS /c/p64 >> $ vagrant init -m hashicorp/precise64 >> A `Vagrantfile` has been placed in this directory. You are now >> ready to `vagrant up` your first virtual environment! Please read >> the comments in the Vagrantfile as well as documentation on >> `vagrantup.com` for more information on using Vagrant. >> >> $ vagrant up >> Bringing machine 'default' up with 'virtualbox' provider... >> ==> default: Box 'hashicorp/precise64' could not be found. Attempting to >> find and install... >> default: Box Provider: virtualbox >> default: Box Version: >= 0 >> The box 'hashicorp/precise64' could not be found or >> could not be accessed in the remote catalog. If this is a private >> box on HashiCorp's Vagrant Cloud, please verify you're logged in via >> `vagrant login`. Also, please double-check the name. The expanded >> URL and error message are shown below: >> >> URL: ["https://vagrantcloud.com/hashicorp/precise64";] >> Error: Failed to connect to vagrantcloud.com port 443: Timed out >> >> Installed Version: 2.2.3 >> >> $ vagrant plugin list >> No plugins installed. >> >> $ vagrant destroy >> ==> default: VM not created. Moving on... >> >> Attached vagrant file and vagrant up debug logs >> >> On Wednesday, April 3, 2019 at 10:57:03 AM UTC-7, ashkarthik wrote: >>> >>> Hi >>> Am using vagrant v 2.2.3 and Virtual box version 6.0. When I do a >>> vagrant up runbox, the process is stuck at Selectin on IO: See debug >>> message below. A GUI opens with message Starting virtual machine 0% and is >>> stuck there >>> DEBUG subprocess: Waiting for process to exit. Remaining to timeout: >>> 32000 >>> DEBUG subprocess: Exit status: 0 >>> INFO subprocess: Starting process: ["C:/Program >>> Files/Oracle/VirtualBox/VBoxManage.exe", "modifyvm", >>> "3a1ee436-bf75-4e8b-bf82-264a9da72200", "--cpus", "4"] >>> INFO subprocess: Command not in installer, restoring original >>> environment... >>> DEBUG subprocess: Selecting on IO >>> DEBUG subprocess: Waiting for process to exit. Remaining to timeout: >>> 32000 >>> DEBUG subprocess: Exit status: 0 >>> INFO subprocess: Starting process: ["C:/Program >>> Files/Oracle/VirtualBox/VBoxManage.exe", "modifyvm", >>> "3a1ee436-bf75-4e8b-bf82-264a9da72200", "--memory", "12288"] >>> INFO subprocess: Command not in installer, restoring original >>> environment... >>> DEBUG subprocess: Selecting on IO >>> DEBUG subprocess: Waiting for process to exit. Remaining to timeout: >>> 32000 >>> DEBUG subprocess: Exit status: 0 >>> INFO warden: Calling IN action: >>> #<VagrantPlugins::ProviderVirtualBox::Action::Boot:0x000000000593d8c0> >>> INFO interface: info: Booting VM... >>> INFO interface: info: ==> runbox: Booting VM... >>> ==> runbox: Booting VM... >>> INFO subprocess: Starting process: ["C:/Program >>> Files/Oracle/VirtualBox/VBoxManage.exe", "startvm", >>> "3a1ee436-bf75-4e8b-bf82-264a9da72200", "--type", "gui"] >>> INFO subprocess: Command not in installer, restoring original >>> environment... >>> DEBUG subprocess: Selecting on IO >>> >>> Any pointers? >>> >> -- >> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/7b3b7783-0a08-4de0-8059-fd83fb6667db%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/7b3b7783-0a08-4de0-8059-fd83fb6667db%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Alvaro > > -- 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/c872997c-05da-4f74-8607-2db5be6fa828%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
