I'm sorry to hear that you're experiencing issues with setting up a Postgres destination in Airbyte. The HTTP 504 error typically indicates a gateway timeout error. This could be due to a variety of reasons such as resource constraints, network issues, or configuration problems. Here are a few troubleshooting steps you can take: 1.
Upgrade to the latest Airbyte version and redeploy Airbyte: Make sure you're using the latest version of Airbyte and the Postgres connector. Upgrading might resolve the issue if it's caused by a bug that has been fixed in a newer version ([source](
https://discuss.airbyte.io/t/376)). 2.
Check your resource allocation: If you're running Airbyte in a Docker environment, ensure that Docker has sufficient resources. Some users have resolved similar issues by increasing the CPU and memory allocated to Docker ([source](
https://github.com/airbytehq/airbyte/issues/42135)). 3.
Check your network settings: If you're running Airbyte on Kubernetes, there could be issues with how your nodes are set up or how data is being shared across nodes. You might also want to check the memory consumption when running the sync ([source](
https://discuss.airbyte.io/t/376)). 4.
Increase the timeout on the ingress proxy: If you're using Kubernetes, you might need to increase the timeout on the ingress proxy. This can be done by editing the ingress definition and adding the appropriate annotations ([source](
https://github.com/airbytehq/airbyte/issues/45156)). 5.
Check your Postgres connection details: Ensure that the connection details for your Postgres destination are correct. This includes the host, port, username, password, and database name ([source](
https://airbyte.com/tutorials/postgres-replication#step-2)). If none of these steps resolve your issue, I would recommend reaching out to the Airbyte community on their [discussion forum](
https://discuss.airbyte.io/) or [GitHub](
https://github.com/airbytehq/airbyte/issues) for further assistance.