Waiting for remote builder fly-builder-wandering-fire-1326... 🌏 WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-wandering-fire-1326` WARN Failed to start remote builder heartbeat: remote builder app unavailable My builder isn’t doing any work no…

I read [image] `fly deploy` stuck on "Waiting for remote builder" It’s impossible for me to deploy for the last few hours. It gets stuck on “Waiting for remote builder”. [image] After a while it errors with: Error failed to fetch an image or build from so…

Looking at fly-builder-wandering-fire-1326 logs I see that the builder started just fine. I wonder if this might be a Wireguard connectivity issue. Can you try to switch flyctl agent from UDP to websockets for Wireguard and try again? Like this: $ fly agent stop $ fly wg websockets enable

@pavel Thanks for your reply. I tried this but it doesn’t help. Because of your information, I captured a little packets and thought maybe the this is the problem: Every request { "query": "mutation($input: ValidateWireGuardPeersInput!) { validateWireGuardPeers(input: $input) { invalidPeerIps }…

This part is correct. flyctl checks if Wireguard peers listed in its config are valid and prunes the ones that no longer exist on the backend. Can you try this? # stop the agent to make sure it starts a new log file $ fly agent stop # remove previous agent log files $ rm ~/.fly/agent-logs/*.log # …

Okay. This rules out Wireguard issue. One more thing to give more info. When you deploy with debug log level: $ LOG_LEVEL=debug fly deploy there will be a lot of debug info printed, including connection attempts to the builder. There should be some debug output after the line that looks like: W…

@pavel Hi, this is the log Waiting for remote builder fly-builder-wandering-fire-1326... 🌏DEBUG Remote builder unavailable, retrying in 200ms (err: error during connect: Get "http://[fdaa:1:8c65:a7b:7f47:5aee:fd59:2]:2375/_ping": proxyconnect tcp: connect tcp 127.0.0.1:6152: bad local address) DEBU…

After run HTTP_PROXT= fly deploy I build successfully!

Okay. That’s a great finding. This is something we should probably fix on the flyctl side. However, is there any way I can use it with proxy? Connections to the builder happen over the private network that flyctl connects to via its agent. It’s possible to connect your computer directly to this …

@pavel Got it! Thank you. Just because… I’m in China and I’m afraid one day I can’t connect to the builder without a proxy.

`fly deploy` stuck on “Waiting for remote builder”

General

singee May 10, 2023, 6:36am 2

I read

but nothing help