Export not working #2531

Closed
opened 2026-03-22 14:10:45 -05:00 by GiteaMirror · 11 comments
Owner

Originally created by @winkelement on GitHub (Feb 10, 2026).

Pre-submission checklist

  • I have searched for existing open or closed issue reports with the same problem.

Description

Trying to download an export of user data fails.

Console errors:

sw.js:2 Uncaught NetworkError: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https://try.vikunja.io/workbox-v7.3.0/workbox-sw.js' failed to load.
    at sw.js:2:5325
(anonymous) @ sw.js:2
The script has an unsupported MIME type ('text/html').
index--rcGo1rr.js:588 Error during service worker registration: TypeError: Failed to register a ServiceWorker for scope ('https://try.vikunja.io/') with script ('https://try.vikunja.io/sw.js'): ServiceWorker script evaluation failed
error @ index--rcGo1rr.js:588
r @ index--rcGo1rr.js:588
Xc @ index--rcGo1rr.js:588
(anonymous) @ index--rcGo1rr.js:588
Promise.catch
QT @ index--rcGo1rr.js:588
(anonymous) @ index--rcGo1rr.js:588
Promise.then
GG @ index--rcGo1rr.js:588
(anonymous) @ index--rcGo1rr.js:588
index-BZnWE8hY.js:492  POST https://try.vikunja.io/api/v1/user/export/download 404 (Not Found)
(anonymous) @ index-BZnWE8hY.js:492
apply @ index-BZnWE8hY.js:491
(anonymous) @ index--rcGo1rr.js:7
xhr @ index--rcGo1rr.js:7
M3 @ index--rcGo1rr.js:9
Promise.then
_request @ index--rcGo1rr.js:10
request @ index--rcGo1rr.js:9
(anonymous) @ index--rcGo1rr.js:5
getBlobUrl @ index--rcGo1rr.js:12
download @ dataExport-i244vXrN.js:1
$ @ DataExportDownload-BOK2H_uE.js:1
b.onClick.s.<computed>.s.<computed> @ DataExportDownload-BOK2H_uE.js:1
gl @ index--rcGo1rr.js:3
Zr @ index--rcGo1rr.js:3
x7 @ index--rcGo1rr.js:5
e.disabled.oe.onClick.o.<computed>.o.<computed> @ index--rcGo1rr.js:15
gl @ index--rcGo1rr.js:3
Zr @ index--rcGo1rr.js:3
n @ index--rcGo1rr.js:5
dataExport-i244vXrN.js:1 Uncaught (in promise) gt {message: 'Request failed with status code 404', name: 'AxiosError', code: 'ERR_BAD_REQUEST', config: {…}, request: XMLHttpRequest, …}
A6 @ index--rcGo1rr.js:7
v @ index--rcGo1rr.js:7
XMLHttpRequest.send
(anonymous) @ index-BZnWE8hY.js:492
apply @ index-BZnWE8hY.js:491
(anonymous) @ index--rcGo1rr.js:7
xhr @ index--rcGo1rr.js:7
M3 @ index--rcGo1rr.js:9
Promise.then
_request @ index--rcGo1rr.js:10
request @ index--rcGo1rr.js:9
(anonymous) @ index--rcGo1rr.js:5
getBlobUrl @ index--rcGo1rr.js:12
download @ dataExport-i244vXrN.js:1
$ @ DataExportDownload-BOK2H_uE.js:1
b.onClick.s.<computed>.s.<computed> @ DataExportDownload-BOK2H_uE.js:1
gl @ index--rcGo1rr.js:3
Zr @ index--rcGo1rr.js:3
x7 @ index--rcGo1rr.js:5
e.disabled.oe.onClick.o.<computed>.o.<computed> @ index--rcGo1rr.js:15
gl @ index--rcGo1rr.js:3
Zr @ index--rcGo1rr.js:3
n @ index--rcGo1rr.js:5

Vikunja Version

1.1.0

Browser and version

Chrome 144.0.7559.110 (arm64)

Can you reproduce the bug on the Vikunja demo site?

Yes

Screenshots

