github-starred/vikunja
2
0
Fork 0
mirror of https://github.com/go-vikunja/vikunja.git synced 2026-05-06 03:27:53 -05:00
Code Issues 690 Packages Projects Releases 11 Wiki Activity

[GH-ISSUE #14] Error Request failed with status code 500 Internal Server Error #5819

New Issue
Closed
opened 2026-04-20 16:09:10 -05:00 by GiteaMirror · 2 comments
GiteaMirror commented 2026-04-20 16:09:10 -05:00
Owner
Copy Link

Originally created by @Shardonnay on GitHub (Dec 21, 2021).
Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/14

Hello, beforehand I want to thank you for this amazing project !
I'm not sure if this error is really a bug or just a simple permission error.

The problem:
When uploading an attachment or setting a wallpaper I get the following error message: " Error Request failed with status code 500 Internal Server Error". In the docker container log I got the following error message: "ERROR ▶ handler/UploadBackground 1f7 open files/3: permission denied"

My docker compose file looks like the following:
version: '3'

services:
api:
image: vikunja/api
environment:
VIKUNJA_DATABASE_TYPE: sqlite
VIKUNJA_SERVICE_FRONTENDURL: URL
VIKUNJA_SERVICE_ENABLETASKATTACHMENTS: 1
VIKUNJA_SERVICE_ENABLEREGISTRATION: 1
VIKUNJA_SERVICE_ENABLELINKSHARING: 1
VIKUNJA_SERVICE_ENABLETASKCOMMENTS: 1
VIKUNJA_SERVICE_ENABLEEMAILREMINDERS: 1
VIKUNJA_SERVICE_ENABLEUSERDELETION: 1
VIKUNJA_MAILER_ENABLED: 1
VIKUNJA_MAILER_HOST: SERVER
VIKUNJA_MAILER_PORT: 587
VIKUNJA_MAILER_USERNAME: EMAIL
VIKUNJA_MAILER_PASSWORD: PASSWORD
VIKUNJA_RATELIMIT_ENABLED: 0
VIKUNJA_FILES_MAXSIZE: 8000MB
VIKUNJA_SERVICE_ENABLETOTP: 1
VIKUNJA_SERVICE_TIMEZONE: Europe/Berlin
ports:
- 3456:3456
volumes:
- ./files:/app/vikunja/files
restart: unless-stopped
frontend:
image: vikunja/frontend
ports:
- 4242:80
environment:
VIKUNJA_API_URL: URL/api/v1
restart: unless-stopped

Originally created by @Shardonnay on GitHub (Dec 21, 2021). Original GitHub issue: https://github.com/go-vikunja/vikunja/issues/14 Hello, beforehand I want to thank you for this amazing project ! I'm not sure if this error is really a bug or just a simple permission error. The problem: When uploading an attachment or setting a wallpaper I get the following error message: " Error Request failed with status code 500 Internal Server Error". In the docker container log I got the following error message: "ERROR ▶ handler/UploadBackground 1f7 open files/3: permission denied" My docker compose file looks like the following: version: '3' services: api: image: vikunja/api environment: VIKUNJA_DATABASE_TYPE: sqlite VIKUNJA_SERVICE_FRONTENDURL: URL VIKUNJA_SERVICE_ENABLETASKATTACHMENTS: 1 VIKUNJA_SERVICE_ENABLEREGISTRATION: 1 VIKUNJA_SERVICE_ENABLELINKSHARING: 1 VIKUNJA_SERVICE_ENABLETASKCOMMENTS: 1 VIKUNJA_SERVICE_ENABLEEMAILREMINDERS: 1 VIKUNJA_SERVICE_ENABLEUSERDELETION: 1 VIKUNJA_MAILER_ENABLED: 1 VIKUNJA_MAILER_HOST: SERVER VIKUNJA_MAILER_PORT: 587 VIKUNJA_MAILER_USERNAME: EMAIL VIKUNJA_MAILER_PASSWORD: PASSWORD VIKUNJA_RATELIMIT_ENABLED: 0 VIKUNJA_FILES_MAXSIZE: 8000MB VIKUNJA_SERVICE_ENABLETOTP: 1 VIKUNJA_SERVICE_TIMEZONE: Europe/Berlin ports: - 3456:3456 volumes: - ./files:/app/vikunja/files restart: unless-stopped frontend: image: vikunja/frontend ports: - 4242:80 environment: VIKUNJA_API_URL: URL/api/v1 restart: unless-stopped
GiteaMirror commented 2026-04-20 16:09:12 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Dec 21, 2021):

Hi!

That looks a lot like a permission issue.

Vikunja runs as the user 1000:1000 in the container so that user needs to have access to the mounted files folder. Check out this forum thread about the problem: https://community.vikunja.io/t/permission-error-uploading-attachment/425

<!-- gh-comment-id:999002661 --> @kolaente commented on GitHub (Dec 21, 2021): Hi! That looks a lot like a permission issue. Vikunja runs as the user 1000:1000 in the container so that user needs to have access to the mounted files folder. Check out this forum thread about the problem: https://community.vikunja.io/t/permission-error-uploading-attachment/425
GiteaMirror commented 2026-04-20 16:09:13 -05:00
Author
Owner
Copy Link

@Shardonnay commented on GitHub (Dec 21, 2021):

Thanks @kolaente ! I will now close the issue.

<!-- gh-comment-id:999041739 --> @Shardonnay commented on GitHub (Dec 21, 2021): Thanks @kolaente ! I will now close the issue.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area/api
area/attachments
area/auth
area/avatars
area/backup-restore
area/caldav
area/calendar-view
area/comments
area/config
area/database
area/desktop
area/docker
area/email
area/favorites
area/filters
area/frontend
area/gantt
area/i18n
area/import-export
area/internal-code
area/kanban
area/labels
area/list-view
area/mobile
area/notifications
area/permissions
area/projects
area/pwa
area/recurring-tasks
area/reminders
area/search
area/shortcuts
area/subtasks
area/sync
area/table-view
area/task-editor
area/task-metadata
area/task-relations
area/teams
area/theming
area/time-tracking
area/typesense
area/views
area/webhooks
bug
changes requested
concern/accessibility
concern/performance
concern/regression
concern/ux
confirmed
db/mysql
dependencies
enhancement
good first issue
help wanted
integration/inbound
integration/outbound
kind/bug
kind/feature
needs reproduction
pull-request
Mirrored from GitHub Pull Request
 question
security
support
upstream issue
waiting for reply
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/vikunja#5819
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?