Omnitruck 404 Issues

Were there any recent changes to omnitruck? The following was working earlier today but is not now:

curl -I ""
HTTP/1.1 404 Not Found
Content-Type: text/html;charset=utf-8
Server: nginx/1.4.6 (Ubuntu)
X-Content-Type-Options: nosniff
X-Frame-Options: SAMEORIGIN
X-XSS-Protection: 1; mode=block
Content-Length: 0
Accept-Ranges: bytes
Date: Wed, 30 Mar 2016 23:42:57 GMT
Via: 1.1 varnish
Age: 0
Connection: keep-alive
X-Served-By: cache-lax1421-LAX
X-Cache: MISS
X-Cache-Hits: 0

The current channel gets nuked from time to time. You want to be using the stable channel for installing released builds.

hmm, OK, so this is actually getting generated by Vagrant, I just copied the URL it was trying. I’ll have to see whats involved in making that change. Do we know for sure if current did infact get nuked today?

It did, and it was a bug in Vagrant that it defaults to using the current channel. This will be fixed in the next release of Vagrant but for now just specify the stable channel in your Vagrantfile.

As usual @coderanger you’re spot on, that worked.

Build artifact retention for 'current' is 30 days.

1 Like