Image
Originally created by @winkelement on GitHub (Feb 10, 2026). ### Pre-submission checklist - [x] I have searched for existing open or closed issue reports with the same problem. ### Description Trying to download an export of user data fails. Console errors: ``` sw.js:2 Uncaught NetworkError: Failed to execute 'importScripts' on 'WorkerGlobalScope': The script at 'https://try.vikunja.io/workbox-v7.3.0/workbox-sw.js' failed to load. at sw.js:2:5325 (anonymous) @ sw.js:2 The script has an unsupported MIME type ('text/html'). index--rcGo1rr.js:588 Error during service worker registration: TypeError: Failed to register a ServiceWorker for scope ('https://try.vikunja.io/') with script ('https://try.vikunja.io/sw.js'): ServiceWorker script evaluation failed error @ index--rcGo1rr.js:588 r @ index--rcGo1rr.js:588 Xc @ index--rcGo1rr.js:588 (anonymous) @ index--rcGo1rr.js:588 Promise.catch QT @ index--rcGo1rr.js:588 (anonymous) @ index--rcGo1rr.js:588 Promise.then GG @ index--rcGo1rr.js:588 (anonymous) @ index--rcGo1rr.js:588 index-BZnWE8hY.js:492 POST https://try.vikunja.io/api/v1/user/export/download 404 (Not Found) (anonymous) @ index-BZnWE8hY.js:492 apply @ index-BZnWE8hY.js:491 (anonymous) @ index--rcGo1rr.js:7 xhr @ index--rcGo1rr.js:7 M3 @ index--rcGo1rr.js:9 Promise.then _request @ index--rcGo1rr.js:10 request @ index--rcGo1rr.js:9 (anonymous) @ index--rcGo1rr.js:5 getBlobUrl @ index--rcGo1rr.js:12 download @ dataExport-i244vXrN.js:1 $ @ DataExportDownload-BOK2H_uE.js:1 b.onClick.s.<computed>.s.<computed> @ DataExportDownload-BOK2H_uE.js:1 gl @ index--rcGo1rr.js:3 Zr @ index--rcGo1rr.js:3 x7 @ index--rcGo1rr.js:5 e.disabled.oe.onClick.o.<computed>.o.<computed> @ index--rcGo1rr.js:15 gl @ index--rcGo1rr.js:3 Zr @ index--rcGo1rr.js:3 n @ index--rcGo1rr.js:5 dataExport-i244vXrN.js:1 Uncaught (in promise) gt {message: 'Request failed with status code 404', name: 'AxiosError', code: 'ERR_BAD_REQUEST', config: {…}, request: XMLHttpRequest, …} A6 @ index--rcGo1rr.js:7 v @ index--rcGo1rr.js:7 XMLHttpRequest.send (anonymous) @ index-BZnWE8hY.js:492 apply @ index-BZnWE8hY.js:491 (anonymous) @ index--rcGo1rr.js:7 xhr @ index--rcGo1rr.js:7 M3 @ index--rcGo1rr.js:9 Promise.then _request @ index--rcGo1rr.js:10 request @ index--rcGo1rr.js:9 (anonymous) @ index--rcGo1rr.js:5 getBlobUrl @ index--rcGo1rr.js:12 download @ dataExport-i244vXrN.js:1 $ @ DataExportDownload-BOK2H_uE.js:1 b.onClick.s.<computed>.s.<computed> @ DataExportDownload-BOK2H_uE.js:1 gl @ index--rcGo1rr.js:3 Zr @ index--rcGo1rr.js:3 x7 @ index--rcGo1rr.js:5 e.disabled.oe.onClick.o.<computed>.o.<computed> @ index--rcGo1rr.js:15 gl @ index--rcGo1rr.js:3 Zr @ index--rcGo1rr.js:3 n @ index--rcGo1rr.js:5 ``` ### Vikunja Version 1.1.0 ### Browser and version Chrome 144.0.7559.110 (arm64) ### Can you reproduce the bug on the Vikunja demo site? Yes ### Screenshots <img width="2218" height="2150" alt="Image" src="https://github.com/user-attachments/assets/51968647-6790-4a29-ba83-5c39f8dd5e6f" />
Author
Owner

