# Vagrant 1.8.7 will not download image. Reverting to 1.8.6 will work

**URL:** https://meta.discourse.org/t/vagrant-1-8-7-will-not-download-image-reverting-to-1-8-6-will-work/53276
**Category:** Development
**Created:** [November 22, 2016, 10:22pm UTC](https://meta.discourse.org/t/vagrant-1-8-7-will-not-download-image-reverting-to-1-8-6-will-work/53276 "2016-11-22T22:22:17Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![eriko](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eriko/32/1915_2.png) [@eriko](https://meta.discourse.org/u/eriko)
#### Post date: [November 22, 2016, 10:22pm UTC](https://meta.discourse.org/t/vagrant-1-8-7-will-not-download-image-reverting-to-1-8-6-will-work/53276/1 "2016-11-22T22:22:17Z")

</div>

I am back to a bit more work on the the cas\_sso app and rebuilding things after doing a full wipe of my dev environment. Anyways I am getting the following while doing vagrant up

```
default: Downloading: https://www.dropbox.com/s/2132770g1e05c6d/discourse.box?dl=1
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

```

Any thoughts?

---

<div class="post-metadata">

### Author: ![jsvisa](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jsvisa/32/64370_2.png) [@jsvisa](https://meta.discourse.org/u/jsvisa)
#### Post date: [November 24, 2016, 3:41pm UTC](https://meta.discourse.org/t/vagrant-1-8-7-will-not-download-image-reverting-to-1-8-6-will-work/53276/2 "2016-11-24T15:41:46Z")

</div>

No, It’s ok in my side:

```
~$curl -I "https://www.dropbox.com/s/2132770g1e05c6d/discourse.box?dl=1"
HTTP/1.1 302 Found
Server: nginx
Date: Thu, 24 Nov 2016 15:40:44 GMT
Content-Type: text/html; charset=utf-8
Connection: keep-alive
Cache-Control: no-cache
Content-Security-Policy: sandbox
Location: https://dl.dropboxusercontent.com/content_link/h78fWH1o3u1rZawKAHJ1sCDMyPojKjG6vG9txWXJAmFh7IjAP7RmsSK9wkGYHqyK/file?dl=1
Pragma: no-cache
Set-Cookie: locale=en; Domain=dropbox.com; expires=Tue, 23 Nov 2021 15:40:43 GMT; Path=/; secure
Set-Cookie: gvc=MTI0NzQ5NzUwMjAyMDAxMDQzMjU4MzEyODA1MTc0Mjg4NTg2MTg5; expires=Tue, 23 Nov 2021 15:40:43 GMT; httponly; Path=/; secure
Set-Cookie: __Host-js_csrf=beDoDaNB6TeHXCsDOo0_6Crt; expires=Sun, 24 Nov 2019 15:40:43 GMT; Path=/; secure
Set-Cookie: t=beDoDaNB6TeHXCsDOo0_6Crt; Domain=dropbox.com; expires=Sun, 24 Nov 2019 15:40:43 GMT; httponly; Path=/; secure
Set-Cookie: puc=; expires=Thu, 24 Nov 2016 15:40:43 GMT; httponly; Path=/; secure
User-Agent:
X-Content-Type-Options: nosniff
X-Dropbox-Http-Protocol: None
X-Dropbox-Request-Id: e61ad2838b672fa08c79be8546919b01
X-Frame-Options: DENY
X-Robots-Tag: noindex, nofollow, noimageindex
X-Xss-Protection: 1; mode=block
Strict-Transport-Security: max-age=15552000; includeSubDomains

```

---

<div class="post-metadata">

### Author: ![eriko](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eriko/32/1915_2.png) [@eriko](https://meta.discourse.org/u/eriko)
#### Post date: [November 28, 2016, 7:52pm UTC](https://meta.discourse.org/t/vagrant-1-8-7-will-not-download-image-reverting-to-1-8-6-will-work/53276/3 "2016-11-28T19:52:49Z")

</div>

Hmm. Curl also succeeds for me but I get the following when I  
vagrant up

```
==> default: Adding box 'discourse-16.04' (v0) for provider: virtualbox
    default: Downloading: https://www.dropbox.com/s/2132770g1e05c6d/discourse.box?dl=1
An error occurred while downloading the remote file. The error
message, if any, is reproduced below. Please fix this error and try
again.

```

I must have misinterpreted the error.

---

<div class="post-metadata">

### Author: ![eriko](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/eriko/32/1915_2.png) [@eriko](https://meta.discourse.org/u/eriko)
#### Post date: [November 29, 2016, 12:52am UTC](https://meta.discourse.org/t/vagrant-1-8-7-will-not-download-image-reverting-to-1-8-6-will-work/53276/4 "2016-11-29T00:52:35Z")

</div>

It seems that vagrant 1.8.7 is broken on OSX. Downgrading to 1.8.6 seems to have fixed the issue.
