flyctl deploy: You hit a Fly API error with request ID...

1

Just signed up for fly and went through the sample Python/Flask app. Tested the app locally and all seemed good. Then ran the following commands:

> flyctl auth login
> flyctl launch
> flyctl deploy

After the image was built, pushed to fly and a release created, I got a not-so-helpful error message “Error You hit a Fly API error with request ID:…”

--> Building image done
==> Pushing image to fly
The push refers to repository [registry.fly.io/my-rando-app]
83d85471d9f8: Pushed
0f651b8f92a6: Pushed
f6b3eafdc09a: Pushed
1bc0789c8944: Pushed
185181dd43f0: Pushed
96ed7248d21f: Pushed
c23057e83cef: Pushed
0ce631bf90b9: Pushed
4937035502fd: Pushed
c892a6f3f753: Pushed
17b998bb08c1: Pushed
4a641e21953d: Pushed
deployment-01GDYMBBFXKNQJMB6BK96K5PCD: digest: sha256:93aaebde6d4b5e8663bed43f85c4859655f9e891a05ada73e80e05403a12a9af size: 2831
--> Pushing image done
image: registry.fly.io/my-rando-app:deployment-01GDYMBBFXKNQJMB6BK96K5PCD
image size: 328 MB
==> Creating release
Error You hit a Fly API error with request ID: 01GDYMDKY8XJ8A2R4KXSHEP2F2-lga

Any ideas on how to resolve? Thanks!

2 Likes
2

Same problem here a few minutes ago. I put together a custom dockerfile, but it exposes port 8080, I can run the docker image and hit the server it runs from a browser on the host machine. fly launch worked, but fly deploy reports the same error as above, with a different request ID.

3

Same with hello fly from the getting started section from docs

4

same here, Error You hit a Fly API error with request ID
this is the toml file looks like

app = “appname”
kill_signal = “SIGINT”
kill_timeout = 5
processes =

i think its with fly.io server issue

5

Same here. Getting the same exact error since few hours ago

6

Same situation. I even tried switching regions with no success.

7

Same issue. Can’t success with flyio/hellofly:latest or other Docker Hub pre-built images.

8

Same issue here,

==> Creating release
Error You hit a Fly API error with request ID: 01GDZ4STEWA05WD7SA56NV4CN0-cdg

Edit: Resolved by doing flyctl launch

1 Like
9

Recreate everything and run flyctl launch works

10

FYI the issue seems resolved - I just ran fly deploy and it deployed without error. Didn’t need to rerun fly launch.

11

I reran fly launch and it seemed to get further, then crapped out with a separate python error:

2022-09-27T13:46:30.000 [info]   File "/layers/paketo-buildpacks_cpython/cpython/lib/python3.10/importlib/__init__.py", line 126, in import_module
2022-09-27T13:46:30.000 [info]     return _bootstrap._gcd_import(name[level:], package, level)
2022-09-27T13:46:30.000 [info]   File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
2022-09-27T13:46:30.000 [info]   File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
2022-09-27T13:46:30.000 [info]   File "<frozen importlib._bootstrap>", line 1004, in _find_and_load_unlocked
2022-09-27T13:46:30.000 [info] ModuleNotFoundError: No module named 'server'
2022-09-27T13:46:30.000 [info] [2022-09-27 13:46:30 +0000] [532] [INFO] Worker exiting (pid: 532)
2022-09-27T13:46:30.000 [info] [2022-09-27 13:46:30 +0000] [515] [INFO] Shutting down: Master
2022-09-27T13:46:30.000 [info] [2022-09-27 13:46:30 +0000] [515] [INFO] Reason: Worker failed to boot.
2022-09-27T13:46:31.000 [info] Starting clean up.
***v0 failed - Failed due to unhealthy allocations - no stable job version to auto revert to and deploying as v1

Troubleshooting guide at https://fly.io/docs/getting-started/troubleshooting/
Error abort

Not sure why, I’m simply deploying the cloned fly Python sample app.

Then tried flyctl deploy and got:

2022-09-27T13:59:41Z   [info][2022-09-27 13:59:41 +0000] [532] [INFO] Worker exiting (pid: 532)
2022-09-27T13:59:41Z   [info][2022-09-27 13:59:41 +0000] [515] [INFO] Shutting down: Master
2022-09-27T13:59:41Z   [info][2022-09-27 13:59:41 +0000] [515] [INFO] Reason: Worker failed to boot.
12

Hi! I had a same problem after re-creating my app builder.
I removed my app then tried flyctl launch but it doesn’t solve my problem.
Also I tried repeating flyctl deploy , the error message remains.

スクリーンショット 2022-09-29 195324
スクリーンショット 2022-09-29 1953241380×118 26.7 KB

13

Hi!

We’re working through an incident at the moment: https://status.flyio.net/

That’s likely related - give it a try after the issue is resolved and let us know what you see then!

1 Like
14

Heya, in case you missed it, this should be resolved now

3 Likes
15

Hi! I an new to fly.io and just run the python tutorial in the document.
However, the problem as above seems not revolved.
Any advice is appreciated.

16

Maybe your problem will be similar to this:
[URGENT] Contact Lost with instance - Questions / Help - Fly.io
@moonstarsky37

17

@Cadulogy Thanks for your advice.
I take a look in this reply and check the
flyctl logs -a MY_FLY-builder
It shows “Deadline reached without docker build”

I think the problem is like the reply as ‘LuxuryMode’
since my deploy error also shows

2022-10-09T06:53:04.000 [info]     return _bootstrap._gcd_import(name[level:], package, level)
2022-10-09T06:53:04.000 [info]   File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
2022-10-09T06:53:04.000 [info]   File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
2022-10-09T06:53:04.000 [info]   File "<frozen importlib._bootstrap>", line 1004, in _find_and_load_unlocked
2022-10-09T06:53:04.000 [info] ModuleNotFoundError: No module named 'server'
2022-10-09T06:53:04.000 [info] [2022-10-09 06:53:04 +0000] [538] [INFO] Worker exiting (pid: 538)
2022-10-09T06:53:04.000 [info] [2022-10-09 06:53:04 +0000] [520] [INFO] Shutting down: Master
2022-10-09T06:53:04.000 [info] [2022-10-09 06:53:04 +0000] [520] [INFO] Reason: Worker failed to boot.
2022-10-09T06:53:05.000 [info] Starting clean up.
18

I am still having this same issue. I managed to deploy the app once by spamming flyctl launch and flyctl deploy until it finally succeeded.

After that I unfortunately accidentally removed the project and now I have been spamming those commands over 10 times and I am still unable to deploy the project…

Oh wait, just now it finally succeeded again. Only thing that I did differently was to open my project in the fly.io dashboard and open the monitoring tab while deploying.

19

try:

flyctl version update
flyctl agent restart

and

fly deploy
2 Likes
20

Since 2-3 hours, I am seeing the same error in FRA & AMS (have not tried other regions yet):

image: registry.fly.io/vauXXX99:deployment-01GFNFZ35QH8JF3ZEHDKGX2BC4
image size: 221 MB
==> Creating release
Error You hit a Fly API error with request ID: 01GFNFZ6HN3Z750PDVRA5MEJTD-fra

flyctl upgrade, agent restart, launch/deploy did not help. Neither fly deploy --verbose, nor log provides any additional info.

1 Like