@kolaente commented on GitHub (Feb 11, 2026):

Does this happen on your instance or only on the demo? The demo is cleaned up periodically which may cause these kinds of errors.

If it happens on your instance, what do you see in the logs?

@kolaente commented on GitHub (Feb 11, 2026): Does this happen on your instance or only on the demo? The demo is cleaned up periodically which may cause these kinds of errors. If it happens on your instance, what do you see in the logs?
Author
Owner

@winkelement commented on GitHub (Feb 12, 2026):

Happens exactly like that on my instance, errors in the browser console are the same.

Docker logs show this when i click "Request a copy of my Vakunja Data" (Nothing happens in the UI).

{
  "time": "2026-02-12T07:45:29.628Z",
  "level": "ERROR",
  "msg": "Error while handling message 5039bf30-042b-4c18-b674-ce10061b63fc, handler_poisoned=user.export.requested.handle.user.data.export, subscriber_poisoned=gochannel.GoChannel, reason_poisoned=error creating temp file: open /tmp/vikunja-export-3681373255.zip: no such file or directory, topic_poisoned=user.export.requested,  payload={\\\"user\\\":{\\\"id\\\":2,\\\"name\\\":\\\"XXX \\\",\\\"username\\\":\\\"XXX\\\",\\\"created\\\":\\\"2026-02-10T11:30:39Z\\\",\\\"updated\\\":\\\"2026-02-11T17:07:17Z\\\"}}"
}
@winkelement commented on GitHub (Feb 12, 2026): Happens exactly like that on my instance, errors in the browser console are the same. Docker logs show this when i click "Request a copy of my Vakunja Data" (Nothing happens in the UI). ```json { "time": "2026-02-12T07:45:29.628Z", "level": "ERROR", "msg": "Error while handling message 5039bf30-042b-4c18-b674-ce10061b63fc, handler_poisoned=user.export.requested.handle.user.data.export, subscriber_poisoned=gochannel.GoChannel, reason_poisoned=error creating temp file: open /tmp/vikunja-export-3681373255.zip: no such file or directory, topic_poisoned=user.export.requested, payload={\\\"user\\\":{\\\"id\\\":2,\\\"name\\\":\\\"XXX \\\",\\\"username\\\":\\\"XXX\\\",\\\"created\\\":\\\"2026-02-10T11:30:39Z\\\",\\\"updated\\\":\\\"2026-02-11T17:07:17Z\\\"}}" } ```
Author
Owner

@joren485 commented on GitHub (Feb 13, 2026):

I encounter the same problem, using the vikunja/vikunja:latest Docker image in a docker compose setup. I get the same error message: error creating temp file: open /tmp/vikunja-export-3581461698.zip: no such file or directory

This might be happening because the Docker image is based on scratch, which does not have a /tmp/ folder.

I can reproduce it using the standard docker-compose.yml file:

---

services:
  vikunja:
    image: vikunja/vikunja
    environment:
      VIKUNJA_SERVICE_PUBLICURL: "http://127.0.0.1/"
      VIKUNJA_DATABASE_HOST: db
      VIKUNJA_DATABASE_PASSWORD: changeme
      VIKUNJA_DATABASE_TYPE: postgres
      VIKUNJA_DATABASE_USER: vikunja
      VIKUNJA_DATABASE_DATABASE: vikunja
      VIKUNJA_SERVICE_JWTSECRET: vikunja
    ports:
      - 127.0.0.1:3456:3456
    volumes:
      - ./files:/app/vikunja/files
    depends_on:
      db:
        condition: service_healthy
    restart: unless-stopped
  db:
    image: postgres:18
    environment:
      POSTGRES_PASSWORD: changeme
      POSTGRES_USER: vikunja
    volumes:
      - ./db:/var/lib/postgresql
    restart: unless-stopped
    healthcheck:
      test: ["CMD-SHELL", "pg_isready -h localhost -U $$POSTGRES_USER"]
      interval: 2s
      start_period: 30s
