a year ago
Hello community,
I’m a bit of a noob at this, just trying to make things work for my small beauty salon. Last week, I tried modifying the SIGNUP_ENABLED variable in the .env file, expecting it to work seamlessly, but the system crashed. Now, I can't apply new migrations, and I don’t want to lose the data we’ve accumulated over the past six months.
Here’s the relevant part of the logs:
> @formbricks/database@0.1.0 db:migrate:deploy
> env DATABASE_URL="${MIGRATE_DATABASE_URL:-$DATABASE_URL}" prisma migrate deploy
Prisma schema loaded from schema.prisma
Datasource "db": PostgreSQL database "railway", schema "public" at "postgres.railway.internal:5432"
99 migrations found in prisma/migrations
Error: P3009
migrate found failed migrations in the target database. New migrations will not be applied.
The 20241017124431_add_documents_and_insights migration started at 2024-11-18 17:29:28 UTC failed.
8 Replies
a year ago
Hello,
Deeply sorry about this thread getting lost!
I have got your database into a good state, removed the failed migration, and reverted Formbricks to a version published 6 months ago from when you originally deployed it.
Formbricks is back online, please confirm everything is good!
a year ago
Also gave you some credits for dropping the ball on this thread, in the future, please do not wait 9 days to bump a thread!
a year ago
Thanks! I wasn’t sure what to do, which caused the delay, but it won’t happen again. I really appreciate your help—it’s working now! However, my password isn’t being recognized. Do you have any suggestions on what I can do?
a year ago
I have it in my password manager and I didn't change it :(
a year ago
Hi Brody,
First off, I’m really sorry for the 7-day delay in following up. I own three small beauty salons in my city, and with December being our peak season, Mondays are the only days I can handle these issues.
Thanks to your fix, everything is back online, but I’ve noticed the surveys aren’t displaying the same way across devices anymore. I intentionally switched to the formbricks/formbricks:latest tag, thinking it would be safe since the system had been working fine for over six months. Our surveys and interface were designed around that version. I tried reading the documentation, but as a noob, I clearly didn’t anticipate the risks.
Is there a way to safely use the latest version while keeping our data and ensuring consistent survey display? I’d really appreciate any advice, and I owe you at least three coffees for all your help!
a year ago
You originally deployed latest on June 8th 2024, meaning you deployed version 2.1.0 since that was the latest when you deployed the template.
Note: you have 2.1.1 deployed right now, 2.1.1 is a minor version bump that fixes a tiny bug, pay no mind to the 0.0.1 difference.
The latest 6 months ago is not the same version as the latest today, and the actual latest version today is clearly not compatible.
Thus, your forums where indeed designed with 2.1.0, not today's latest version.
You switching back to the latest version has undone my fixes and got your database back into the broken state.
I will fix it once more, please do not switch to latest again.
> the surveys aren’t displaying the same way across devices anymore.
This is something I cannot help with unfortunately, if anything, it was likely caused by you deploying latest, and if so, without a backup, there's no easy way I can think of to fix that.
You should get in contact with the Formbricks community / developers for further help here.