b
Any insights..
u
Hi Bala, this image is displayed typically when you start airbyte and visit the UI before the server has had time to start up
u
if you visit the UI now do you still see this issue?
u
yes
u
and i see the init and seed are not starting too
u
Also, it’s expected that the
seed
and
init
images exit
u
ok , good to know
u
they’re just images used for bootstrapping
u
how much time typically the startup take?
u
should be no more than 20 seconds
u
or is there a log area i can check
u
can you force refresh the airbyte UI
u
cmd-shift-r on chrome mac
u
no luck. the server is remote Ubuntu …
u
got it. So Airbyte is running on a remote Ubuntu and not locally?
u
yes
u
and i am doing port forwarding using VS Code.
u
can you also port forward 8001 to local 8001?
u
ok doing now
u
now it worked
u
i see this on 8001 though
u
8000 worked.
u
8001 is the API server, 8000 is the UI
u
Got it.
u
surprising it needed the local route - expected it will work internally
u
thanks @s
u
Yeah, I agree that it’s not ideal
u
out of curiosity, were you following one of the setup guides?
u
or did you go for a DIY installation?
u
skipped to
u
as i have already have ec2 system where i am running other docker images
u
and didnt use the tunnel from thedocument
u
and used VS Code Tunnel - DIY
u
missed the subtle tunnel step from this ssh
u
hope that helps
u
thanks for help @s
u
Got it — thanks for the explanation. Glad you’re up and running now! Let us know if there is anything else we can help wtih
u
Yep will do.
u
I had the same problem while using the GCP guide. I expect some ports have to be opened in the firewall?