I tried uploading a new logo and a user picture and it always appears broken, nothing else seems to have problems on the server side, but this stuff just seems iffy, whats the fix? [image]

Thanks for reporting this. For a broken logo/user picture after upload, the first things to check are the browser console for the exact error and whether your Seafile deployment URLs are set consistently. In Seafile 12, please verify that SEAFILE_SERVER_PROTOCOL and SEAFILE_SERVER_HOSTNAME match the…

I'm accessing via cloudflare from my own domain, this should me correct ? - SEAFILE_SERVER_PROTOCOL=https - SEAFILE_SERVER_LETSENCRYPT=false this is what the console says: I went into the activities tab and i got this: [image] I

Yes — SEAFILE_SERVER_PROTOCOL=https is correct when you access Seafile over HTTPS through Cloudflare. Please also verify that SEAFILE_SERVER_HOSTNAME is set to the exact public domain you use in the browser, and that it matches the external URL end to end. In Seafile 12, FILESERVER_ROOT is no longe…

I just migrated to seafile 13, the problem persists. My seafilehostname matches exactly my public domain otherwise i couldnt access it from that link and thats the only way i use it from home or otherwise. This is my full seafile hostname - SEAFILE_SERVER_HOSTNAME=seafile.boomsmash.xyz i dont …

Have you tried checking the file permissions on the server? I had a similar issue a couple of years ago (Docker and NFS): [image] Avatar - image won't appear, 403 Forbidden error Seafile Server Sorry it took so long to look back into this. Your tip worked per…

I have gone around checking all the folders permissions, and apparently its all good, but I’ll go check that tip and see i missed the specific one that would fix it !

after all i fed that page to claude and it helped me finally get to the issue, i appreciate it !, it wasnt exactly that but it was a permission that tos wasnt having so finally got hacked it together and now it works <3

Seafile 12 issue with logo / user picture

Seafile Server

Resilient8924 September 21, 2026, 9:24pm 6

Have you tried checking the file permissions on the server? I had a similar issue a couple of years ago (Docker and NFS):