Hey guys, I just installed seafile server and im having a weird issue, I can’t upload via the webUI. I can download via the webUI and i can upload and download via the desktop app. Its just uploading via the webUI that fails.
Seafile.log has the following error when i try to upload: Failed to read content from block temp file: Operation not permitted.
Config files are below. I’m using Seafile Server 7.0.5 on Centos 7.
I am setting similar env as u use Ngnix and expose https for use to access.
In your nginx I see 127.0.0.1 listening on port 8000 8082 and 8080
So your real service URL should be the default one , I guess is 127.0.0.1:8000
Or u can also edit from portal setting …and also can try to add file_upload_root option
But all those two option will be overwrited if u edit it from portal admin setting —-I remember it is mentioned in Manual.
I stopped Seafile and Seahub, changed the Service URL to https://127.0.0.1:8000, restarted Seafile and Seahub, and tried to upload the file via the WebUI and it failed.
I repeated the same process with 127.0.0.1:8000 (no https://) and tried to upload and it didn’t work either.
I should note that i had an instance of 7.0.4 server running and it was working properly. I basically made sure ccnet.conf, seahub_settings.py, and seafile.conf (in nginx) were the same (not literally the same but had all the same settings, same URLs, etc.). Thats why i am surprised that i am having this issue. Maybe its na issue with 7.0.5?
based on the seafile.log file, it looks like a permissions issue but i cant for the life of my find a file that the seafile user doesn’t have access to that it needs.
I just cleared my browser cache and that did not fix it. How do i clear memcache? My seafile 7.0.5 server install was a clean install, unrelated to the instance of 7.0.4 i had running.
hmm If still same error “Failed to read content from block temp file: Operation not permitted.” then most likely some place permission u didnt set correctly.
or maybe u can share more configuration to here.
I installed both docker version and pure tar package applicatin version never have such issue.
When I try to search your error message ddint get too much.
I dont think it is real application issue.
Or you may want to restart seafile and seahub service and share seafile.log seahub.log/
i think ccnet.conf use http:xxxxx:8000 should be fine.
Here is my conf
ccnet.conf
Blockquote[General]
USER_NAME = app03
ID = xxxxxxx
NAME = app03
SERVICE_URL = http://0.0.0.0:8000
[Client]
PORT = 13419
nginx.conf
Blockquote
server {
listen 443 ssl;
server_name seafiledemo;
set $appvip ; #set app vip by keepalived
ssl on;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_certificate /etc/nginx/ssl/seafile-selfsigned.crt;
ssl_certificate_key /etc/nginx/ssl/seafile-selfsigned.key;
Here is my seahub.log. I think these warnings are because I am not using the pro version.
2019-11-05 15:10:26,934 [WARNING] django.request:152 get_response Not Found: /api2/repos/0a593706-5d67-4323-9688-5d6062e468ff/
2019-11-05 15:15:26,934 [WARNING] django.request:152 get_response Not Found: /api2/repos/0a593706-5d67-4323-9688-5d6062e468ff/
2019-11-05 15:20:26,986 [WARNING] django.request:152 get_response Not Found: /api2/repos/0a593706-5d67-4323-9688-5d6062e468ff/
2019-11-05 15:25:27,812 [WARNING] django.request:152 get_response Not Found: /api2/repos/0a593706-5d67-4323-9688-5d6062e468ff/
Seafile.log:
[11/05/2019 02:25:55 PM] upload-file.c(1101): Failed to read content from block temp file: Operation not permitted.
[11/05/2019 02:31:46 PM] upload-file.c(1101): Failed to read content from block temp file: Operation not permitted.
[11/05/2019 02:32:11 PM] upload-file.c(1101): Failed to read content from block temp file: Operation not permitted.
seahub error looks ok… that not found i always get …
seafile error looks funny… i even can not google too much this kind of error.
can i know how many servers u are using?
all in one and with nginx?
if you disable nginux service are u able to reach the the web portal by http://localhost:8000
as the seafile code are all binary files… maybe u can try to download the installer pacakge again and install. Sorry just my idea… as i never see this kind of error after playing this app so many times…