@joren485 commented on GitHub (Feb 13, 2026): I encounter the same problem, using the `vikunja/vikunja:latest` Docker image in a docker compose setup. I get the same error message: `error creating temp file: open /tmp/vikunja-export-3581461698.zip: no such file or directory` This might be happening because the Docker image is based on `scratch`, which does not have a `/tmp/` folder. I can reproduce it using the standard `docker-compose.yml` file: ``` --- services: vikunja: image: vikunja/vikunja environment: VIKUNJA_SERVICE_PUBLICURL: "http://127.0.0.1/" VIKUNJA_DATABASE_HOST: db VIKUNJA_DATABASE_PASSWORD: changeme VIKUNJA_DATABASE_TYPE: postgres VIKUNJA_DATABASE_USER: vikunja VIKUNJA_DATABASE_DATABASE: vikunja VIKUNJA_SERVICE_JWTSECRET: vikunja ports: - 127.0.0.1:3456:3456 volumes: - ./files:/app/vikunja/files depends_on: db: condition: service_healthy restart: unless-stopped db: image: postgres:18 environment: POSTGRES_PASSWORD: changeme POSTGRES_USER: vikunja volumes: - ./db:/var/lib/postgresql restart: unless-stopped healthcheck: test: ["CMD-SHELL", "pg_isready -h localhost -U $$POSTGRES_USER"] interval: 2s start_period: 30s ```
Author
Owner

@lirc572 commented on GitHub (Feb 14, 2026):

Same error.

@lirc572 commented on GitHub (Feb 14, 2026): Same error.
Author
Owner

@winkelement commented on GitHub (Feb 14, 2026):

I worked around this by adding a tmp directory mount to my compose.yaml:

[...]
    volumes:
      - ./files:/app/vikunja/files
      - ./config.yml:/etc/vikunja/config.yml
      - ./tmp:/tmp:rw
[...]

I had to

chown 1000 tmp/

to make it writable by the vikunja docker container.

@winkelement commented on GitHub (Feb 14, 2026): I worked around this by adding a `tmp` directory mount to my compose.yaml: ```yaml [...] volumes: - ./files:/app/vikunja/files - ./config.yml:/etc/vikunja/config.yml - ./tmp:/tmp:rw [...] ``` I had to ```bash chown 1000 tmp/ ``` to make it writable by the vikunja docker container.
Author
Owner

@kolaente commented on GitHub (Feb 14, 2026):

Does this work with the latest unstable build? There have been a few fixes lately around file permissions that might have fixed this.

@kolaente commented on GitHub (Feb 14, 2026): Does this work with the latest unstable build? There have been a few fixes lately around file permissions that might have fixed this.
Author
Owner

@winkelement commented on GitHub (Feb 18, 2026):

No, using vikunja/vikunja:unstable gets me the same error.

time=2026-02-18T22:29:02.645Z level=ERROR msg="Error while handling message 48839cc7-5616-4489-b239-bacba5138ce7, topic_poisoned=user.export.requested, handler_poisoned=user.export.requested.handle.user.data.export, subscriber_poisoned=gochannel.GoChannel, reason_poisoned=error creating temp file: open /tmp/vikunja-export-3509487275.zip: no such file or directory,  payload={\"user\":{\"id\":7,\"name\":\"xxxxx\",\"username\":\"xxxxx\",\"created\":\"2026-02-18T22:28:43Z\",\"updated\":\"2026-02-18T22:28:43Z\"}}"
@winkelement commented on GitHub (Feb 18, 2026): No, using `vikunja/vikunja:unstable` gets me the same error. ```none time=2026-02-18T22:29:02.645Z level=ERROR msg="Error while handling message 48839cc7-5616-4489-b239-bacba5138ce7, topic_poisoned=user.export.requested, handler_poisoned=user.export.requested.handle.user.data.export, subscriber_poisoned=gochannel.GoChannel, reason_poisoned=error creating temp file: open /tmp/vikunja-export-3509487275.zip: no such file or directory, payload={\"user\":{\"id\":7,\"name\":\"xxxxx\",\"username\":\"xxxxx\",\"created\":\"2026-02-18T22:28:43Z\",\"updated\":\"2026-02-18T22:28:43Z\"}}" ```
Author
Owner

