[vagrant-up] can´t get it to work

2016-02-07 Thread Sonlard Berglund
i have the newest vagrant and newest virtualbox

I run windows 10.

In commandprompt i write:

vagrant init hashicorp/precise64

and it creates the vagrantfile

then i write vagrant up and get a error message that says:

 INFO interface: detail: default: Box Provider: virtualbox
default: Box Provider: virtualbox
 INFO interface: detail: Box Version: >= 0
 INFO interface: detail: default: Box Version: >= 0
default: Box Version: >= 0
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: machine_action_up 
#
 INFO warden: Calling IN action: 
#
 INFO environment: Running hook: authenticate_box_url
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 2 hooks defined.
 INFO runner: Running action: authenticate_box_url 
#
 INFO warden: Calling IN action: 
#
 INFO warden: Calling OUT action: 
#
 INFO box_add: Downloading box: 
https://atlas.hashicorp.com/hasicorp/precise64?a
ccess_token=FDNILzLONhGvwA.atlasv1.enzOFS23BKzKXQ4iuXoGNEjHEWkwjFNiAUHF6RX5L8ZQw
ZPQFqwzY9Z8Og1WACAWICg => 
C:/Users/sonlard/.vagrant.d/tmp/box18c4d6937ac41b7203d
5f8d2a46d6c264cc2f3f7
 INFO downloader: HEAD: 
https://atlas.hashicorp.com/hasicorp/precise64?access_to
ken=FDNILzLONhGvwA.atlasv1.enzOFS23BKzKXQ4iuXoGNEjHEWkwjFNiAUHF6RX5L8ZQwZPQFqwzY
9Z8Og1WACAWICg
 INFO subprocess: Starting process: 
["C:\\HashiCorp\\Vagrant\\embedded\\bin/curl
.EXE", "-I", "-q", "--fail", "--location", "--max-redirs", "10", 
"--user-agent",
 "Vagrant/1.8.1 (+https://www.vagrantup.com; ruby2.2.3)", "--continue-at", 
"-",
"-H", "Accept: application/json", 
"https://atlas.hashicorp.com/hasicorp/precise6
4?access_token=FDNILzLONhGvwA.atlasv1.enzOFS23BKzKXQ4iuXoGNEjHEWkwjFNiAUHF6RX5L8
ZQwZPQFqwzY9Z8Og1WACAWICg"]
 WARN downloader: Downloader exit code: 60
ERROR warden: Error occurred: The box 'hasicorp/precise64' 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/hasicorp/precise64;]
Error: SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: The box 'hasicorp/precise64' 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/hasicorp/precise64;]
Error: SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
ERROR warden: Error occurred: The box 'hasicorp/precise64' 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/hasicorp/precise64;]
Error: SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification 

Re: [vagrant-up] can´t get it to work

2016-02-07 Thread Alvaro Miranda Aguilera
Hello,

At this stage is failing to download the box.

As you are in windows, probably is due a change in curl.exe

Can you install 32 bit C++ redistributable package?

Even if your OS is 64 bits, the 32 bits is needed.

https://www.microsoft.com/en-us/download/details.aspx?id=

Thanks
Alvaro

On Sun, Feb 7, 2016 at 10:28 PM, Sonlard Berglund <
sonlard.bergl...@gmail.com> wrote:

