Can't upload background images #633

Closed
opened 2020-08-14 17:29:21 +00:00 by leggettc18 · 5 comments
Contributor

I went to try out the background image feature of the lists, but I got a 500 internal service error sent to the front end. The api logs are showing a "permission denied" when I try to upload the file. Perhaps some permissions got knocked out of whack inside the api container? What should the proper permissions on the files folder be?

I went to try out the background image feature of the lists, but I got a 500 internal service error sent to the front end. The api logs are showing a "permission denied" when I try to upload the file. Perhaps some permissions got knocked out of whack inside the api container? What should the proper permissions on the `files` folder be?
Owner

By default, the user 1000 and group 1000 should have write access to the files folder, you can change that with the PUID and PGID env variables. Do task attachments work? They use the same underlying files mechanism.

By default, the user `1000` and group `1000` should have write access to the `files` folder, you can change that with the [`PUID` and `PGID`](https://vikunja.io/docs/install-backend/#setting-user-and-group-id-of-the-user-running-vikunja) env variables. Do task attachments work? They use the same underlying files mechanism.
Author
Contributor

When uploading attachments, I get "e is undefined", both in the frontend and api logs.

When uploading attachments, I get "e is undefined", both in the frontend and api logs.
Author
Contributor

Works fine after docker execing into the container and chowning the files folder with chown -R vikunja:vikunja files, so somehow my permissions got out of whack in my api container. Most likely a side effect of some other kind of troubleshooting I did at some point earlier.

Works fine after `docker exec`ing into the container and `chown`ing the `files` folder with `chown -R vikunja:vikunja files`, so somehow my permissions got out of whack in my api container. Most likely a side effect of some other kind of troubleshooting I did at some point earlier.
Owner

Glad you could solve it!

The e is undefined issue is pretty weired, and since its a js issue it's especially weired it shows up in the api logs. Could you open a frontend issue if you see it again?

Glad you could solve it! The `e is undefined` issue is pretty weired, and since its a js issue it's especially weired it shows up in the api logs. Could you open a frontend issue if you see it again?
Author
Contributor

Actually I think I mistyped about the e is undefined error, the api logs just said permission denied on that one. I can still open the issue on that one if it appears again, but I'm guessing it was probably caused by the permissions.

Actually I think I mistyped about the e is undefined error, the api logs just said permission denied on that one. I can still open the issue on that one if it appears again, but I'm guessing it was probably caused by the permissions.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: vikunja/vikunja#633
No description provided.