Unauthorized errors when clicking 'get started' behind nginx proxy

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

Summary

Airbyte setup behind nginx proxy causing unauthorized errors when clicking ‘get started’. Possible issue with proxy configuration.


Question

I’ve set up airbyte (using abctl) behind nginx and am able to load the main page, but I’m getting unauthorized errors when I try to click “get started”. I think this is maybe due to the proxy configuration? Any idea how I can get this working? My nginx proxy config is as follows:

  listen 443 ssl;
  server_name <http://my.domain.com|my.domain.com>;
  client_max_body_size 200M; 
  ssl_certificate /etc/ssl/certs/airbyte.crt.pem;
  ssl_certificate_key /etc/ssl/certs/airbyte.key.pem;

  location / {
    proxy_pass <http://localhost:8000>;
    proxy_set_header Cookie $http_cookie; 
    proxy_read_timeout 3600;
  }
}```

<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/p1725392050319629) if you want 
to access the original thread.

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

<sub>
["airbyte", "nginx-proxy", "unauthorized-errors", "proxy-configuration"]
</sub>
2

or is there a new way to do this with abctl

3

Hey Jett, I’m not super pro with nginx and ask the deployment team some help!

4

<@U06Q97T576V> please check docs: https://docs.airbyte.com/deploying-airbyte/integrations/ingress

5

You can create a values.yaml and apply to your abctl deployment

6

Any guidance on how to configure that with https? Would definitely be helpful to add to the docs

7

btw the nginx configuration is still listed here: https://docs.airbyte.com/operating-airbyte/security

8

Seems like it still would be the easiest way to achieve what I would like to do, but not sure what I’m missing since that configuration no longer works

9

I cannot seem to get the values working with:

  ingress:
    enabled: true
    annotations:
      <http://nginx.ingress.kubernetes.io/ssl-redirect|nginx.ingress.kubernetes.io/ssl-redirect>: "true"
      <http://nginx.ingress.kubernetes.io/backend-protocol|nginx.ingress.kubernetes.io/backend-protocol>: "HTTP"
    hosts:
      - host: my.domain
        paths:
          - path: /
            pathType: ImplementationSpecific
    tls:
      - secretName: airbyte-https
        hosts:
          - my.domain```
the kind cluster doesn't even seem to expose 443