Webui at port 8000 not showing

  • Is this your first time deploying Airbyte?: Yes
  • OS Version / Instance: AL2 latest
  • Memory / Disk: you can use something like - NA
  • Deployment: Are you using Docker or Kubernetes deployment? Docker
  • Airbyte Version: What version are you using now? : Docker latest container images
  • Source name/version: NA
  • Destination name/version: NA
  • Step: The issue is happening during the startup?-
    Description: I have a docker instance on the EC2 running with the airbyte sister images (all the microservices). All services are active and containers are running. But when I hit the port 8000 for the web UI, i am prompted for the login/password but immediately the ngnix welcome is displayed instead of the Airbyte UI. I’m wondering what may be wrong? I am pretty sure it;s connected with few ports/Security grps that may have to be opened, but what else? Can somebody guide me through what I may be missing?

I did open the 8000 port on the inbound and only the ngnix banner is shown. I believe internally there is some traffic that is being exchanged between the containers since airbyte shows some network setup as well. But I think from Security Group on the EC2 pov - something needs to change. Anybody if they know or any settings are reuquired on ngnix ; pls help.

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.
The Community Assistance Team

Can you please check the problem definition ; and update? I’ve been as verbose as possible :).
Any logs that you want, please let me know.