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

[Question] When I upload images to list's description, error happen #7

New Issue
Closed
opened 2025-11-01 20:43:45 -05:00 by GiteaMirror · 13 comments
GiteaMirror commented 2025-11-01 20:43:45 -05:00
Owner
Copy Link

Originally created by @rogerBridge on GitHub (Jun 9, 2021).

Hello Sir, your vikunja is really a fantastic app, recently, while using your app, I found a bug, when I upload image file to list's description, a bug will happen, in browser console:
image
In frontend:
image

my platform:
client: linux x86 64, firefox 89.0;
server: docker-compose, follow your website's example;
If you need more info about this situation, please tell me : )
could u help me deal with this question? Thank you Sir!

Originally created by @rogerBridge on GitHub (Jun 9, 2021). Hello Sir, your vikunja is really a fantastic app, recently, while using your app, I found a bug, when I upload image file to list's description, a bug will happen, in browser console: ![image](https://user-images.githubusercontent.com/17608761/121435768-fccfe280-c96e-11eb-8a26-eb93bdcfdc91.png) In frontend: ![image](https://user-images.githubusercontent.com/17608761/121435821-0d805880-c96f-11eb-8070-8f7203126027.png) my platform: client: linux x86 64, firefox 89.0; server: docker-compose, follow your website's example; If you need more info about this situation, please tell me : ) could u help me deal with this question? Thank you Sir!
GiteaMirror commented 2025-11-01 20:43:46 -05:00
Author
Owner
Copy Link

@rogerBridge commented on GitHub (Jun 9, 2021):

PS: this error msg is circulate print in browser console

@rogerBridge commented on GitHub (Jun 9, 2021): PS: this error msg is circulate print in browser console
GiteaMirror commented 2025-11-01 20:43:47 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 10, 2021):

Hi :)

What Vikunja version is that? (There should be a message in the browser console)

Can you reproduce this on try?

@kolaente commented on GitHub (Jun 10, 2021): Hi :) What Vikunja version is that? (There should be a message in the browser console) Can you reproduce this on [try](https://try.vikunja.io)?
GiteaMirror commented 2025-11-01 20:43:48 -05:00
Author
Owner
Copy Link

@rogerBridge commented on GitHub (Jun 10, 2021):

Hello Sir:
This is the frontend version: Vikunja frontend version 0.17.0+47-34ded051d1,
Sir, when I upload image file to "try", I found a error existed, show below:
image
image
Thanks for response : )

@rogerBridge commented on GitHub (Jun 10, 2021): Hello Sir: This is the frontend version: Vikunja frontend version 0.17.0+47-34ded051d1, Sir, when I upload image file to "try", I found a error existed, show below: ![image](https://user-images.githubusercontent.com/17608761/121562996-8633f300-ca09-11eb-9ee1-e126fa7f9c45.png) ![image](https://user-images.githubusercontent.com/17608761/121563083-9f3ca400-ca09-11eb-8f1d-f667f7eca50a.png) Thanks for response : )
GiteaMirror commented 2025-11-01 20:43:48 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 10, 2021):

That's odd - works for me on try (at least for tasks).

Does the error also occur in a private tab with all caches cleared?

@kolaente commented on GitHub (Jun 10, 2021): That's odd - works for me on try (at least for tasks). Does the error also occur in a private tab with all caches cleared?
GiteaMirror commented 2025-11-01 20:43:48 -05:00
Author
Owner
Copy Link

@rogerBridge commented on GitHub (Jun 11, 2021):

I just retest it on "try", it worked, I guess maybe some static asset load error yesterday, the same time, I found a small issue, I add a list called: "test_list", and add a item called: "test_image_upload", when I click the attachment, it looks like miss token in request header so the api call is rejected by api server

@rogerBridge commented on GitHub (Jun 11, 2021): I just retest it on "try", it worked, I guess maybe some static asset load error yesterday, the same time, I found a small issue, I add a list called: "test_list", and add a item called: "test_image_upload", when I click the attachment, it looks like miss token in request header so the api call is rejected by api server
GiteaMirror commented 2025-11-01 20:43:48 -05:00
Author
Owner
Copy Link

