# Error when lauching node app: "Error fetching base layers \[...\] connect tcp connection was refused"

**URL:** <https://community.fly.io/t/error-when-lauching-node-app-error-fetching-base-layers-connect-tcp-connection-was-refused/7961>\
**Category:** Questions / Help\
**Created:** [October 18, 2022, 2:53pm UTC](https://community.fly.io/t/error-when-lauching-node-app-error-fetching-base-layers-connect-tcp-connection-was-refused/7961 "2022-10-18T14:53:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![clemwo](https://avatars.discourse-cdn.com/v4/letter/c/76d3ee/32.png) [@clemwo](https://community.fly.io/u/clemwo)\
**Post date:** [October 18, 2022, 2:53pm UTC](https://community.fly.io/t/error-when-lauching-node-app-error-fetching-base-layers-connect-tcp-connection-was-refused/7961/1 "2022-10-18T14:53:17Z")

</div>

Hi everyone,

I’m trying to launch my simple backend to [fly.io](http://fly.io) and follow the getting started guide. After executing “flyctl launch” I get the following error:

> An existing fly.toml file was found for app dawn-snowflake-1079  
> App is not running, deploy…  
> Deploying dawn-snowflake-1079  
> ==\> Validating app configuration  
> → Validating app configuration done  
> Services  
> TCP 80/443 ⇢ 8080  
> Remote builder fly-builder-muddy-frost-2787 ready  
> ==\> Building image with Buildpacks  
> → docker host: 20.10.12 linux x86\_64  
> 20: Pulling from heroku/buildpacks  
> Digest: sha256:170f711f7485fd510161bde9f2cfae92b6c7061d8ff4818a31d4e202edb006f1  
> Status: Image is up to date for heroku/buildpacks:20  
> 20-cnb: Pulling from heroku/heroku  
> Digest: sha256:26ec15fdf56a83cf90ecbf0efdb0bd41a446b5051d2d65163b1a22d5554f7299  
> Status: Image is up to date for heroku/heroku:20-cnb  
> Error fetching base layers: saving base image with ID “sha256:b2cdf0f40ce29f75cd7eef4f17dfffbabe797afacb2d802916ccbcb131eb9930” from the docker daemon: error during connect: Get “http://[fdaa:0:bdff:a7b:c6ef:71f3:63a0:2]:2375/v1.41/images/get?names=sha256%3Ab2cdf0f40ce29f75cd7eef4f17dfffbabe797afacb2d802916ccbcb131eb9930”: connect tcp [fdaa:0:bdff:a7b:c6ef:71f3:63a0:2]:2375: connection was refused

I already changed my dns server to 1.1.1.1 and turned off any vpn I have here however the problem still persists. Also tried to use another computer and get the same error.  
Im now trying to use the [GitHub - fly-apps/hellonode-builtin: A minimal Fly example Node application for use in tutorials](https://github.com/fly-apps/hellonode-builtin) example.

I would greatly appreciate any help. Thanks!

---

<div class="post-metadata">

**Author:** ![clemwo](https://avatars.discourse-cdn.com/v4/letter/c/76d3ee/32.png) [@clemwo](https://community.fly.io/u/clemwo)\
**Post date:** [October 19, 2022, 9:24am UTC](https://community.fly.io/t/error-when-lauching-node-app-error-fetching-base-layers-connect-tcp-connection-was-refused/7961/2 "2022-10-19T09:24:57Z")

</div>

Now I get the following error. Apparently the same one that other people already had: [Error failed to fetch an image or build from source: error rendering push status stream: unauthorized: not allowed - #29 by iragsdale](https://community.fly.io/t/error-failed-to-fetch-an-image-or-build-from-source-error-rendering-push-status-stream-unauthorized-not-allowed/5042/29)

> ==\> Verifying app config  
> → Verified app config  
> ==\> Building image  
> Remote builder fly-builder-muddy-frost-2787 ready  
> ==\> Building image with Buildpacks  
> → docker host: 20.10.12 linux x86\_64  
> 20: Pulling from heroku/buildpacks  
> Digest: sha256:170f711f7485fd510161bde9f2cfae92b6c7061d8ff4818a31d4e202edb006f1  
> Status: Image is up to date for heroku/buildpacks:20  
> 20-cnb: Pulling from heroku/heroku  
> Digest: sha256:26ec15fdf56a83cf90ecbf0efdb0bd41a446b5051d2d65163b1a22d5554f7299  
> Status: Image is up to date for heroku/heroku:20-cnb  
> Error failed to fetch an image or build from source: failed to write image to the following tags: [pack.local/builder/6b72646d666365666a73:latest: io: read/write on closed pipe]

I also tried to use my smartphone as a hotspot to make sure it’s not my home router doing funky stuff. Could this be a fly io server issue?