@kolaente commented on GitHub (Feb 19, 2026):

Did you request an export before trying to download it?

There was another bug in the frontend that showed the button to download it when none was available.

@kolaente commented on GitHub (Feb 19, 2026): Did you request an export before trying to download it? There was another bug in the frontend that showed the button to download it when none was available.
Author
Owner

@winkelement commented on GitHub (Feb 20, 2026):

Did you request an export before trying to download it?

Yes i did. Requesting an export is what produces the error. I verified again with latest unstable (v1.1.0-85-a8d3594c):

vikunja-app     | time=2026-02-20T07:54:41.833Z level=INFO component=http method=POST uri=/api/v1/user/export/request status=200 latency=2.938482ms
vikunja-app     | time=2026-02-20T07:54:44.108Z level=ERROR msg="Error while handling message 57d81b43-4697-42aa-9cf7-ccf321d37db6, reason_poisoned=error creating temp file: open /tmp/vikunja-export-3848462020.zip: no such file or directory, topic_poisoned=user.export.requested, handler_poisoned=user.export.requested.handle.user.data.export, subscriber_poisoned=gochannel.GoChannel,  payload={\"user\":{\"id\":6,\"name\":\"XXX\",\"username\":\"XXX\",\"created\":\"2026-02-20T07:54:27Z\",\"updated\":\"2026-02-20T07:54:27Z\"}}"
@winkelement commented on GitHub (Feb 20, 2026): > Did you request an export before trying to download it? Yes i did. Requesting an export is what produces the error. I verified again with latest unstable (v1.1.0-85-a8d3594c): ``` vikunja-app | time=2026-02-20T07:54:41.833Z level=INFO component=http method=POST uri=/api/v1/user/export/request status=200 latency=2.938482ms vikunja-app | time=2026-02-20T07:54:44.108Z level=ERROR msg="Error while handling message 57d81b43-4697-42aa-9cf7-ccf321d37db6, reason_poisoned=error creating temp file: open /tmp/vikunja-export-3848462020.zip: no such file or directory, topic_poisoned=user.export.requested, handler_poisoned=user.export.requested.handle.user.data.export, subscriber_poisoned=gochannel.GoChannel, payload={\"user\":{\"id\":6,\"name\":\"XXX\",\"username\":\"XXX\",\"created\":\"2026-02-20T07:54:27Z\",\"updated\":\"2026-02-20T07:54:27Z\"}}" ```
Author
Owner

@magrecia commented on GitHub (Feb 26, 2026):

I worked around this by adding a tmp directory mount to my compose.yaml:

[...]
volumes:
- ./files:/app/vikunja/files
- ./config.yml:/etc/vikunja/config.yml
- ./tmp:/tmp:rw
[...]

Hi

I solved the problem with a tmpfs directive in my docker-compose.yml

volumes:
     - type: tmpfs
       target: /tmp

No need to create a tmp folder, no need to chown or chmod.

@magrecia commented on GitHub (Feb 26, 2026): > I worked around this by adding a `tmp` directory mount to my compose.yaml: > > [...] > volumes: > - ./files:/app/vikunja/files > - ./config.yml:/etc/vikunja/config.yml > - ./tmp:/tmp:rw > [...] Hi I solved the problem with a tmpfs directive in my docker-compose.yml ``` volumes: - type: tmpfs target: /tmp ``` No need to create a tmp folder, no need to chown or chmod.
Author
Owner

@vikunja-bot-app[bot] commented on GitHub (Mar 2, 2026):

This issue has been fixed in 84d563c, please check with the next unstable build (should be ready for deployment in ~30min, also on the demo).

@vikunja-bot-app[bot] commented on GitHub (Mar 2, 2026): This issue has been fixed in [`84d563c`](https://api.github.com/repos/go-vikunja/vikunja/commits/84d563c51b6cd15000f4af6e058362c5e45c8dc2), please check with the next unstable build (should be ready for deployment in ~30min, also on [the demo](https://try.vikunja.io)).
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#2531