File Upload Failed - Network Error

Seafile Server
#1

Hi,

for testing purpose I tried running Seafile with Docker on my personal laptop.
I followed the instructions here: hxxps://download.seafile.com/published/seafile-manual/docker/deploy%20seafile%20with%20docker.md

In short I downloaded docker-compose.yml and run docker-compose up -d.

Everything goes well but when I try to upload a file, I get a Network error as showed in the following screen:

Screenshot from 2020-09-04 14-41-49
Screenshot from 2020-09-04 14-41-491622×924 50.4 KB

I didn’t modify any configuration file.
I’m running “Debian GNU/Linux 10 (buster)” and “Docker version 19.03.12”.

Any idea?

#2

I’ve been struggling with this problem all day … I can finally send and create files if you put your public domain (if you have one) in your SEAFILE_SERVER_HOSTNAME variable of your docker-compose.yml file or 127.0.0.1 (for example) if you prefer run it locally. Remember to modify your current docker-compose, delete your / opt / seafile folders, and run the new docker-compose file.

2 Likes
#3

OMG I think I love you!
Thank you very much!

#4

Same issue as OP but local IP and 127.0.0.1 both don’t work.

#5

Anyone have any idea how to get this working?

#6

I have the same problem

#7
#8

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.

2 Likes
#9

I am late to this thread, but just experienced this problem. Running Apache as the box’s primary web server, then have Seafile running in Docker with NGINX using alternative ports 1080 and 8443.

I do have Apache do a redirect
RewriteRule ^ https://%{SERVER_NAME}:8443%{REQUEST_URI} [END,NE,R=permanent]

This particular grief was SOLVED by proceeding to the Admin Settings page and setting

I described the URLS below but not included as there is a “no links” rule :stuck_out_tongue:

SERVICE_URL: included https and included :8443 then a trailing slash
FILE_SERVER_ROOT: included https and included :8443 then a trailing slash/ then seafhttp

A quick check with my other browser logged in as a user, bingidity bang!

Note that you can make theses setting changes in the py file, but do note that the settings page explains that setting made there are stored in the database and take precedence over the py configurations.