Issue Summary

I have installed formbricks with the quickinstall-guide using docker on a ubuntu-vm under proxmox. Installation went well without errors. But I can't access the webapp. By proof to the docker containers, i see that the container "ghcr.io/formbricks/formbricks:latest" is endless restarting.

Expected Behavior

No response

Other information (incl. screenshots, Formbricks version, steps to reproduce,...)

In the logs is an "migrating error". But this is a new installation.

[formbricks-formbricks-1] 2026-04-15T19:13:19.452093932Z ❌ database migration timed out after 300 seconds
[formbricks-formbricks-1] 2026-04-15T19:13:19.452243741Z 📋 This might indicate database connectivity issues
[formbricks-formbricks-1] 2026-04-15T19:13:23.328964258Z 🗃️ Running database migrations...
[formbricks-formbricks-1] 2026-04-15T19:13:23.329095409Z Using timeout (300 seconds) for database migration
[formbricks-formbricks-1] 2026-04-15T19:13:35.507035316Z {"level":"error","time":1776280415314,"pid":8,"hostname":"9491f5d97250","name":"formbricks","err":{"type":"Error","message":"Command failed: prisma migrate deploy --schema="/home/nextjs/packages/database/schema.prisma"\nError: P3009\n\nmigrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve\nThe 20240421093432_adds_website_survey_type migration started at 2026-03-03 16:17:37.928205 UTC failed\n\n\n","stack":"Error: Command failed: prisma migrate deploy --schema="/home/nextjs/packages/database/schema.prisma"\nError: P3009\n\nmigrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve\nThe 20240421093432_adds_website_survey_type migration started at 2026-03-03 16:17:37.928205 UTC failed\n\n\n\n at genericNodeError (node:internal/errors:985:15)\n at wrappedFn (node:internal/errors:539:14)\n at ChildProcess.exithandler (node:child_process:417:12)\n at ChildProcess.emit (node:events:508:28)\n at maybeClose (node:internal/child_process:1100:16)\n at Socket. (node:internal/child_process:457:11)\n at Socket.emit (node:events:508:28)\n at Pipe. (node:net:346:12)","code":1,"killed":false,"signal":null,"cmd":"prisma migrate deploy --schema="/home/nextjs/packages/database/schema.prisma"","stdout":"Prisma schema loaded from packages/database/schema.prisma\nDatasource "db": PostgreSQL database "formbricks", schema "public" at "postgres:5432"\n\n1 migration found in prisma/migrations\n\n","stderr":"Error: P3009\n\nmigrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve\nThe 20240421093432_adds_website_survey_type migration started at 2026-03-03 16:17:37.928205 UTC failed\n\n\n"},"msg":"Schema migration 20230329205933_init failed"}
[formbricks-formbricks-1] 2026-04-15T19:13:35.524024960Z {"level":"fatal","time":1776280415338,"pid":8,"hostname":"9491f5d97250","name":"formbricks","err":{"type":"Error","message":"Command failed: prisma migrate deploy --schema="/home/nextjs/packages/database/schema.prisma"\nError: P3009\n\nmigrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve\nThe 20240421093432_adds_website_survey_type migration started at 2026-03-03 16:17:37.928205 UTC failed\n\n\n","stack":"Error: Command failed: prisma migrate deploy --schema="/home/nextjs/packages/database/schema.prisma"\nError: P3009\n\nmigrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve\nThe 20240421093432_adds_website_survey_type migration started at 2026-03-03 16:17:37.928205 UTC failed\n\n\n\n at genericNodeError (node:internal/errors:985:15)\n at wrappedFn (node:internal/errors:539:14)\n at ChildProcess.exithandler (node:child_process:417:12)\n at ChildProcess.emit (node:events:508:28)\n at maybeClose (node:internal/child_process:1100:16)\n at Socket. (node:internal/child_process:457:11)\n at Socket.emit (node:events:508:28)\n at Pipe. (node:net:346:12)","code":1,"killed":false,"signal":null,"cmd":"prisma migrate deploy --schema="/home/nextjs/packages/database/schema.prisma"","stdout":"Prisma schema loaded from packages/database/schema.prisma\nDatasource "db": PostgreSQL database "formbricks", schema "public" at "postgres:5432"\n\n1 migration found in prisma/migrations\n\n","stderr":"Error: P3009\n\nmigrate found failed migrations in the target database, new migrations will not be applied. Read more about how to resolve migration issues in a production database: https://pris.ly/d/migrate-resolve\nThe 20240421093432_adds_website_survey_type migration started at 2026-03-03 16:17:37.928205 UTC failed\n\n\n"},"msg":"Migration failed"}
[formbricks-formbricks-1] 2026-04-15T19:13:35.524040386Z ❌ database migration timed out after 300 seconds
[formbricks-formbricks-1] 2026-04-15T19:13:35.524120321Z 📋 This might indicate database connectivity issues

Your Environment

Self-hosted Formbricks