-
-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
uploaded Avatar not found #279
Comments
Your username is in the url, that's what it uses to figure out which avatar to serve. Does the files volume have the appropriate permissions, as outlined in the docs? https://vikunja.io/docs/installing#docker Did you change the user Vikunja is running as? |
I had set the ROOTPATH in the environment variables and only mapped this one folder:
I can see the config.yaml and vikunja.db files. I now added the files path as written in your config. Why is "ROOTPATH" not including the file-directory? |
Good question, I guess I never really thought about that. I admit it makes sense, added an item to the backlog. In the meantime, you can change the basepath for the files directory to be a subdirectory of the rootpath: https://vikunja.io/docs/config-options#files |
Description
I updated from v0.23 to v0.24.0 without issues.
Only one minor thing was seen: My uploaded Avatar was gone:
When opening the image in a new tab I get "Internal Server Error" with following link:
https://todo.DOMAIN.COM/api/v1/avatar/readily-tender-sawfly?size=50&=1719944689649
It seems there is some "id" missig before "=1719944689649"
The log shows:
When trying to upload a new avatar, I get also an "Internal Server Error" with following error in the log:
I then changed the mounted folder premissions from 755 to 777. Still the same owner/group 1000:1000.
When trying to upload again, I only get this log:
I'm running Vikunja in Docker. In v0.23.0 it worked with the avatar.
Did some premissions change? In the changelog are no informations regarding possible changes in premissions.
As written: just a minor inconvenience. Thanks for the great software :)
Sidenote: Vikunja is the only container of my 20 services, which has the timestamp two times in the log.
Vikunja Version
0.24
Browser and version
Firefox 126.0.1
Can you reproduce the bug on the Vikunja demo site?
No
Screenshots
No response
The text was updated successfully, but these errors were encountered: