Deploy errors: Post "https://api.fly.io/graphql": unexpected EOF

Getting errors trying to deploy into a new account. (App is the hello world node demo.)

$ fly --verbose deploy --remote-only
==> Verifying app config
--> Verified app config
==> Building image
Error failed to fetch an image or build from source: Post "https://api.fly.io/graphql": unexpected EOF

Our API was serving intermittent errors for a few minutes. We disabled a possibly problematic host while we investigate.

Hm, I’m still getting this error – repro’d again seconds ago.

Running into this error as well when trying to create a new volume.

Will you all visit debug.fly.dev and let me know what output you get? You can just copy and paste the text here.

=== Headers ===
Host: debug.fly.dev
Fly-Region: sjc
Fly-Request-Id: 01FW057PJ2S5663D3WSRR8PWXE-sjc
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-User: ?1
Fly-Client-Ip: <my ip redacted>
X-Forwarded-Proto: https
X-Forwarded-Port: 443
Accept-Encoding: gzip, deflate, br
Sec-Fetch-Site: cross-site
Fly-Forwarded-Ssl: on
Fly-Forwarded-Port: 443
Fly-Dispatch-Start: t=1644977969730404;instance=f55cc794
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:96.0) Gecko/20100101 Firefox/96.0
Fly-Forwarded-Proto: https
X-Forwarded-Ssl: on
Via: 2 fly.io
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Dnt: 1
X-Request-Start: t=1644977969730078
X-Forwarded-For: <my ip redacted>, 77.83.140.164

=== ENV ===
FLY_ALLOC_ID=f55cc794-394b-2d85-a90e-389c5d2ff867
FLY_APP_NAME=debug
FLY_PUBLIC_IP=2604:1380:45e1:3002:0:f55c:c794:1
FLY_REGION=sjc
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-02-16 02:19:29.732219697 +0000 UTC m=+5807173.855446365
=== Headers ===
Host: debug.fly.dev
Sec-Fetch-Mode: navigate
Dnt: 1
Fly-Client-Ip: <>
X-Forwarded-Port: 443
Via: 2 fly.io
Sec-Fetch-User: ?1
Fly-Request-Id: 01FW05DNFECST6HT07WWTBN0RJ-lga
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate, br
X-Forwarded-Ssl: on
Fly-Forwarded-Port: 443
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Firefox/91.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
X-Request-Start: t=1644978165230523
Sec-Fetch-Dest: document
Sec-Fetch-Site: cross-site
X-Forwarded-For: <>, 77.83.140.164
Fly-Forwarded-Proto: https
X-Forwarded-Proto: https
Fly-Forwarded-Ssl: on
Fly-Region: lga
Fly-Dispatch-Start: t=1644978165230933;instance=80d793d8

=== ENV ===
FLY_ALLOC_ID=80d793d8-10a9-f476-eb4d-e8aceaef0be6
FLY_APP_NAME=debug
FLY_PUBLIC_IP=2604:1380:45d1:2802:0:80d7:93d8:1
FLY_REGION=ewr
FLY_VM_MEMORY_MB=128
GPG_KEY=<>
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-02-16 02:22:44.482364101 +0000 UTC m=+5807470.406153769

Just received a 503 error as well

Dashboard 500-ing for me too

Our web API is experiencing an outage (those EOFs were probably early indicators). We’re working on it and updating the status page: https://status.flyio.net

1 Like

Hi folks,

I am experiencing the same issues as previously, but now when I try to set up a postgres cluster. The cluster and app do get created though.

Some help would be great.

These are the errors I am experiencing;

Creating postgres cluster **** in organization ******
Launching…⡿ Error failed creating the Postgres cluster ****: Post “GraphQL Playground”: unexpected EOF

and Pinging WireGuard gateway (give us a sec)… FAILED
(Error: ping gateway: pinger: Post “GraphQL Playground”: unexpected EOF)

1 Like

I am also experiencing API issues.

When pinging my personal organization, I receive either:
Error server returned a non-200 status code: 504
or
Error Post “GraphQL Playground”: unexpected EOF

PS: I am not (knowingly) using WireGuard (at least there’s no entry in my ~/.fly/config.yml).

Do we have an ETA on this fix? Thanks!

We’re looking into this.

2 Likes