hi folks, glad i found out this slack channel. I h...
# replication-troubleshooting
a
hi folks, glad i found out this slack channel. I have a container based deployment in AWS and trying to hit the airbyte UI. When I do that using the 8000, port I am able to see ngnix and not the airbyte UI. I am pretty sure it's due to the SG inbound rules that is out there.. Wondering what I am missing.
I'm not using ssh to connect but using SSM to directly hop on to the terminal n deployed there. Should not really affect. Also have opened port 8000-8003 and so on.for inbound.
What else I am missing? - any help to see the airbyte UI will be highly appreciated.
Is it required to have ssh configured? I am using just the direct console based.
s
Hey @A BK, sorry for the delay in response. Were you able to find a solution and access the airbyte-ui?
a
actually nope. I do see the login but ngnix default page gets displayed.
I am thinking if I need to open any ports etc, I will be able to post the details tomorrow on this..(SG changes).
s
hey @A BK if you're still running into this, can you check if logging in helps? The default login is
airbyte
/
password
If you're able to see nginx then i don't think it's a routing issue, sounds like airbyte may not have started up correctly. It might be helpful to redeploy or try a new version
a
I did check that airbyte has started (all the docker ps processes). I am going to pull the latest docker and ping you here.
thanks much.