Vagrant login detail for debian-jessie64 about ampache-sandstorm-prototype

[vionemc]

Perfect! It solved it easily.

[paulproteus]

Hi @vionemc !

It looks to me like vagrant can't access the Internet on your computer. I say that because the URL works OK for me.

Per http://superuser.com/questions/804214/how-to-enable-vagrants-verbose-mode , can you add the VAGRANT_LOG=info environment variable, and maybe that will provide more info about why it's failing?

[vionemc]

Yup, it says the same. It's because I am not logged in yet (and maybe you already are now). And I need the username and password. Did you do vagrant login before?
And I can open the URL in my browser just fine.

 INFO interface: error: The box 'sandstorm/debian-jessie64' 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:

[paulproteus]

I haven't run vagrant login on this machine where I'm testing. I think it's not necessary.

You can try it if you want, though! You can create a free account on https://atlas.hashicorp.com/account/new and use that to log into Vagrant.

I'd like to generally test Vagrant's ability to reach the Internet for public resources by having you go through this tutorial -- https://www.vagrantup.com/docs/getting-started/ -- which uses Vagrant boxes that are definitely public. My hunch is that you'll find you can't access the boxes that are definitely public, in which case we'll know something is weird about your machine's Vagrant connectivity.

[paulproteus]

It could also have been a transient error. I wonder if you retry, does the problem go away? :)

[vionemc]

Hmmm, OK, thanks! That's very helpful.
Nope, it does not go away. I am suspicious there is something wrong with my VirtualBox installation.

[paulproteus]

For what it's worth, the error is coming from Vagrant, not VirtualBox, from what I can tell.

Are you using Internet connectivity that uses a proxy? If so, we'll need to tell Vagrant about it probably.

If your Internet connection is proxying HTTPS traffic and changing certificates, then vagrant will probably have to get told about that, too, though I'm not sure how to.

[vionemc]

Nope, I don't use any proxy. I'll try to Google it. Maybe I'll find something

[paulproteus]

On my system, Vagrant seems to use curl to download things.

Also, you can run:

cd .sandstorm
vagrant up --debug

and get a lot of debug output. Some of that will provide hints about the connectivity problem, I think. Feel free to share it in a gist or in a comment on this issue.

[paulproteus]

Looks like you're running into hashicorp/vagrant#6754 and need a DLL!

[paulproteus]

Once you install https://www.microsoft.com/en-us/download/details.aspx?id=8328 , it should be fixed.

[paulproteus]

If this managed to resolve your question, please mark this as closed! Hopefully my research was helpful; if not, then we should make sure to get your problem resolved!