Error creating connection in Airbyte with HTTP 504

Summary

After deploying self-hosted Airbyte via Docker and configuring NGINX for proxy-pass, encountering an error ‘An unknown error occurred. (HTTP 504)’ when trying to create a connection. Error message in airbyte-worker logs: ‘baseUrl is invalid.’ Seeking assistance on resolving this issue.


Question

Hey everyone,

I am newbie in Airbyte so I am little bit confused.

I tried to deploy self-hosted airbyte via docker and everything is ok. I fellow this instruction for deploy: https://docs.airbyte.com/deploying-airbyte/docker-compose
After deploy I also configured NGINX for proxy-pass to my airbyte. After that I went to my airbyte – tried to configured destination with my postgres server and test connection passed fine and my airbyte created new schema in my db. After that I went to configure BigQuery source – test connection passed fine too. So, I thought that everything fine but when I tried to create connection, I got an error:
An unknown error occurred. (HTTP 504)

I checked an airbyte-worker logs and saw this one:
io.temporal.failure.ApplicationFailure: message='baseUrl is invalid.', type='java.lang.IllegalStateException', nonRetryable=false
Somebody got errors like this? Maybe I need to configured something extra or missing some information in the guide?
I would appreciate any help,
Thank you!



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

["airbyte", "docker", "nginx", "http-504", "connection-error", "airbyte-worker", "baseurl-is-invalid"]

Hello <@U076W62QLKF> are you trying t deploy for the first time or upgrading from a previous version?

<@U02TQLBLDU4> Hi Marcos! It’s my first time deploy, I didn’t use any previous versions before

Other users reported the same issue but was related to upgrading. For new deployment it shouldn’t be the case.

You can follow more about that discussion here: https://github.com/airbytehq/airbyte/issues/38854 there is a workaround to edit env variables you could try

Yeah, downgrading version to 0.60.1 helped me, thanks for useful link!

<@U02TQLBLDU4> I will try, thank you!