Deployment hangs for sample golang app

Questions / Help Build debugging
1

I’m unable to deploy the sample app from Run a Go App · Fly Docs

Running flyctl deploy basically just hangs forever. I’ve let it run for up to an hour with no luck. I tried re-running it with LOG_LEVEL=debug flyctl deploy and it looks like it’s just waiting on the remote builder:

DEBUG Sending remote builder heartbeat pulse to http://fdaa:1:26c0:a7b:c6ef:c26:dbed:2:8080/flyio/v1/extendDeadline...
DEBUG Remote builder heartbeat response: 202 Accepted
DEBUG Sending remote builder heartbeat pulse to http://fdaa:1:26c0:a7b:c6ef:c26:dbed:2:8080/flyio/v1/extendDeadline...
DEBUG Remote builder heartbeat response: 202 Accepted
DEBUG Sending remote builder heartbeat pulse to http://fdaa:1:26c0:a7b:c6ef:c26:dbed:2:8080/flyio/v1/extendDeadline...

Full output from the deploy command: flyctl deploy debugging · GitHub

(also, you can’t ctrl-c flyctl when it’s stuck in this state, you have to kill it with kill -9 which doesn’t seem great)

I’ve tried in both regions AMS and FRA, but it seems to be using the same remote builder each time.

Peeking at the monitoring stats for the remote builder in the web dashboard, it doesn’t seem like it’s overloaded. CPU usage and such seem low.

Any advice? Thanks in advance!

2

have you fixed it?
I’m facing the same issue

3

Nope! Poked at it a little bit but ultimately I gave up, fly was too many red flags for me - I wanted something simple that I didn’t have to think about and this absolutely wasn’t it.