Skip to main content
Version: v2.x

Troubleshooting Hasura GraphQL engine errors

Introduction

This section provides references that can help in troubleshooting errors when developing with Hasura.

Logs

In order to find out about the origins of an error, it can be helpful to check the logs.

Metrics and distributed tracing in Hasura Cloud

Hasura Cloud includes metrics and distributed tracing which makes troubleshooting faster. For more information, see Metrics and Tracing in Hasura Cloud.

Server logs

For errors that come from the Hasura server, server logs will give you more insights. For details on how you can access these logs, as well as different log types, visit this page.

Console logs

Should there be any error coming from the Hasura console UI, they will show up in the Browser dev tools.

Remote service logs

Errors can come from a remote service, such as remote schemas, events or actions. In this case, check the errors of the respective remote service. For actions, check out this debugging page.

GitHub issues

It's possible that someone with the same problem has created a GitHub issue on the Hasura repo. If you don't come across an issue with solution in your search, feel free to create a new issue.

Hasura blog

The Hasura blog contains a lot of useful resources including tutorials. You can use the search functionality to find what you're looking for.

YouTube

If you prefer to watch tutorials in the form of videos, check out the Hasura Youtube channel.

Database docs

If you come across a database error, it will be helpful to check their logs:

Client-side

SSL certificate errors

SSL certificate errors occur when a web browser can't verify the SSL certificate installed on a site. For SSL errors such as:

ERROR:
{
code: EPROTO,
errno: EPROTO,
message:
request to <graphql-api> failed, reason: write EPROTO <....> alert handshake failure:..<...>: SSL alert number 40
}

Follow the steps below to try and resolve the issue:

  1. Whitelist the EPROTO error code (in client-side code).
  2. Allow the retry logic to be activated.
  3. Monitor the system for improvements or changes in the reconciliation process.

Discord

If you didn't find a solution in any of the above mentioned sections or if you prefer to troubleshoot with the community, feel free to join our Discord server. Other users might have come across the same issues, and the Hasura community on Discord is very active and helpful.