"Download and install Vagrant within minutes" isn't working

[Kenatsun]

I'm evaluating Vagrant for use in an upcoming Rails project. 

I have installed VirtualBox and Vagrant in my Windows 7 Pro (SP1) system per the instructions in "the book".

I've verified the installs by bringing up the VirtualBox GUI and getting the Vagrant version # (1.7.2) from the console command "Vagrant --version".

But when I run the "two commands", I get:

C:\Users\Ken>vagrant init hashicorp/precise32
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.

C:\Users\Ken>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'hashicorp/precise32' could not be found. Attempting to find and install...
    default: Box Provider: virtualbox
    default: Box Version: >= 0
The box 'hashicorp/precise32' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, 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://atlas.hashicorp.com/hashicorp/precise32"]
Error: Failed connect to atlas.hashicorp.com:443; No error

I notice that the "init" command is different on the "getting started" web page (http://docs.vagrantup.com/v2/getting-started/index.html), which I used in the above vs in "the book".  When I try the book's version, I get this variant on the error:

C:\Users\Ken>vagrant init precise64 http://file.vagrantup.com/precise64.box
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.

C:\Users\Ken>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'precise64' could not be found. Attempting to find and install.
..
    default: Box Provider: virtualbox
    default: Box Version: >= 0
==> default: Adding box 'precise64' (v0) for provider: virtualbox
    default: Downloading: http://file.vagrantup.com/precise64.box
    default: Progress: 0% (Rate: 0curl:/s, Estimated time remaining: --:--:--)
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

Could not resolve host: (nil); Host not found

[Chris Baldauf]

Hello,

You might try manually installing the box to see if that provides a better error message with `vagrant box add hashicorp/precise32`. To get more debug output, you can always add `--debug` parameter to any command That should give you much more output.

Chris

--
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 vagrant-up+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Alvaro Miranda Aguilera]

On Tue, May 26, 2015 at 11:42 AM, Kenatsun <kena...@gmail.com> wrote:
> URL: ["https://atlas.hashicorp.com/hashicorp/precise32"]
> Error: Failed connect to atlas.hashicorp.com:443; No error

Hello,

the book probably was pre version 1.5, where the user/box and auto
download was introduced.

As you did install 1.7.x either way should word.

The command show that there is no internet at the command prompt, can
I ask if you have to setup a proxy to get internet there?

Otherwise, any of those commands should be working.

[Kenatsun]

Thanks, Chris.  Alas, this just evoked the following:

C:\Users\Ken>vagrant box add hashicorp/precise32

The box 'hashicorp/precise32' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Atlas, 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://atlas.hashicorp.com/hashicorp/precise32"]
Error: Failed connect to atlas.hashicorp.com:443; No error

Adding "--debug" evoked (as you promised) "much more output" - much more than I have the time and ability to wade through.

[Kenatsun]

Arvado, thank you. 

I didn't know I had to set up a proxy to connect to the internet, the instructions didn't say anything about this, and I wouldn't know how to go about doing it.  My machine is connected to the internet.

Is there some other way than the command line to get whatever it is that these commands are trying to download?

[Alvaro Miranda Aguilera]

Hello Kenatsun

Is not that Vagrant require a proxy, is just for some reason the
command line is not being able to curl/get the information from atlas.
So I was wondering if you were in a office that was configured with a
proxy, or some user/password requirement on windows.

if your box is connected to internet, it should work.

