can´t get it to work

[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 #<Vagrant::Action::Builder:0x3f9
81c0>
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::BoxAdd:0x371db58>
 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 #<Vagrant::Action::Builder:0x
36f5b80>
 INFO warden: Calling IN action: #<VagrantPlugins::LoginCommand::AddAuthenticati
on:0x3fdbe40>
 INFO warden: Calling OUT action: #<VagrantPlugins::LoginCommand::AddAuthenticat
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`. 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: Calling recover: #<Vagrant::Action::Builtin::Call:0x36a81c8>
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO warden: Recovery complete.
 INFO warden: Beginning recovery process...
 INFO warden: Recovery complete.
 INFO environment: Released process lock: machine-action-84cc5a58696c857ca6f805b
0546f1cb0
 INFO environment: Running hook: environment_unload
 INFO runner: Preparing hooks for middleware sequence...
 INFO runner: 1 hooks defined.
 INFO runner: Running action: environment_unload #<Vagrant::Action::Builder:0x37
26b40>
ERROR vagrant: Vagrant experienced an error! Details:
ERROR vagrant: #<Vagrant::Errors::BoxAddShortNotFound: The box 'hasicorp/precise
64' 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.>
ERROR vagrant: 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.
ERROR vagrant: C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant
/action/builtin/box_add.rb:89:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.
rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder
.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.
rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:1
9:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.
rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin
/handle_box.rb:82:in `handle_box'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin
/handle_box.rb:42:in `block in call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin
/handle_box.rb:36:in `synchronize'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin
/handle_box.rb:36:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.
rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.
rb:95:in `block in finalize_action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.
rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.
rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder
.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.
rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:1
9:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.
rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builtin
/call.rb:53:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.
rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/plugins/providers/virtualb
ox/action/check_virtualbox.rb:17:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/warden.
rb:34:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/builder
.rb:116:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.
rb:66:in `block in run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/util/busy.rb:1
9:in `busy'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/action/runner.
rb:66:in `run'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:224
:in `action_raw'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:199
:in `block in action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/environment.rb
:561:in `lock'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:185
:in `call'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/machine.rb:185
:in `action'
C:/HashiCorp/Vagrant/embedded/gems/gems/vagrant-1.8.1/lib/vagrant/batch_action.r
b:82:in `block (2 levels) in run'
 INFO interface: error: 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.
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 interface: Machine: error-exit ["Vagrant::Errors::BoxAddShortNotFound", "T
he box 'hasicorp/precise64' could not be found or\ncould not be accessed in the
remote catalog. If this is a private\nbox on HashiCorp's Atlas, please verify yo
u're logged in via\n`vagrant login`. Also, please double-check the name. The exp
anded\nURL and error message are shown below:\n\nURL: [\"https://atlas.hashicorp
.com/hasicorp/precise64\"]\nError: SSL certificate problem: unable to get local
issuer certificate\r\nMore details here: http://curl.haxx.se/docs/sslcerts.html\
r\n\r\ncurl performs SSL certificate verification by default, using a \"bundle\"
\r\n of Certificate Authority (CA) public keys (CA certs). If the default\r\n bu
ndle file isn't adequate, you can specify an alternate file\r\n using the --cace
rt option.\r\nIf this HTTPS server uses a certificate signed by a CA represented
 in\r\n the bundle, the certificate verification probably failed due to a\r\n pr
oblem with the certificate (it might be expired, or the name might\r\n not match
 the domain name in the URL).\r\nIf you'd like to turn off curl's verification o
f the certificate, use\r\n the -k (or --insecure) option."]


How do i get this to work?

[Edgar Oliveira]

Try which another box, e.g. 32 bits!
Access this site: https://atlas.hashicorp.com/boxes/search?utm_source=vagrantcloud.com&vagrantcloud=1
Or http://www.vagrantbox.es

--
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 vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2d2f15e1-ed7c-46c8-b016-8818b749d40b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Edgar Oliveira]

Try with another box, e.g. 32 bits!

Access this site: https://atlas.hashicorp.com/boxes/search?utm_source=vagrantcloud.com&vagrantcloud=1
Or http://www.vagrantbox.es

On Feb 7, 2016 9:28 AM, "Sonlard Berglund" <sonlard....@gmail.com> wrote:

[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=5555

Thanks

Alvaro

[Moshe Suberri]

You do have issue with the SSL certificate.
Try the following:
   vagrant init
   vagrant up hashicorp/precise64 --insecure

[Mark M]

Did you ever get this working?  Here I am 1 year later, trying it on a Windows 10 box and I have the same problem.  I am using Vagrant 1.9.1

- Mark

On Sunday, February 7, 2016 at 4:28:26 AM UTC-5, Sonlard Berglund wrote:

[Alvaro Miranda Aguilera]

Hello Mark.

Vagrant on win10 it does work

I use them in 2 computers.

What are the errors/issues you see?

Did you install virtualbox from the official download, and did restart the machine after?

did you install vagrant from our official installer and then restarted the machine?

Thanks

Alvaro.

Virusvrij. www.avast.com

[Alvaro Miranda Aguilera]

hello

could you try this

vagrant halt

set VAGRANT_LOG=debug

vagrant up

and share the verbose output over a gist (gist.github.com)

thanks

alvaro

---------- Forwarded message ----------
From: M6rk <m6r...@gmail.com>
Date: Mon, Feb 27, 2017 at 6:55 PM
Subject: Re: [vagrant-up] Re: can´t get it to work
To: kik...@gmail.com

Hi Alvaro ,

Thanks for the response.  I installed latest using Chocolatey:

choco inst vagrant virtualbox

I did reboot. 

Vagrant -v shows 1.9.1

Here is the error I get:

PS D:\ubuntu> vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'hashicorp/precise32' could not be found. Attempting to find and in
    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: 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.

PS D:\ubuntu>

Any help or guidance would be appreciated.  I can also setup a GTM and share my screen etc if you think that would help. 

- Mark

--

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/8HTAaXnsYt4/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezHMsKFSEyGe4_JUoFViB0nbjbYua8qyg4pMj0XqERoKg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[M6rk]

Nothing new in the output:

gist:c05a9400bb3a0c658cb9b02e4204f218

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ewoEdCnZOZpEUW4ORwo4cYHpP63mHZMaJ8PAvRM2S66rg%40mail.gmail.com.

[Alvaro Miranda Aguilera]

hello

Can you try as this (check the capital letters)

set VAGRANT_LOG=debug

vagrant up

It seems you are on power shell, so the variable may be need to be ser differently:

https://msdn.microsoft.com/en-us/powershell/reference/4.0/microsoft.powershell.utility/set-variable

Are you behind any proxy or coporate network?

Do you know if you need to setup a proxy to reach internet?

We just tested on a new win10 machines and confirmed it just works.

Thanks

Alvaro

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CADc-WxM-D0j0AdfrmMHXSmzNaxO_Bb07twnp7L6oYk-51VM%2BuQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Dawn Hersey]

Has anyone found a fix for this?  I am using Windows 10, installed Vagrant 2.0.0, and have the same problem.

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/CAHqq0ezHMsKFSEyGe4_JUoFViB0nbjbYua8qyg4pMj0XqERoKg%40mail.gmail.com.

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 a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/8HTAaXnsYt4/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/CAHqq0ewoEdCnZOZpEUW4ORwo4cYHpP63mHZMaJ8PAvRM2S66rg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--
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 vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CADc-WxM-D0j0AdfrmMHXSmzNaxO_Bb07twnp7L6oYk-51VM%2BuQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

[Alvaro Miranda Aguilera]

whats the same problem?