Restore - permission denied

Hello! I am trying to move my tasks from one vikunja instance to another. I got permission denied error when I tried the dump command. I switched to the latest unstable build and passed a path using the -p flag. That worked.

When I try the restore command on the other instance, I get the following error:

psyspy@truenas:/mnt/mypool/docker/vikunja$ sudo docker exec -it vikunja /app/vikunja/vikunja restore /app/vikunja/files/vikunja-dump_2025-07-03_13-01-18.zip
2025-07-03T21:52:15Z: INFO      ? 001 Using config file: /etc/vikunja/config.yml
2025-07-03T21:52:15Z: INFO      ? 002 Running migrations…
2025-07-03T21:52:15Z: INFO      ? 070 Ran all migrations successfully.
2025-07-03T21:52:15Z: WARNING   ? 071 Restoring a dump will wipe your current installation!
2025-07-03T21:52:15Z: WARNING   ? 072 To confirm, please type 'Yes, I understand' and confirm with enter:
Yes, I understand
2025-07-03T21:52:23Z: CRITICAL  ? 073 could not open config file for writing: open config.yml: permission denied

Can you please let me know how to fix this issue?

Are you trying to restore from a dump made with an unstable version?

Yes. Both instances are unstable. I couldn’t get the dump to work on a stable version due to the permission denied issue. I switched to unstable because it has the --path support.

On a side note, will we get a stable version soon?

I got shell access to the db container and created a backup using the mysqldump command. I tried restoring it in the new instance. I can see all the tasks in overview. However, if I click on any project name, I get the following error:

▶ 217 Task filter expression '{"filter":"done = 'false"}'' is invalid [ExpressionError: unexpected character '{']

How do I fix this? Any help is appreciated.

Do I need to update the done field in a sql query?

You shouldn’t need to. The format has changed, which is where that error is coming from.

Did you dump and restore from the same Vikunja unstable build? (with mysqldump)

I did not :grimacing:. Sorry about that. I tried with the same build on both machines, it works fine now. Thanks for your help.