I am sorry for not being more helpful, but run out of ideas on this one.. :(

[dragon788]

Kenatsun, you could try doing a manual box add rather than having vagrant pull it during the up.

vagrant box add ubuntu/precise32 http://atlas.hashicorp.com/ubuntu/precise32

Should work. If you are still getting failures, verify you can ping atlas.hashicorp.com. You can also switch between http and https on this URL to see if it is an issue with SSL or not.

[Kenatsun]

Thanks, Dragon ~

I tried your easiest suggestion first, and found I can't ping atlas:

C:\>ping atlas.hashicorp.com

Pinging atlas-frontend-atlas-230110478.us-east-1.elb.amazonaws.com [54.175.82.16
9] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 54.175.82.169:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

I also tried another pinger called pathping and got this (I obscured a couple of IPs that I don't want to post on a public forum):

C:\>pathping atlas.hashicorp.com

Tracing route to atlas-frontend-atlas-230110478.us-east-1.elb.amazonaws.com [54.
175.82.169]
over a maximum of 30 hops:
  0  KenGate [192.168.1.108]
  1  192.168.1.1
  2  nnn.nnn.nnn.nnn
  3  nnn.nnn.nnn.nnn
  4  te-9-1-ur02.wbloomfield.mi.michigan.comcast.net [69.139.255.102]
  5  te-0-8-0-8-ar02.pontiac.mi.michigan.comcast.net [69.139.255.69]
  6  be-33668-cr01.350ecermak.il.ibone.comcast.net [68.86.90.45]
  7  be-10206-cr01.newyork.ny.ibone.comcast.net [68.86.86.225]
  8  he-0-12-0-1-pe03.111eighthave.ny.ibone.comcast.net [68.86.85.86]
  9  as16509-3-c.111eighthave.ny.ibone.comcast.net [50.242.148.118]
 10  54.240.229.76
 11     *        *        *
Computing statistics for 250 seconds...
            Source to Here   This Node/Link
Hop  RTT    Lost/Sent = Pct  Lost/Sent = Pct  Address
  0                                           KenGate [192.168.1.108]
                                0/ 100 =  0%   |
  1    0ms     0/ 100 =  0%     0/ 100 =  0%  192.168.1.1
                                0/ 100 =  0%   |
  2   14ms     0/ 100 =  0%     0/ 100 =  0%  nnn.nnn.nnn.nnn
                                0/ 100 =  0%   |
  3   20ms     0/ 100 =  0%     0/ 100 =  0%  nnn.nnn.nnn.nnn
                                0/ 100 =  0%   |
  4   19ms     0/ 100 =  0%     0/ 100 =  0%  te-9-1-ur02.wbloomfield.mi.michigan.comcast.net [69.139.255.102]
                                0/ 100 =  0%   |
  5   18ms     0/ 100 =  0%     0/ 100 =  0%  te-0-8-0-8-ar02.pontiac.mi.michigan.comcast.net [69.139.255.69]
                                0/ 100 =  0%   |
  6   26ms     0/ 100 =  0%     0/ 100 =  0%  be-33668-cr01.350ecermak.il.ibone.comcast.net [68.86.90.45]
                                0/ 100 =  0%   |
  7   44ms     0/ 100 =  0%     0/ 100 =  0%  be-10206-cr01.newyork.ny.ibone.comcast.net [68.86.86.225]
                                0/ 100 =  0%   |
  8   42ms     0/ 100 =  0%     0/ 100 =  0%  he-0-12-0-1-pe03.111eighthave.ny.ibone.comcast.net [68.86.85.86]
                                0/ 100 =  0%   |
  9   42ms     0/ 100 =  0%     0/ 100 =  0%  as16509-3-c.111eighthave.ny.ibone.comcast.net [50.242.148.118]
                                0/ 100 =  0%   |
 10   40ms     0/ 100 =  0%     0/ 100 =  0%  54.240.229.76

Trace complete.

I don't know what to do given this result.  Advice?

~ Tx, Ken

[Ethan S.]

It sounds like your internet provider is unable to access the Amazon Web Services cluster where Atlas is located. I don't have time right this second, but if someone could ping that and give you the IP you could try accessing it directly, but it may be a routing issue between your network and theirs as well. There are some alternative box hosting sites like vagrant box.es where you could try to find a similar box.

You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/Mfw8G4pCUes/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.

[Uday Pingale]

i am facing same issue, can you share how it was resolved...

[Ethan S.]

Uday, can you try the same steps?

Try doing a manual box add rather than having vagrant pull it during the up.

vagrant box add ubuntu/precise32 http://atlas.hashicorp.com/ubuntu/precise32

Should work. If you are still getting failures, verify you can ping atlas.hashicorp.com. You can also switch between http and https on this URL to see if it is an issue with SSL or not.

Ethan S.
ComputerPhreaks
660.386.4096

--
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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/Mfw8G4pCUes/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/f49d23bd-b734-4e03-a0f9-1d3b6b012603%40googlegroups.com.