Localhost refused to connect

is this your first time deploying Airbyte: Yes
OS Version / Instance: MacOS Monterey, instance built through GCP , E2 medium running Debian 10
Memory / Disk:2 vCPUs, 4GB memory
Deployment : Docker
Airbyte Version : latest, or whichever is used for deploying to GCP in the instructions on On GCP (Compute Engine) - Airbyte Documentation
Source name/version : not there yet
Destination name/version : not there yet
Step : Getting started
Description : Having trouble launching localhost:8000 after having installed gcloud, docker, docker-compose and airbyte to the instance. any browser I visit is throwing the same “connection refused” or “refused to connect” error

Hi @Parth ,
Did you port-forward the GCP host to your localhost on port 8000?
This is suggested in the guide you linked:
gcloud --project=$PROJECT_ID beta compute ssh $INSTANCE_NAME -- -L 8000:localhost:8000 -N -f

As I also mentions on Slack, do you confirmed that you upsized your instance to at least a 16GB/8cpu/30GB disk sizing?

Hi @alafanechere
Yes, I did the the port forwarding and I confirm that I have upsized the instance although the guide specifies that e2 medium (2vCPU/4GB memory) should be sufficient for testing out airbyte. This is the current configuration : 8CPU/16GB Memory

Just ensuring we are on the same page. You used the command in your terminal rather than the compute engine one right?

Yes, I ran it on my machine’s terminal, not the compute engine one.

Hey @Parth when you SSH into your VM, can you reach http://localhost:8000 with curl? We first need to understand if all the services are started correctly on your host before figuring out external networking concerns.

Yes, I am able to reach localhost with curl
Screenshot 2022-04-05 at 9.31.07 PM

1 Like

And what’s the output of the same curl command but ran from your laptop after having set up port forwarding using:

gcloud --project=$PROJECT_ID beta compute ssh $INSTANCE_NAME -- -L 8000:localhost:8000 -N -f

Hi there from the Community Assistance team.
We’re letting you know about an issue we discovered with the back-end process we use to handle topics and responses on the forum. If you experienced a situation where you posted the last message in a topic that did not receive any further replies, please open a new topic to continue the discussion. In addition, if you’re having a problem and find a closed topic on the subject, go ahead and open a new topic on it and we’ll follow up with you. We apologize for the inconvenience, and appreciate your willingness to work with us to provide a supportive community.