Even though the flag might trigger this error, the root cause in my opinion is the very strange construction regarding the media / avatars folders. For me, it was easy to deploy Seafile in a Docker environment, but it was hours of work to find out why avatars were not displayed, and I have to manually re-copy files and correct folder permissions after every update. So I would strongly wish for a revision of whatever makes this so special in contrast to all other data/database storage.
Just a selection of years-long problems with avatars, which in my opinion should not at all be an isolated factor that could cause any trouble:
I’ll never understand why someone distributes all this non-working shit.
Trying to setup Seafile 10 like explained in instructions.
But setup-seafile-mysql.sh ends with:
Error: Failed to prepare seahub avatars dir: [Errno 13] Permission denied: ‘default-non-register.jpg’
Hi,
Docker Seafile 8.0.7 is running fine.
Upgrade to 8.0.7-1 runs fine.
Upgrade to any later version (9.0.0, latest) fails with error messages in the container log.
*** Running /etc/my_init.d/01_create_data_links.sh...
*** Booting runit daemon...
*** Runit started as PID 25
*** Running /scripts/enterpoint.sh...
2023-05-15 10:22:11 Waiting Nginx
2023-05-15 10:22:12 Nginx ready
2023-05-15 10:22:12 This is a idle script (infinite loop) to keep container running.
[05/15/2023 10:22:12][upgrade…
Hi, my avatar is broken and Chrome shows this in error in console.
Failed to load resource: the server responded with a status of 403 ()
Hovewer, I can upload an avatar without any issue.
So I managed to setup seafile 7.1.4 via docker and after logging in I see a broken image instead of my avatar.
Google chrome reveals:
failed to load SourceMap: Could not load content for https://mydomain.tld/media/css/seafile-ui.map: HTTP error: status code 404, net::ERR_HTTP_RESPONSE_CODE_FAILURE
so I enter the docker container and check:
docker exec -ti seafile bash
cat /etc/nginx/sites-enabled/seafile.nginx.conf
shows
location /media {
root /opt/seafile/seafile-server-latest/seahub; …
Good evening, I would appreciate some help; installed Seafile this evening and some minor problem.
All is installed and working fine except the Avatar in my profile on Seahub. On my Settings page, it shows as a broken image. If I click on it and select a replacement file to upload, I get “Internal Server Error”.
The Seahub log file says:
2019-07-10 00:30:37,513 [WARNING] django.request:152 get_response Not Found: /media/avatars/default.png
2019-07-10 00:30:47,671 [WARNING] django.request:15…
When loading up an avatar, the picture does not load. When checking the URL of the image it is trying to load, it’s “http://127.0.0.1:8000/media/avatars …” as opposed to the proper address it is supposed to be.
When looking avatars in CE 6.3.4, it works properly.
It looks like Seahub is failing to fill in the proper HTTP URL for the avatar image.