[Bug]: After latest update to 1.22.0 planka no longer starts #571

New Issue

OVERLORD · 2026-02-04T20:24:31+03:00

OVERLORD commented

2026-02-04 20:24:31 +03:00

Originally created by @jimz011 on GitHub (Sep 20, 2024).

Where is the problem occurring?

I encountered the problem while using the application (Frontend)

What browsers are you seeing the problem on?

Brave, Chrome, Firefox, Microsoft Edge, Safari, Other

Current behaviour

After updating to the latest docker image it no longer wants to start. It also shows no logs at all. If I try an older tag (e.g. 1.21.1) then it will start but throw the following error:

Error: The migration directory is corrupt, the following files are missing: 20240831195806_additional_http_only_token_for_enhanced_security_in_browsers.js

I hope someone can help me as reverting to older versions of postgres and planka have no effect and I can't find anything on the web about this specific error.

Desired behaviour

The desired behaviour is that it works as before again.

Steps to reproduce

I did update both postgresql (v. 16.4) and planka (v. 1.22.0)

Other information

No response

Originally created by @jimz011 on GitHub (Sep 20, 2024). ### Where is the problem occurring? I encountered the problem while using the application (Frontend) ### What browsers are you seeing the problem on? Brave, Chrome, Firefox, Microsoft Edge, Safari, Other ### Current behaviour After updating to the latest docker image it no longer wants to start. It also shows no logs at all. If I try an older tag (e.g. 1.21.1) then it will start but throw the following error: ``` Error: The migration directory is corrupt, the following files are missing: 20240831195806_additional_http_only_token_for_enhanced_security_in_browsers.js ``` I hope someone can help me as reverting to older versions of postgres and planka have no effect and I can't find anything on the web about this specific error. ### Desired behaviour The desired behaviour is that it works as before again. ### Steps to reproduce I did update both postgresql (v. 16.4) and planka (v. 1.22.0) ### Other information _No response_

OVERLORD closed this issue

2026-02-04 20:24:36 +03:00

OVERLORD commented

2026-02-04 20:24:48 +03:00

@meltyshev commented on GitHub (Sep 20, 2024):

Hi! Thanks for reporting this.

To rollback to 1.21.1, you need to specify 1.22.0 in the docker-compose.yml, run it, and then connect to the container (the container name may be different):

docker exec -ti planka-planka-1 /bin/bash

After that perform a database rollback:

cd db
npx --yes knex migrate:rollback

If the above doesn't work, please reply here and I'll suggest other options.

@meltyshev commented on GitHub (Sep 20, 2024): Hi! Thanks for reporting this. To rollback to `1.21.1`, you need to specify `1.22.0` in the `docker-compose.yml`, run it, and then connect to the container (the container name may be different): ``` docker exec -ti planka-planka-1 /bin/bash ``` After that perform a database rollback: ``` cd db npx --yes knex migrate:rollback ``` If the above doesn't work, please reply here and I'll suggest other options.

OVERLORD commented

2026-02-04 20:24:51 +03:00

@meltyshev commented on GitHub (Sep 20, 2024):

Regarding Planka not starting: when running via docker compose, the startup logs for both Planka and Postgres should be displayed. Could you please show me what's being displayed, or is nothing showing up at all?

@meltyshev commented on GitHub (Sep 20, 2024): Regarding Planka not starting: when running via docker compose, the startup logs for both Planka and Postgres should be displayed. Could you please show me what's being displayed, or is nothing showing up at all?

OVERLORD commented

2026-02-04 20:25:03 +03:00

@jimz011 commented on GitHub (Sep 23, 2024):

Unfortunately this did not work. I even did a full database restore to the point where it still worked without success.
When running the latest version it will show no logs at all (though I am able to run commands in the container).
When using tags other than latest it will throw errors like the above.

I also used the rollback command mentioned in your post, it rolls back succesfully but that is basically it, the more rollbacks I do the more errors it will show.

EDIT: I have to mention that when I run the latest version it will open a completely white page when visiting IP:PORT.

@jimz011 commented on GitHub (Sep 23, 2024): Unfortunately this did not work. I even did a full database restore to the point where it still worked without success. When running the latest version it will show no logs at all (though I am able to run commands in the container). When using tags other than latest it will throw errors like the above. I also used the rollback command mentioned in your post, it rolls back succesfully but that is basically it, the more rollbacks I do the more errors it will show. EDIT: I have to mention that when I run the latest version it will open a completely white page when visiting IP:PORT.

OVERLORD commented

2026-02-04 20:25:08 +03:00

@jimz011 commented on GitHub (Sep 23, 2024):

I have also tried rolling back the db, removing the planka image entirely and reinstall it. No avail.
I have also tried rollinb back the db and then reinstalling an older image of planka (it will then throw this error: (process:19): VIPS-WARNING **: 07:17:30.731: threads clipped to 1024.

When doing anything else it will just throw an error that the migration files are missing (as stated in the first post).

@jimz011 commented on GitHub (Sep 23, 2024): I have also tried rolling back the db, removing the planka image entirely and reinstall it. No avail. I have also tried rollinb back the db and then reinstalling an older image of planka (it will then throw this error: ` (process:19): VIPS-WARNING **: 07:17:30.731: threads clipped to 1024`. When doing anything else it will just throw an error that the migration files are missing (as stated in the first post).

OVERLORD commented

2026-02-04 20:25:12 +03:00

@jimz011 commented on GitHub (Sep 23, 2024):

After some hours of debugging I found the actual problem. It was not the DB that was corrupted (it only shows that error when downgrading anyway).

The problem was the BASE_URL which now sends an Access-Control-Allow-Origin header, this was blocked by NGINX and has now been resolved.

I hope that this message will help others that face the same problem in the future! My apologies for bothering you.

Marked as resolved!

@jimz011 commented on GitHub (Sep 23, 2024): After some hours of debugging I found the actual problem. It was not the DB that was corrupted (it only shows that error when downgrading anyway). The problem was the BASE_URL which now sends an `Access-Control-Allow-Origin` header, this was blocked by NGINX and has now been resolved. I hope that this message will help others that face the same problem in the future! My apologies for bothering you. Marked as resolved!

OVERLORD referenced this issue

2026-02-04 21:46:24 +03:00

[PR #571] [MERGED] Add: Translation Ukrainian #1049

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/planka#571