No you are not going crazy, S3 is down


Which is affecting Meteor’s docs —

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.

Thank goodness we don’t host our critical javascript files on S3.

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… :smirk:

1 Like

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; server returned [504]
  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, 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. :wink:

You think YOU were going crazy? This happened just when I had edited .meteor/release to go from to!


1 Like

Okay, works for me now.

1 Like