Meteor update / meteor add 500 Internal Server Error

help
1

I’m trying to determine if something is wrong with my install or if something is wrong with the meteor servers. Any package install (not NPM, just meteor) ends in an internal server error 500.

*** If someone can just try on their machine and report back… that would help a lot. I just don’t have much to go off of as far as errors go:

/mt-os.osx.x86_64/dev_bundle/lib/node_modules/meteor-promise/promise_server.js:218
throw error;
^
Error: Internal server error [500]
at Connection._livedata_result (packages/ddp-client/common/livedata_connection.js:1519:9)

2 Likes
2

same problem here. Just tried updating and got a 500 error.

3

I can confirm the same here - getting 500 errors with both meteor update/add.

4

Thank you. This is actually a relief. Distract myself for a few hours and the problem will go away. Was fearing needing to fix it.

HEY METEOR, there’s an internal server error (and your system status says the package server is up so that might need some work too).

5

You might try @ing someone from MGD, otherwise your just shouting into the abyss.

@benjamn, @sashko

2 Likes
6

Looks like they took notice on GitHub =)

1 Like
7

@mainstreetmower Thanks for the reminder about the status page (easy to forget as we’re focusing on the investigation itself): http://status.meteor.com/

Please refer to the GitHub issue linked above for further discussion, and/or subscribe to updates on the status page.

Thanks for your patience, everyone!

1 Like
8

We believe this problem to be resolved and we have updated the status page accordingly. We will continue to monitor the stability of the package server.

2 Likes
9

Ah yes… the Meteor package server experiences the joys of being an app hosted on Galaxy. Random outage for no known reason.

10

anyone else experiencing this now? I was able to replicate this again in our CI servers and locally.

11

We too - in Pipeline & locally

12

Seems to be fixed again! :partying_face:

2 Likes