GraphQL error 500 when deploying

Dev Support
1

We’ve suddenly started getting a GraphQL error 500 when trying to deploy to our development and UAT environments using 8base deploy

error: GraphQL Error (Code: 500): {“response”:{“message”:“Internal server error”,“status”:500},“request”:{“query”:"\n query DeployStatus($buildName: String!) {\n deployStatus(buildName: $buildName) {\n status, message\n }\n }",“variables”:{“buildName”:“6000ef4f7df9310008f49367_1617158556829”}}}

The last time we were able to deploy was on the 29th of March, so I tried deploying an old commit to see if it was something in our code… but no dice.

1 Like
2

Getting same error on 8base deploy

3

Potentially related: Getting a GQL 500 when creating a new CLI environment:

GraphQL Error (Code: 500): {"response":{"message":"Internal server error","status":500},"request":{"query":"\n query status($sessionId: String!) {\n status: asyncSessionStatus(sessionId:$sessionId) { status message }\n }\n ","variables":{"sessionId":"XXX"}}}

However, the creation of the environment seems to have taken place - it can be selected inside the 8base app.

4

Same thing happens when running other 8base CLI commands, for example 8base backup create:

GraphQL Error (Code: 500): {"response":{"message":"Internal server error","status":500},"request":{"query":"\n    query status($sessionId: String!)  {\n      status: asyncSessionStatus(sessionId:$sessionId) { status message }\n    }\n  ","variables":{"sessionId":"ckmx5ls3a000409ma2n2i4ayi"}}}
5

Seems to have been resolved now.

1 Like
6

This issue is reoccurring. Anyone have any experience with it and a solution?
Thanks

7

Hello!

Despite the fact that all the errors in the topic are related to deploy, their causes are different. You can find the solution for @PCSupport case resolved via our service-desk below. It will help those who use pre-install scripts in package.json

The quickest temporary workaround for you to make deploy work is to delete preinstall script from your package.json

The deal is that there is no preinstall-script.js file in your project (you store it outside of the project and run it locally), but it probably would not work if you move it inside the project because of the server-side issue. We know about it and have been already working on the solution. We will try to release a hot-fix asap.

Sorry for the inconvenience.

Lada Kokotova | Technical Support Engineer