> i have the newest vagrant and newest virtualbox
>
> I run windows 10.
>
> In commandprompt i write:
>
> vagrant init hashicorp/precise64
>
> and it creates the vagrantfile
>
> then i write vagrant up and get a error message that says:
>
>  INFO interface: detail: default: Box Provider: virtualbox
> default: Box Provider: virtualbox
>  INFO interface: detail: Box Version: >= 0
>  INFO interface: detail: default: Box Version: >= 0
> default: Box Version: >= 0
>  INFO runner: Preparing hooks for middleware sequence...
>  INFO runner: 1 hooks defined.
>  INFO runner: Running action: machine_action_up
> # 81c0>
>  INFO warden: Calling IN action:
> #
>  INFO environment: Running hook: authenticate_box_url
>  INFO runner: Preparing hooks for middleware sequence...
>  INFO runner: 2 hooks defined.
>  INFO runner: Running action: authenticate_box_url
> # 36f5b80>
>  INFO warden: Calling IN action:
> # on:0x3fdbe40>
>  INFO warden: Calling OUT action:
> # ion:0x3fdbe40>
>  INFO box_add: Downloading box:
> https://atlas.hashicorp.com/hasicorp/precise64?a
>
> ccess_token=FDNILzLONhGvwA.atlasv1.enzOFS23BKzKXQ4iuXoGNEjHEWkwjFNiAUHF6RX5L8ZQw
> ZPQFqwzY9Z8Og1WACAWICg =>
> C:/Users/sonlard/.vagrant.d/tmp/box18c4d6937ac41b7203d
> 5f8d2a46d6c264cc2f3f7
>  INFO downloader: HEAD:
> https://atlas.hashicorp.com/hasicorp/precise64?access_to
>
> ken=FDNILzLONhGvwA.atlasv1.enzOFS23BKzKXQ4iuXoGNEjHEWkwjFNiAUHF6RX5L8ZQwZPQFqwzY
> 9Z8Og1WACAWICg
>  INFO subprocess: Starting process:
> ["C:\\HashiCorp\\Vagrant\\embedded\\bin/curl
> .EXE", "-I", "-q", "--fail", "--location", "--max-redirs", "10",
> "--user-agent",
>  "Vagrant/1.8.1 (+https://www.vagrantup.com; ruby2.2.3)",
> "--continue-at", "-",
> "-H", "Accept: application/json", "
> https://atlas.hashicorp.com/hasicorp/precise6
>
> 4?access_token=FDNILzLONhGvwA.atlasv1.enzOFS23BKzKXQ4iuXoGNEjHEWkwjFNiAUHF6RX5L8
> ZQwZPQFqwzY9Z8Og1WACAWICg"]
>  WARN downloader: Downloader exit code: 60
> ERROR warden: Error occurred: The box 'hasicorp/precise64' 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/hasicorp/precise64;]
> Error: SSL certificate problem: unable to get local issuer certificate
> More details here: http://curl.haxx.se/docs/sslcerts.html
>
> curl performs SSL certificate verification by default, using a "bundle"
>  of Certificate Authority (CA) public keys (CA certs). If the default
>  bundle file isn't adequate, you can specify an alternate file
>  using the --cacert option.
> If this HTTPS server uses a certificate signed by a CA represented in
>  the bundle, the certificate verification probably failed due to a
>  problem with the certificate (it might be expired, or the name might
>  not match the domain name in the URL).
> If you'd like to turn off curl's verification of the certificate, use
>  the -k (or --insecure) option.
>  INFO warden: Beginning recovery process...
>  INFO warden: Recovery complete.
> ERROR warden: Error occurred: The box 'hasicorp/precise64' 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/hasicorp/precise64;]
> Error: SSL certificate problem: unable to get local issuer certificate
> More details here: http://curl.haxx.se/docs/sslcerts.html
>
> curl performs SSL certificate verification by default, using a "bundle"
>  of Certificate Authority (CA) public keys (CA certs). If the default
>  bundle file isn't adequate, you can specify an alternate file
>  using the --cacert option.
> If this HTTPS server uses a certificate signed by a CA represented in
>  the bundle, the certificate verification probably failed due to a
>  problem with the certificate (it might be expired, or the name might
>  not match the domain name in the URL).
> If you'd like to turn off curl's verification of the certificate, use
>  the -k (or --insecure) option.
>  INFO warden: Beginning recovery process...
>  INFO warden: Recovery complete.
> ERROR warden: Error occurred: The box 'hasicorp/precise64' 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`.