From 088bac28871e00940646a27217425be52233ef06 Mon Sep 17 00:00:00 2001
From: LRVT <21357789+l4rm4nd@users.noreply.github.com>
Date: Sun, 25 Feb 2024 03:29:03 +0100
Subject: [PATCH] Update README.md

adjust notes
---
 examples/seafile/README.md | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/examples/seafile/README.md b/examples/seafile/README.md
index 2009164..b4474b9 100644
--- a/examples/seafile/README.md
+++ b/examples/seafile/README.md
@@ -4,12 +4,24 @@
 
 # Notes
 
-If you run seafile behind a SSL/TLS reverse proxy with HTTPS, you will likely see a `CSRF verification failed` error message during login.
+If you run seafile behind a SSL/TLS reverse proxy with HTTPS, you will likely see a few error messages during login or uploads.
 
-Try adding your domain to the corresponding Django setting inside the Docker bind mount location `/mnt/docker-volumes/seafile/data/seafile/conf/seahub_settings.py`:
+### CSRF Verification Failed
+
+During first login, you may receive a CSRF verification error. This is caused by the Django CMS, which verifies requests based on the Referer HTTP header.
+
+To fix the issue, add your domain via the following config line in `/mnt/docker-volumes/seafile/data/seafile/conf/seahub_settings.py`:
 
 ````
 CSRF_TRUSTED_ORIGINS = ["https://seafile.example.com"]
 ````
 
 See https://github.com/haiwen/seafile/issues/2707#issuecomment-1732493096
+
+### Network Error During File Uploads
+
+Once logged into Seafile you may notice that file uploads do not work yet. You will receive a network failure error when trying to upload something.
+
+This is caused by Seafile's default settings using HTTP urls for `SERVICE_URL` and `FILE_SERVER_ROOT`. 
+
+Head over to the system administration area at `/sys/web-settings/` and adjust both URL variables to use HTTPS instead.