Nginx logs and configuration issue with Airbyte connection

Slack Knowledge Base Q&A Platform Questions
, , , ,
1

Summary

User encountered a 502 error while attempting to create a connection via API in Kubernetes and seeks guidance on where to find nginx logs and configurations.


Question

Hi,

when trying to create a connection via forwarding from kubernetes:

http://localhost:8080/api/public/v1/connections

im getting the following response:

Error html { color-scheme: light dark; } 
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>

An error occurred.

Sorry, the page you are looking for is currently unavailable.
Please try again later.

If you are the system administrator of this resource then you should check the error log for details.

Faithfully yours, nginx.

Where to i have to look for nginx logs and configurations?

When trying it within the UI i get 502 that airbyte is unavailable and should try it again.


This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.

Join the conversation on Slack

['nginx-logs', 'kubernetes', '502-error', 'airbyte-connection', 'api']
2

For which pod have you run kubectl port-forward ...?

3

<http://app.kubernetes.io/name=webapp|app.kubernetes.io/name=webapp>

4

airbyte-webapp-78d8fdf595-glszp

5

since the api server is not available anymore

6

i get also validation errors if the connection configuration is incorrectm but when i start the call it takes a couple of minutes and it turns into 502 Bad Gateway, so my guess there is a downstream timeout/error

7

seems like the auto discovery for mongodb causes this problem i reduces the sample size and then it worked.

8

Search for environment variables HTTP_IDLE_TIMEOUT, READ_TIMEOUT
and annotations
<http://nginx.ingress.kubernetes.io/proxy-send-timeout|nginx.ingress.kubernetes.io/proxy-send-timeout>
<http://nginx.ingress.kubernetes.io/proxy-read-timeout|nginx.ingress.kubernetes.io/proxy-read-timeout>
on Slack

For my Airbyte deployments I have:

  env_vars:
    HTTP_IDLE_TIMEOUT: "1800s"

webapp:
  ingress:
    annotations:
      <http://nginx.ingress.kubernetes.io/proxy-send-timeout|nginx.ingress.kubernetes.io/proxy-send-timeout>: "1800"
      <http://nginx.ingress.kubernetes.io/proxy-read-timeout|nginx.ingress.kubernetes.io/proxy-read-timeout>: "1800"```
9

If that won’t help, then you need to investigate further. My favourite tool for quick inspections is k9s https://k9scli.io/topics/install/