Which is affecting Meteor’s docs — http://status.meteor.com/incidents/psdfyfv1kz4s
Galaxy deployment process apparently depends on S3 as we get 502 bad gateway error when trying to meteor deploy. (us-east-1 region) Our servers are still up and running fine though we can’t re-point our image assets to non-S3 hosts.
I know cloudfront got hit with a bunch of password stolen this week… wondering if somebody got amazon passwords or something else loosely related.
Actually, I was almost about to go crazy…
I can’t even build my app on my developer machine!
meteor build /dev/shm/android_build/mmks --server=http://localhost:3000/;
Gets me …
Error: Could not get https://warehouse.meteor.com/builds/L2z2ZWho3X7SAP2N3/1473815125395/F2PW2Yhhrg/htmljs-1.0.11-os+web.browser+web.cordova.tgz; server returned  at Error (native) at Object.getUrlWithResuming (/tools/utils/http-helpers.js:495:13) at /tools/packaging/tropohouse.js:483:34 at /tools/utils/buildmessage.js:359:18 at [object Object].withValue (/tools/utils/fiber-helpers.js:89:14)
s3 just came back 3 seconds ago for me, so hopefully shoul dbe okay soon
Sad to say,
https://warehouse.meteor.com/ still pukes when I try to run my build.
For me it works again.
Galaxy still not working on my end:
Error deploying application: Internal error
Fixed that for you.
You think YOU were going crazy? This happened just when I had edited
.meteor/release to go from
Okay, works for me now.