@rogerBridge commented on GitHub (Jun 11, 2021):

"e is not defined" error message still exist in my environment, I guess maybe I did something wrong, I follow majority of your instruct on vikunja website: "nginx -> (api + frontend)", but I add a layer, "caddy -> nginx -> (api + frontend)", I just use caddy point to nginx's port, just like: nginx associate local 127.0.0.1:8000, and caddy as a reverse proxy point to 127.0.0.1:8000(because caddy had very easy let's encrypt certificate apply and I had some app use caddy, I want make all of them in one place), I will visit nginx only as reverse proxy and try it later

@rogerBridge commented on GitHub (Jun 11, 2021): "e is not defined" error message still exist in my environment, I guess maybe I did something wrong, I follow majority of your instruct on vikunja website: "nginx -> (api + frontend)", but I add a layer, "caddy -> nginx -> (api + frontend)", I just use caddy point to nginx's port, just like: nginx associate local 127.0.0.1:8000, and caddy as a reverse proxy point to 127.0.0.1:8000(because caddy had very easy let's encrypt certificate apply and I had some app use caddy, I want make all of them in one place), I will visit nginx only as reverse proxy and try it later
GiteaMirror commented 2025-11-01 20:43:49 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 11, 2021):

it looks like miss token in request header so the api call is rejected by api server

Anything in the server logs? Is the file created correctly in the db and on disk?

I had some app use caddy, I want make all of them in one place), I will visit nginx only as reverse proxy and try it later

If you're running with docker behind caddy, you might want to check out the caddy proxy examples.

@kolaente commented on GitHub (Jun 11, 2021): > it looks like miss token in request header so the api call is rejected by api server Anything in the server logs? Is the file created correctly in the db and on disk? > I had some app use caddy, I want make all of them in one place), I will visit nginx only as reverse proxy and try it later If you're running with docker behind caddy, you might want to check out [the caddy proxy examples](https://vikunja.io/docs/full-docker-example/#example-with-caddy-v2-as-proxy).
GiteaMirror commented 2025-11-01 20:43:49 -05:00
Author
Owner
Copy Link

@rogerBridge commented on GitHub (Jun 11, 2021):

Anything in the server logs? Is the file created correctly in the db and on disk?

Sir, I am sorry for my bad English and my bad expression, "try" is try, it is your website, so I could not know the server logs.

If you're running with docker behind caddy, you might want to check out the caddy proxy examples.

Thanks, Sir, I will follow your instruct to check out "the caddy proxy examples"

