Help Needed: SQL App Deploy Issues - Suspended/ Lost Access

1

Hi All,

I deployed my first Fly app a few months ago, a simple Node.js Express website with a PostgreSQL database. Fly.io set up everything, and it worked fine. I now have two apps: nodeapp and sqlapp.

Recently, I updated the schema and created a Flask API for the Node.js site. I wanted to allow external connections to the SQL database, so I updated the .toml file and created a simple Dockerfile:

Dockerfile
FROM postgres:15.7
CMD [“postgres”]

I put these files in a new subfolder to isolate to sql and ran fly deploy --app sqlapp.

After that, everything stopped working. Both apps were suspended, and a new generic fly-builder name was active. I lost access to SQL and can’t figure out what went wrong.

I have some ideas but don’t know how to revert back. I tried fly deploy -i registry to an earlier version, but that seems to apply only to the nodeapp, not the sqlapp. The Fly.io dashboard shows the first release for sqlapp was just moments ago, with prior activities only showing secrets.

My questions:

  1. Did I lose my PostgreSQL data?
  2. Was creating a Dockerfile for SQL a mistake that forced a generic format instead of Fly.io’s managed service?
  3. How can I proceed? Even if I start over, how can I make changes only to the SQL app if it’s linked to my Node.js app?

I did back up my DB, so I’m not panicking, but I need guidance on the next steps.

Thanks for any help!

2

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.