for paid support or unsure email [email protected] if the box is private, then they should get access to the box first then use vagrant login to make sure they will use their creds to be able to see/download private boxes
feel free to email [email protected] Alvaro On Thu, Aug 3, 2017 at 9:31 AM, brunom <[email protected]> wrote: > Hi there, > > I am not sure if this group would be the right one to post this ... > however I will start here before posting something on GitHub as I am > uncertain where one would ask for support for Vagrantcloud (we have a paid > plan, etc but where to find support is unclear to me, as a paying > customer). Maybe that'd be the first question :) > > Second: I have created a new revision and released it of a private box > that we use as our SOE base for devs. We have two providers we care about > for vagrant, virtualbox and vmware. Both are created via packer in Atlas > and published using a post-processor. I can see the boxes via the web UI on > vagrant cloud, I can see that vagrant sees the latest version when I do > `vagrant box add ... ` ... however, all my colleagues and myself are > getting: > > ==> box: Adding box 'waysact/trusty64' (v26) for provider: virtualbox > box: Downloading: https://vagrantcloud.com/waysact/boxes/trusty64/ > versions/26/providers/virtualbox.box > An error occurred while downloading the remote file. The error > message, if any, is reproduced below. Please fix this error and try > again. > > The requested URL returned error: 404 Not Found > > I generated a new token in vagrant cloud just in case, that token is now > in the env in a clean session/shell ... still. My colleague is setting up a > new machine, clean env ... same. > > So, the questions I have are: > > - any hints on how I can debug exactly what payload is being sent (HTTP > etc)? > - how do I get support on Vagrant Cloud specifically? > > Cheers > > /B > > -- > 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/eb96efea-e5f9-48b9-8b64-d758b6b6ec8d%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/eb96efea-e5f9-48b9-8b64-d758b6b6ec8d%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/CAHqq0ez2tvneubcopECHQkG8ZcKi__-LQB0GEoDFP%3DJ3w3Pu4A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
