"error saving database data" when using dump

Hi Vikunja!

I am using Vikunja (2.2.0) on TrueNAS and I’m trying to export my data. When I run vikunja dump -p /app/vikunja/files inside the container. I get the following output:

2026/03/24 00:23:40 failed to create modcache index dir: mkdir /.cache: permission denied
time=2026-03-24T00:23:40.340Z level=INFO msg="No config file found, using default or config from environment variables."
time=2026-03-24T00:23:40.340Z level=INFO msg="Running migrations…"
time=2026-03-24T00:23:40.371Z level=INFO msg="Ran all migrations successfully."
time=2026-03-24T00:23:40.374Z level=INFO msg="Start dumping config file..."
time=2026-03-24T00:23:40.374Z level=WARN msg="No config file found, not including one in the dump. This usually happens when environment variables are used for configuration."
time=2026-03-24T00:23:40.374Z level=INFO msg="Dumped config file"
time=2026-03-24T00:23:40.375Z level=INFO msg="Dumped .env file"
time=2026-03-24T00:23:40.375Z level=INFO msg="Start dumping version file..."
time=2026-03-24T00:23:40.375Z level=INFO msg="Dumped version"
time=2026-03-24T00:23:40.375Z level=INFO msg="Start dumping database..."
time=2026-03-24T00:23:40.376Z level=ERROR msg="error saving database data: pq: relation \"public.database_notification\" does not exist"

A zip file has been created but importing it results in Internal Server Error in the Web UI presumably because the export is incomplete.

Does anyone know what error saving database data: pq: relation \"public.database_notification\" does not exist means in this context?

This was reported here as well: Table 'vikunja.database_notification' doesn't exist · Issue #2464 · go-vikunja/vikunja · GitHub

A fix is on its way.

1 Like