Nginx reverse proxy tells 502 until containers restarted

Platform, Deploy & Infra Issues
,
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Almalinux 8
  • Memory / Disk: 55G
  • Deployment: Docker
  • Airbyte Version: 0.40.19
  • Source name/version: #
  • Destination name/version: #
  • Step: system startup
  • Description:

Hello, after starting the machine, the nginx proxy which is used to forward port 8000 to 80 with nginx basic auth is always telling 502 Bad Gateway- and getting these log entries in nginx error.log:

2022/11/18 15:28:20 [error] 1095#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: myIP, server: _, request: "GET /api/v1/health HTTP/1.1", upstream: "http://127.0.0.1:8000/api/v1/health", host: "airbyteIP", referrer: "http://airbyteIP/api/v1/health"
2022/11/18 15:28:40 [error] 1095#0: *1 user "airbyte": password mismatch, client: myIP, server: _, request: "GET /api/v1/health HTTP/1.1", host: "airbyteIP", referrer: "http://airbyteIP/api/v1/health"
2022/11/18 15:28:40 [error] 1095#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: myIP, server: _, request: "GET /api/v1/health HTTP/1.1", upstream: "http://127.0.0.1:8000/api/v1/health", host: "airbyteIP", referrer: "http://airbyteIP/api/v1/health"
2022/11/18 15:28:47 [error] 1095#0: *1 user "airbyte": password mismatch, client: myIP, server: _, request: "GET /workspaces/fd1eb391-8908-4a90-8200-4bdbc050d615/connections HTTP/1.1", host: "airbyteIP"
2022/11/18 15:28:48 [error] 1095#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: myIP, server: _, request: "GET /workspaces/fd1eb391-8908-4a90-8200-4bdbc050d615/connections HTTP/1.1", upstream: "http://127.0.0.1:8000/workspaces/fd1eb391-8908-4a90-8200-4bdbc050d615/connections", host: "airbyteIP"
2022/11/18 15:28:48 [error] 1095#0: *1 user "airbyte": password mismatch, client: myIP, server: _, request: "GET /favicon.ico HTTP/1.1", host: "airbyteIP", referrer: "http://airbyteIP/favicon.ico"

This happens after successfully logging in past the nginx proxy with it’s own credentials.

But if I then just restart the containers by using sudo docker compose restart, everything is working as is it should. Simply reloading the page in browser gets me to airbyte ui.

Sorry for that basic question, but i wonder what is going wrong here?
I have basic auth on airbyte side disabled by setting "" as value for BASIC_AUTH_USERNAME and BASIC_AUTH_PASSWORD.
Would there be need of some additional setting?
This started happening with version 0.40.18 or 17 I think. Before it was working fine :man_shrugging:t3:

greetings

2

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
Best,
The Community Assistance Team

3

Hi, @gaurang! Thanks so much for your patience - I was out of the office over the long Thanksgiving weekend.

I’m not the expert in nginx, so if I can’t help you soon I’ll take this to the team on Wednesday. Are you using the provided nginx config, or a custom one?

4

This seems to be fixed with version 0.40.23 :+1::+1:

(maybe it was 3f8ba45 Add restart to airbyte/proxy (#19791) / issue #19790 )

greetings

5

Hello mmoole, it’s been a while without an update from us. Are you still having problems or did you find a solution?