You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
? Would you like to allocate dedicated ipv4 and ipv6 addresses now? No
This deployment will:
* create 1 "app" machine
No machines in group app, launching a new machine
WARN failed to release lease for machine 683d607a7e4398: lease not found
-------
-------
✖ Failed: timeout reached waiting for health checks to pass for machine 683d607a7e4398: failed to get VM 683d607a7e4398: Get "https://api.machines.dev/v1/apps/…
-------
Error: timeout reached waiting for health checks to pass for machine 683d607a7e4398: failed to get VM 683d607a7e4398: Get "https://api.machines.dev/v1/apps/electric-sql-blahblah/machines/683d607a7e4398": net/http: request canceled
Your machine never reached the state "%s".
You can try increasing the timeout with the --wait-timeout flag
I left the machine parameters with the default values, 1GB of ram, shared 1x cpu. I did not change anything in fly.toml other than my database URL.
The text was updated successfully, but these errors were encountered:
I'm running it according to
fly.toml
from here: https://electric-sql.com/docs/deployment/fly#deploying-electric-connected-to-an-external-postgresWhen I'm trying to run the sync service on fly.io, it hangs at the last step:
I left the machine parameters with the default values, 1GB of ram, shared 1x cpu. I did not change anything in
fly.toml
other than my database URL.The text was updated successfully, but these errors were encountered: