error building: dial tcp 0.0.0.0:443: connection refused

Hello! getting strange errors out of the blue today, everything has been fine, just started using Fly a week or so ago for a side project.

When I go to deploy, I’m now getting connection failed errors from the remote build server, I tried all different combinations of flags, but this WAS working just fine.

Anything I can check/try on my side? Is this a remote issue?

fly deploy
==> Verifying app config
Validating /home/x/x/mono/fly.toml
✓ Configuration is valid
→ Verified app config
==> Building image
==> Building image
error reporting health: unavailable: dial tcp 0.0.0.0:443: connect: connection refusedError: failed to fetch an image or build from source: error building: unavailable: dial tcp 0.0.0.0:443: connect: connection refused

Error: failed to fetch an image or build from source: error building: unavailable: dial tcp 0.0.0.0:443: connect: connection refused
Stacktrace:
goroutine 1 [running]:
runtime/debug.Stack()
/opt/hostedtoolcache/go/1.26.1/x64/src/runtime/debug/stack.go:26 +0x5e
github.com/superfly/flyctl/internal/cli.printError(0x73146c68000, 0x73147363c0d, 0x731470d9b08, {0x2ff3ba0, 0x73146e55140})
/home/runner/work/flyctl/flyctl/internal/cli/cli.go:190 +0x64e
github.com/superfly/flyctl/internal/cli.Run({0x301fd48?, 0x7314704c4c0?}, 0x73146c68000, {0x73146b5c2e0, 0x2, 0x2})
/home/runner/work/flyctl/flyctl/internal/cli/cli.go:120 +0xafa
main.run()
/home/runner/work/flyctl/flyctl/main.go:47 +0x150
main.main()
/home/runner/work/flyctl/flyctl/main.go:26 +0x18

Would you show readers your TOML config? Consider using a Markdown code block, so that it is readable.

My first inclination is that the health-check seems to be configured to use HTTPS (443), but apps generally serve HTTP. HTTPS is done on the proxy.