@rogerBridge commented on GitHub (Jun 11, 2021): > Anything in the server logs? Is the file created correctly in the db and on disk? Sir, I am sorry for my bad English and my bad expression, "try" is [try](https://try.vikunja.io), it is your website, so I could not know the server logs. > If you're running with docker behind caddy, you might want to check out the caddy proxy examples. Thanks, Sir, I will follow your instruct to check out "the caddy proxy examples"
GiteaMirror commented 2025-11-01 20:43:49 -05:00
Author
Owner
Copy Link

@rogerBridge commented on GitHub (Jun 11, 2021):

If you're running with docker behind caddy, you might want to check out the caddy proxy examples.

Thanks, Sir, I will follow your instruct to check out "the caddy proxy examples"

Sir, I followed your instruct, and I update all vikunja images(vikunja/api:latest + vikunja/frontend:latest) and the issue still exists;
my docker-compose yml:

version: '3'

services:
  db:
    image: mysql:8.0.25
    command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci
    environment:
      MYSQL_ROOT_PASSWORD: ******
      MYSQL_DATABASE: vikunja
    volumes:
      - ./db:/var/lib/mysql
    restart: unless-stopped
  api:
    image: vikunja/api
    environment:
      VIKUNJA_DATABASE_HOST: db
      VIKUNJA_DATABASE_PASSWORD: ******
      VIKUNJA_DATABASE_TYPE: mysql
      VIKUNJA_DATABASE_USER: root
      VIKUNJA_DATABASE_DATABASE: vikunja
    volumes: 
      - ./files:/app/vikunja/files
    depends_on:
      - db
    restart: unless-stopped
    ports:
      - "127.0.0.1:11000:3456"
  frontend:
    image: vikunja/frontend
    restart: unless-stopped
    ports:
      - "127.0.0.1:11001:80"

my Caddyfile is:

vikunja.fenr.men {
    reverse_proxy /api/* 127.0.0.1:11000
    reverse_proxy /.well-known/* 127.0.0.1:11000
    reverse_proxy /dav/* 127.0.0.1:11000
    reverse_proxy 127.0.0.1:11001
}

While upload images failed, the vikunja/api log is:

image
because I enable the firefox's resist browser fingerprint option, so the request header is wrong.
I guess the issue is when file create, vikunja/api face a permission question, but why it happend? I don't know : (

almost everything works fine, except upload images, if you need more log, please tell me, thanks Sir : )

@rogerBridge commented on GitHub (Jun 11, 2021): > > If you're running with docker behind caddy, you might want to check out the caddy proxy examples. > Thanks, Sir, I will follow your instruct to check out "the caddy proxy examples" Sir, I followed your instruct, and I update all vikunja images(vikunja/api:latest + vikunja/frontend:latest) and the issue still exists; my docker-compose yml: ```yml version: '3' services: db: image: mysql:8.0.25 command: --character-set-server=utf8mb4 --collation-server=utf8mb4_unicode_ci environment: MYSQL_ROOT_PASSWORD: ****** MYSQL_DATABASE: vikunja volumes: - ./db:/var/lib/mysql restart: unless-stopped api: image: vikunja/api environment: VIKUNJA_DATABASE_HOST: db VIKUNJA_DATABASE_PASSWORD: ****** VIKUNJA_DATABASE_TYPE: mysql VIKUNJA_DATABASE_USER: root VIKUNJA_DATABASE_DATABASE: vikunja volumes: - ./files:/app/vikunja/files depends_on: - db restart: unless-stopped ports: - "127.0.0.1:11000:3456" frontend: image: vikunja/frontend restart: unless-stopped ports: - "127.0.0.1:11001:80" ``` my Caddyfile is: ``` vikunja.fenr.men { reverse_proxy /api/* 127.0.0.1:11000 reverse_proxy /.well-known/* 127.0.0.1:11000 reverse_proxy /dav/* 127.0.0.1:11000 reverse_proxy 127.0.0.1:11001 } ``` While upload images failed, the vikunja/api log is: ![image](https://user-images.githubusercontent.com/17608761/121683586-1bd48e80-caad-11eb-9ffd-655d9d4d748d.png) because I enable the firefox's resist browser fingerprint option, so the request header is wrong. I guess the issue is when file create, vikunja/api face a permission question, but why it happend? I don't know : ( almost everything works fine, except upload images, if you need more log, please tell me, thanks Sir : )
GiteaMirror commented 2025-11-01 20:43:49 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 11, 2021):

Sir, I am sorry for my bad English and my bad expression, "try" is try, it is your website, so I could not know the server logs.

Nothing to worry about, I'm not a native english speaker myself so I know that very well 🙂

I've looked at the list and task you created on try and the attachment was uploaded just fine. I can access it when clicking on it in the list, embedding works as well when adding a ! in front of the generated markdown code when uploading through the editor (That's an upstream bug in the editor itself).

Sir, I followed your instruct, and I update all vikunja images(vikunja/api:latest + vikunja/frontend:latest) and the issue still exists;

The configuration looks fine to me. It looks like you're able to access the frontend and upload files even though uploading itself fails. That means the caddy configuration is working fine.

About the permission error: The files folder you mounted to store the attachments (and other things) needs to be accessible to the user and group with the id 1000 for Vikunja to have access to it. Try running chown 1000:1000 ./files -R in the directory where the compose file is stored. After that, restart the container and try uploading an attachment again.

You can could change the uid and gid to match the value of some other user on your host system: https://vikunja.io/docs/install-backend/#files-volume

@kolaente commented on GitHub (Jun 11, 2021): > Sir, I am sorry for my bad English and my bad expression, "try" is try, it is your website, so I could not know the server logs. Nothing to worry about, I'm not a native english speaker myself so I know that very well :slightly_smiling_face: I've looked at the list and task you created on try and the attachment was uploaded just fine. I can access it when clicking on it in the list, embedding works as well when adding a `!` in front of the generated markdown code when uploading through the editor (That's an upstream bug in the editor itself). > Sir, I followed your instruct, and I update all vikunja images(vikunja/api:latest + vikunja/frontend:latest) and the issue still exists; The configuration looks fine to me. It looks like you're able to access the frontend and upload files even though uploading itself fails. That means the caddy configuration is working fine. About the permission error: The files folder you mounted to store the attachments (and other things) needs to be accessible to the user and group with the id 1000 for Vikunja to have access to it. Try running `chown 1000:1000 ./files -R` in the directory where the compose file is stored. After that, restart the container and try uploading an attachment again. You can could change the uid and gid to match the value of some other user on your host system: https://vikunja.io/docs/install-backend/#files-volume
GiteaMirror commented 2025-11-01 20:43:50 -05:00
Author
Owner
Copy Link

@rogerBridge commented on GitHub (Jun 11, 2021):

Wow, it worked, Thanks, Sir, and I have a question, I had add docker to sudo group, so if its permisson group is: root:root, it should has permission to store file in my home directory, why it can't? did it say: docker usergroup is just docker usergroup, it is not root:root, it is just docker:docker and equal to user:user, not equal to root:root, so it has not permission to store file in user:user's folder, is it right? if so, why vikunja/db can store file in my home directory? I can't understand it 😂
ps: just a irrelavant question

@rogerBridge commented on GitHub (Jun 11, 2021): Wow, it worked, Thanks, Sir, and I have a question, I had add docker to sudo group, so if its permisson group is: root:root, it should has permission to store file in my home directory, why it can't? did it say: docker usergroup is just docker usergroup, it is not root:root, it is just docker:docker and equal to user:user, not equal to root:root, so it has not permission to store file in user:user's folder, is it right? if so, why vikunja/db can store file in my home directory? I can't understand it 😂 ps: just a irrelavant question
GiteaMirror commented 2025-11-01 20:43:50 -05:00
Author
Owner
Copy Link

@kolaente commented on GitHub (Jun 11, 2021):

While the docker daemon runs as root, Vikunja itself does not. Vikunja runs as 1000:1000 so if it wants to store files somewhere they have to be accessible to that user. I think you got the gist of it 🙂
There's a bit more info about docker's permission model here: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user

I'm going to close this issue as your problem got resolved. Feel free to open a new one if you have other issues or check out the forum.

@kolaente commented on GitHub (Jun 11, 2021): While the docker daemon runs as root, Vikunja itself does not. Vikunja runs as `1000:1000` so if it wants to store files somewhere they have to be accessible to that user. I think you got the gist of it :slightly_smiling_face: There's a bit more info about docker's permission model here: https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user I'm going to close this issue as your problem got resolved. Feel free to open a new one if you have other issues or [check out the forum](https://community.vikunja.io).
GiteaMirror commented 2025-11-01 20:43:50 -05:00
Author
Owner
Copy Link

@rogerBridge commented on GitHub (Jun 11, 2021):

I found something in vikunja/api Dockerfile:

ENV PUID 1000
ENV PGID 1000

I guess it is the answer, I am wrong before, it associate docker usergroup and host usergroup;
thank you, Sir : )

@rogerBridge commented on GitHub (Jun 11, 2021): I found something in vikunja/api Dockerfile: ```Dockerfile ENV PUID 1000 ENV PGID 1000 ``` I guess it is the answer, I am wrong before, it associate docker usergroup and host usergroup; thank you, Sir : )
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#7
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?