Troubleshooting Hasura GraphQL engine errors
This section provides references that can help in troubleshooting errors when developing with Hasura.
In order to find out about the origins of an error, it can be helpful to check the 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.
Should there be any error coming from the Hasura console UI, they will show up in the Browser dev tools.
Remote service logs
The Hasura blog contains a lot of useful resources including tutorials. You can use the search functionality to find what you're looking for.
If you prefer to watch tutorials in the form of videos, check out the Hasura Youtube channel.
If you come across a database error, it will be helpful to check their logs:
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:
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:
- Whitelist the EPROTO error code (in client-side code).
- Allow the retry logic to be activated.
- Monitor the system for improvements or changes in the reconciliation process.
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.