failed to fetch an image or build from source: error connecting to docker: failed building options: server returned a non-200 status code: 504

Hello. Trying to deploy GitHub - actualbudget/actual-server: Actual's server. Following the readme but having an issue when deploying. This seem to be an on going issue. Any workaround? Thanks

I had the same thing. Cannot launch docker images in multiple regions

1 Like

Same issue here, I cannot deploy to any of my organisations. I have Go and Node apps in syd and lax regions.

I always get the error:
failed to fetch an image or build from source: error connecting to docker: failed building options:
with either
http2: server sent GOAWAY and closed the connection; LastStreamID=XXXXXXXXXX, ErrCode=NO_ERROR, debug=""
or
server returned a non-200 status code: 504

I’ve seen multiple related topics on here, this seems to be an issue on Fly’s end?
Any help welcome! :slightly_smiling_face:

EDIT: I’ve just managed to deploy using --local-only multiple times until success. Also, one deployment attempt successfully created a release, even though my terminal gave me the GOAWAY error. :thinking: Hope this helps!

1 Like

Error error connecting to docker: failed building options: Post “GraphQL Playground”: http2: server sent GOAWAY and closed the connection; LastStreamID=2147483647, ErrCode=NO_ERROR, debug=“”

yeah I always get GOAWAY

Can you all post the contents of debug.fly.dev here?

Also, are you getting these GOAWAY errors quickly, or after 10+ seconds of waiting? Those errors normally mean the backend timed out.

After 10s I managed to deploy with --local-only

I looked at the logs on the builder and it appeared like it can’t connect to docker sock

Both, sometimes it’s instant, but most of the time it waits for the builder for a while and then stops.

Log from debug.fly.dev

=== Headers ===
Host: debug.fly.dev
X-Forwarded-For: 2a04:4e41:44:1::a3d:5077, 2a09:8280:1:763f:8bdd:34d1:c624:78cd
X-Forwarded-Proto: https
Fly-Forwarded-Ssl: on
X-Forwarded-Port: 443
Tracestate:
Accept-Language: mi,en-AU;q=0.9,en;q=0.8
Fly-Client-Ip: 2a04:4e41:44:1::a3d:5077
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.1 Safari/605.1.15
Accept-Encoding: gzip, deflate, br
X-Forwarded-Ssl: on
Via: 2 fly.io
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8
X-Request-Start: t=1662951999999812
Fly-Forwarded-Port: 443
Fly-Forwarded-Proto: https
Traceparent: 00-08df262c6cd452a9b44e5cc450e6d0ca-9bff54fb595ef0a5-00
Fly-Region: syd
Fly-Request-Id: 01GCQTKJFZT61TAQX6MHZ81BRK-syd

=== ENV ===
FLY_ALLOC_ID=d7d03433-45ea-1ecf-296f-4a7530116e76
FLY_APP_NAME=debug
FLY_PUBLIC_IP=2605:4c40:33:5bcc:0:d7d0:3433:1
FLY_REGION=syd
FLY_VM_MEMORY_MB=128
GPG_KEY=A035C8C19219BA821ECEA86B64E628F8D684696D
HOME=/root
LANG=C.UTF-8
PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PYTHON_GET_PIP_SHA256=01249aa3e58ffb3e1686b7141b4e9aac4d398ef4ac3012ed9dff8dd9f685ffe0
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/d781367b97acf0ece7e9e304bf281e99b618bf10/public/get-pip.py
PYTHON_PIP_VERSION=21.2.4
PYTHON_SETUPTOOLS_VERSION=57.5.0
PYTHON_VERSION=3.10.0
TERM=linux
WS=this
is
a
test
cgroup_enable=memory

2022-09-12 03:06:40.003026848 +0000 UTC m=+4755906.150410266

Update: It seems things are working again on my end, I’ve been able to deploy multiple times without issues with the remote builder. :+1:

same problem on my side.

this is my log:

Summary

=== Headers ===
Host: debug.fly.dev
Fly-Request-Id: 01GCSH4G1CN6PHDD9TFW1YHTYP-fra
Traceparent: 00-6a66d125564657c267d1fbf6509d0a1f-6fb589457a846785-00
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/105.0.0.0 Safari/537.36
Sec-Fetch-Dest: document
Fly-Forwarded-Proto: https
X-Forwarded-Ssl: on
Dnt: 1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,/;q=0.8,application/signed-exchange;v=b3;q=0.9
Sec-Ch-Ua-Platform: “macOS”
Accept-Encoding: gzip, deflate, br
Fly-Client-Ip: 91.3.126.227
Fly-Forwarded-Port: 443
X-Request-Start: t=1663009177645002
Sec-Fetch-User: ?1
Tracestate:
Fly-Forwarded-Ssl: on
Sec-Ch-Ua: “Google Chrome”;v=“105”, “Not)A;Brand”;v=“8”, “Chromium”;v=“105”
Sec-Ch-Ua-Mobile: ?0
Accept-Language: de-DE,de;q=0.9,en-US;q=0.8,en;q=0.7,la;q=0.6
X-Forwarded-For: 91.3.126.227, 77.83.140.164
X-Forwarded-Proto: https
X-Forwarded-Port: 443
Sec-Fetch-Site: cross-site
Sec-Fetch-Mode: navigate
Via: 2 fly.io
Fly-Region: fra

=== ENV ===
FLY_ALLOC_ID=a2caa408-8ae6-2190-ed95-780ef7308e85
FLY_APP_NAME=debug
FLY_PUBLIC_IP=2a00:dd80:20:2b:0:a2ca:a408:1
FLY_REGION=fra
FLY_VM_MEMORY_MB=128
GPG_KEY=A035C8C19219BA821ECEA86B64E628F8D684696D
HOME=/root
LANG=C.UTF-8
PATH=/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
PYTHON_GET_PIP_SHA256=01249aa3e58ffb3e1686b7141b4e9aac4d398ef4ac3012ed9dff8dd9f685ffe0
PYTHON_GET_PIP_URL=https://github.com/pypa/get-pip/raw/d781367b97acf0ece7e9e304bf281e99b618bf10/public/get-pip.py
PYTHON_PIP_VERSION=21.2.4
PYTHON_SETUPTOOLS_VERSION=57.5.0
PYTHON_VERSION=3.10.0
TERM=linux
WS=this
is
a
test
cgroup_enable=memory

2022-09-12 18:59:37.647847327 +0000 UTC m=+4754705.872607008

it seems to have work then I got this

 size: 2206
--> Pushing image done
image: registry.fly.io/testing:deployment-01GCT91EWZ364MX0WA3201D4N5
image size: 245 MB
==> Creating release
Error server returned a non-200 status code: 504

it somehow stuck on creating release.

How did you make it work?

Update

Seems to be working now. Not sure what happened but I managed to deploy the project. :slight_smile: