Ishan Anilbhai Koradiya
09/26/2024, 6:05 AMuser
09/26/2024, 6:06 AMjson { "type": "service_account", "project_id": "YOUR_PROJECT_ID", "private_key_id": "YOUR_PRIVATE_KEY", ... }
If you're using Airbyte Open Source, you'll need to create a GCP project, enable the Google Sheets API in your GCP project, and create a Service Account Key with access to the Spreadsheet you want to replicate. If you're still facing issues, could you please provide more details about the problem? That would help me assist you better. Sources: - [Google Sheets Source Setup](https://docs.airbyte.com/integrations/sources/google-sheets#set-up-the-google-sheets-connector-in-airbyte) - [Google Sheets Source Prerequisites](https://docs.airbyte.com/integrations/sources/google-sheets#google-sheets) - [Google Sheets Source Setup for Airbyte Open Source](https://docs.airbyte.com/integrations/sources/google-sheets#for-airbyte-open-source)Ishan Anilbhai Koradiya
09/26/2024, 6:07 AMuser
09/26/2024, 6:07 AMuser
09/26/2024, 6:07 AMHTTP_IDLE_TIMEOUT
and READ_TIMEOUT
environment variables. Here's how you can do it: yaml server: extraEnvs: - name: HTTP_IDLE_TIMEOUT value: 20m - name: READ_TIMEOUT value: 30m
This configuration sets the idle timeout to 20 minutes and the read timeout to 30 minutes. You can adjust these values as per your requirements. If you're still facing issues, it would be helpful if you could provide more details about the error message you're seeing or any relevant logs. This would help in diagnosing the problem more accurately. Source: [Scaling Airbyte After Installation - Schema Discovery Timeouts](https://docs.airbyte.com/enterprise-setup/scaling-airbyte#schema-discovery-timeouts)Ishan Anilbhai Koradiya
09/26/2024, 6:09 AMAirbyte is temporarily unavailable. Please try again. (HTTP 502)
user
09/26/2024, 6:09 AMuser
09/26/2024, 6:09 AMHTTP 502
error. This error typically indicates that a server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request. One possible reason for this could be that the server is taking too long to respond due to the large response for timesheet_details, causing a timeout. You might want to check the server timeout time and consider increasing it if necessary. Additionally, to help us understand better if the error is related to the platform or the specific API you're trying to connect to, could you try connecting to other sources like Github, CSV, or a local Postgres database and see if you encounter the same issue? If the issue persists, it would be helpful to check the logs for any errors. You can do this by running kubectl logs <pod-name>
for the relevant Airbyte pods in your Kubernetes cluster. Sources: - [Facing Issue while trying to Hit Custom API in Airbyte](https://github.com/airbytehq/airbyte/discussions/34557) - [Hubspot source check fail](https://github.com/airbytehq/airbyte/discussions/37798) - [502 Timeout When Creating Connection](https://discuss.airbyte.io/t/1207) - [Self-hosted Airbyte in Docker stuck and will not trigger sync](https://github.com/airbytehq/airbyte/issues/44833) - [Nginx reverse proxy tells 502 until containers restarted](https://discuss.airbyte.io/t/3239)