Timeout error 502 with Facebook-pages source connector in Airbyte OSS

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

Summary

The user is facing a timeout error 502 when using the Facebook-pages source connector in Airbyte OSS. Other connections are working fine, indicating the issue might be with the connector. The user has verified credentials and tried different versions of the connector without success. The user is looking for guidance on troubleshooting the issue.


Question

Hello!

I am trying to use the source connector facebook-pages but I am getting a timeout error 502 .

I am using airbyte OSS. version 0.63.3 .

Facebook-pages version: I have tried with all available, getting same error.

Creating other connections are working very fast, so, I suspect that the problem is in the connector.

I have tried the page token and page id in Python with the request library and it is working fine, so the credentials are not the problem.

Any idea what is going on? Do you know what I can do to better understand what is going on?

I see that a pod is created with 4 containers, but any container is giving me any relevant information


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

["timeout-error-502", "facebook-pages-connector", "airbyte-oss", "troubleshooting"]
2

what deployment do you have? abctl? helm chart with kubernetes?

probably you need to increase timeouts like here:
https://airbytehq.slack.com/archives/C021JANJ6TY/p1721284086969479?thread_ts=1721282163.771559&cid=C021JANJ6TY

it might be a situation that discovery step for that connector takes longer time and nginx “cuts” request due to shorter timeout and returns HTTP 502

3

helm chart yes, the pod takes more than 7 minutes to finish, so I don´t know if increaseing timeout will help

4

Can you try first, and doubt later?
I had issues with BigQuery connector that discovery process took ~17 minutes and pod was still running even after I got HTTP 502 in a browser.
After increasing timeouts to 30 minutes HTTP 502 disappeared

5

I can try yes.

I didn’t understand very well what I need to do.

Add this env variable:

HTTP_IDLE_TIMEOUT: 1800s
And then increase the timeout in the load balancer? I am using gke, so my load balancer is google cloud load balancer.

Do I have to modify any parameters there?

6

Yes, you need to increase timeouts on load balancer as well