migration of a project to v2 didn't work out

I use an aut-hosted penpot instanced with docker.
I ran the migration script
docker exec -ti ./run.sh app.migrations.v2

docker exec -ti kdz-penpot-penpot-backend-1 ./run.sh app.migrations.v2
+ exec /opt/jdk/bin/java -Djava.util.logging.manager=org.apache.logging.log4j.jul.LogManager -Dlog4j2.configurationFile=log4j2.xml -XX:-OmitStackTraceInFastThrow -Dpolyglot.engine.WarnInterpreterOnly=false --enable-preview -jar penpot.jar -m app.migrations.v2
[2024-07-01 10:43:18.686] I app.metrics - action="initialize metrics"
[2024-07-01 10:43:18.752] I app.db - hint="initialize connection pool", name="main", uri="postgresql://penpot-postgres/penpot", read-only=false, with-credentials=true, min-size=0, max-size=60
[2024-07-01 10:43:18.878] I app.migrations - hint="running migrations", module=:app.migrations/migrations
[2024-07-01 10:43:19.904] W app.setup - hint="using autogenerated secret-key, it will change on each restart and will invalidate all sessions on each restart, it is hightly recommended setting up the PENPOT_SECRET_KEY environment variable"
[2024-07-01 10:43:20.673] I app.svgo - hint="initializing svg optimizer pool"
[2024-07-01 10:43:21.639] I app.svgo - hint="stopping svg optimizer pool"

But I still can’t open an old project.


Hello @Guillaume_Cartie, could you please send this issue to support@penpot.app?

it’s done, have a nice day

1 Like


I don’t know exactly the reason, because the logs are quite scarce.
I first make sure that the version of the docker image is correct.

Then to ensure, I would delete the database flag that the application is migrated with the following sql on the database:

delete from server_prop where id = 'v2-migrated';

And I would run the migration again.