How about this?
Unable to upload files (solved)
Check SERVICE_URL in ccnet.conf and FILE_SERVER_ROOT in seahub_settings.py.
Or you can use the parameters in the web settings.

How about this?
Unable to upload files (solved)
Check SERVICE_URL in ccnet.conf and FILE_SERVER_ROOT in seahub_settings.py.
Or you can use the parameters in the web settings.

In web settings is everything written correctly, but in ccnet.conf there is nothing related with SERVICE_URL, should i add it in [General]?
Update: Tried to change from http to https but still nothing
In my ccnet.conf I have an old entry that is now commented-out, so your file should not have an entry.
As to the entry in the Admin Settings for the site, the field for FILE_SERVER_ROOT has this note:
The internal URL for downloading/uploading files. Users will not be able to download/upload files if this is not set correctly. If you config Seafile behind Nginx/Apache, it should be SERVICE_URL/seafhttp, like https://seafile.example.com/seafhttp .
In my case it is simply: https://seafile.mydomain.com/seafhttp or SERVICE_URL/seafhttp (I am running SSL).
In your case, do you have a domain name for your site and are you running SSL?
Another post that reports upload errors:
This fixed the issue for me: login to your Seafile web UI, click on your avatar, got ot “System Admin” > Settings > FILE_SERVER_ROOT > and here you should put your seafile URL or IP address like this:
“hxxp://{YOUR_SERVER_URL}/seafhttp”
For exmple, my server URL is “seafile.local” so I put
hxxp://seafile.local/seafhttp
You can also put it in ‘SEAFILE_SERVER_HOSTNAME=’ in the docker-compose.yml file.
Keep in mind: if the URL is a domain name like (seafile.local), you should have a record for it in your DNS server.
I’m using Pi-Hole as my local DNS server and I’ve added a record for seafile.local pointing to my server’s IP and then put this domain in the system admin URL settings and I was immediately able to upload files.
Yes, all correctly written and I’m using SSL (why wouldn’t I):
SERVICE_URL https://mycloud.example
FILE_SERVER_ROOT https://mycloud.example/seafhttp
I think I will give up on this. Everything looks correctly set up, but I can’t find the problem. I can’t even see logs for the web file upload as the service doesn’t generate any
Where does one find this file ? I clicked on the Manual which took me to a page but it doesn’t tell me where the default location is
“The configuration of seafile fileserver is in the [fileserver] section of the file seafile.conf"
I believe that file can be found here: opt/seafile/conf/seafile.conf .
i found the file in /opt/seafile-data/seafile/conf/ and it’s called seafile.conf