Self host Langfuse not working - column t6.cloud_config does not exist

[SugumarRavichandran]

Throwing error "The column t6.cloud_config does not exist in the current database." If I host it again with new Postgres db it is working fine. But with the existing DB is throwing above error

[dosubot[bot]]

Hey @SugumarRavichandran! I'm here to help you out. If you need assistance with bugs, questions, or becoming a contributor, I'm your bot.

The error you're encountering is likely due to the cloud_config column not being present in your existing PostgreSQL database. This column was added in a migration script, so it seems that the migration hasn't been applied to your existing database.

To resolve this, you can manually apply the migration that adds the cloud_config column. The migration script is located at packages/shared/prisma/migrations/20231223230007_cloud_config/migration.sql and contains the following SQL command:

ALTER TABLE "projects" ADD COLUMN "cloud_config" JSONB;

You can execute this SQL command directly on your existing database to add the missing column. Alternatively, ensure that automatic migrations are enabled by not setting the LANGFUSE_AUTO_POSTGRES_MIGRATION_DISABLED environment variable to true, which allows Langfuse to apply migrations automatically during startup ^[1][2].

To continue talking to Dosu, mention @dosu.

[marcklingen]

I would not recommend to follow these instructions

[marcklingen]

Can you share whether there are any logs by the langfuse container? Generally Langfuse should check for the validity of the database schema at startup of the container and flag any inconsistencies

[marcklingen]

@SugumarRavichandran were you able to resolve this issue?

[SugumarRavichandran]

Hi @marcklingen, ALTER TABLE "projects" ADD COLUMN "cloud_config" JSONB; command worked properly to open the selfhosted langfuse in the browser but when I tried to connect from the code now I'm getting this error, httpcore.ConnectError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1007)

[marcklingen]

Langfuse should be zero-config without any manual migrations necessary. If this is needed, something else is off here. I would not recommend to apply migrations to the db manually as this will make future upgrades impossible / tedious.

Can you check whether a new Langfuse deployment works for you?