Summary
The user encountered a 502 Bad Gateway error when trying to access API endpoints, indicating potential server-side issues. The response suggests checking error logs for further diagnostics.
Question
I tried both of those endpoints before but all I got was error 502 Bad Gateway and this response:
<html>
<head>
<title>Error</title>
<style>
html { color-scheme: light dark; }
body { width: 35em; margin: 0 auto;
font-family: Tahoma, Verdana, Arial, sans-serif; }
</style>
</head>
<body>
<h1>An error occurred.</h1>
<p>Sorry, the page you are looking for is currently unavailable.<br/>
Please try again later.</p>
<p>If you are the system administrator of this resource then you should check
the error log for details.</p>
<p><em>Faithfully yours, nginx.</em></p>
</body>
</html>```
<br>
---
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1733972594204689) if you want
to access the original thread.
[Join the conversation on Slack](https://slack.airbyte.com)
<sub>
['502-bad-gateway', 'api-endpoints', 'error-response', 'nginx']
</sub>