Reverse Proxy with Traefik for Airbyte

Slack Knowledge Base Q&A API, Terraform and Other Topics
, , , ,
1

Summary

The user is trying to set up a reverse proxy with Traefik for Airbyte but is encountering a Gateway Timeout issue. They have added labels in the Traefik configuration for the airbyte-proxy service.


Question

Helllo :wave:

I am trying to do a reverse proxy with Traefik, has anyone done this ?

I have seen the [https://docs.airbyte.com/operating-airbyte/security#network-security|doc] about reverse proxy with Nginx, but it’s not helping me in my case

I have to redirect the request to the airbyte-proxy docker compose service container, on the port 8000 right ? I get a a Gateway Timeout, which means Traefik cannot connect to the container from my understanding.
Am I missing something ?

In traefik termes, I added those labels in the :

...
labels:
  - "traefik.enable=true"
  - "traefik.http.services.airbyte.loadbalancer.server.port=8000"
  - "traefik.http.routers.airbyte.rule=Host(`<http://airbyte.domain.com|airbyte.domain.com>`)"
  - "traefik.http.routers.airbyte.tls.certresolver=le" # &lt;- certificate from LetsEncrypt```
Thanks in advance

<br>

---

This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. [Click here](https://airbytehq.slack.com/archives/C021JANJ6TY/p1718030028232709) if you want 
to access the original thread.

[Join the conversation on Slack](https://slack.airbyte.com)

<sub>
["reverse-proxy", "traefik", "airbyte", "gateway-timeout", "docker-compose", "labels"]
</sub>
2

For futur people searching this topic. We’ve managed to make this work by linking the “airbyte-proxy” to the same network as the docker service “traefik”, in our case it was called “internal”.

Which mean we didn’t need to airbyte_public

So, the airebyte-proxy looks like this:

      - airbyte_internal
      - internal```
And at the end of the docker compose

```networks:
  airbyte_internal:
  internal: # Which is the same network as Traefik is on
    external: true # Because the network is created from another container```