502 Errors from Graphiql

ros
cloud

#1

Currently when I try to run queries from GraphiQL it waits for a very long time, then says:

<html>
<head><title>502 Bad Gateway</title></head>
<body>
<center><h1>502 Bad Gateway</h1></center>
<hr><center>nginx/1.15.5</center>
</body>
</html>
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->
<!-- a padding to disable MSIE and Chrome friendly error page -->

Is there a status page or more information about what’s going on / when it’ll be resolved? I’m able to connect from Realm Studio, just the GraphQL endpoint is playing up.


#2

I completely deleted the entire instance, then created my realm from scratch, and the new realm shows the same behaviour. It must be something the GraphQL endpoint doesn’t like with my schema, but I can’t figure it out. Logs don’t show any errors except this:

sync-client: Connection[18]: Session[18]: Received: ERROR(error_code=211, message_size=27, try_again=0)
3:07:45 PM
context: Object
 level: "info"
 timestamp: "2018-12-14T04:07:45.304Z"

Example schema which produces the problem is:

exports.DataQuery = {
  name: 'DataQuery',
  primaryKey: 'uuid',
  properties: {
    uuid: 'string',
    description: 'string?',
    components: 'DataQueryComponent[]',
    createdAt: 'date',
    updatedAt: 'date',
    entityType: 'string',
    entityId: 'string?',
    sortField: 'string?',
    sortDirection: 'string?'
  }
}

exports.DataQueryComponent = {
  name: 'DataQueryComponent',
  primaryKey: 'uuid',
  properties: {
    uuid: 'string',
    field: 'string',
    operator: 'string?',
    value: 'string',
    typeSpecifier: 'string?'
  }
}

exports.Trial = {
  name: 'Trial',
  primaryKey: 'uuid',
  properties: {
    uuid: 'string',
    name: 'string',
    description: 'string?',
    inclusionCriteria: 'DataQuery[]',
    exclusionCriteria: 'DataQuery[]',
    createdAt: 'date',
    updatedAt: 'date'
  }
}

#3

I tried re-creating it again with a simpler schema and am getting the same problem. I don’t know what else to try here.

The instance I’m referring to is https://enome-testing.us1a.cloud.realm.io, default realm.


#4

@kevin I am getting a 403 denied when I go to
https://enome-testing.us1a.cloud.realm.io/graphql/explore/%2F__admin

{“type”:“https://realm.io/docs/object-server/problems/access-denied",“title”:"The path is invalid or current user has no access.”,“status”:403,“detail”:“Authorization header is missing.”,“code”:614}

Because you need to attach a valid auth token as documented here:


#5

@kevin

The link worked for me to get to your Realm.

However - PLEASE open a support ticket for that 502 error. It may be unrelated but we have those same 502 Bad Gateway errors consistently for the past 2+ months (which we have an ongoing ticket for), and may be a known but hard-to-reproduce issue for the Realm team.


#6

@ianward, as per the original post, I’m not getting a 403, I’m getting a 502.

@jay, I’m still getting the 502 when I use Graphiql (again, as per the original post), so I’ll create a ticket.