[SOLVED] CORS issue after migration

Seafile Server
1

Hi,

I’ve migrated seafile from a server to another, everything seems fine, except:

  • images: The image could not be loaded,
  • pdf: Access token not found.

After some investigations, I notice that the old url is used for these files:
https://OLD_URL/seafhttp/files/d6bf948c-…/file.pdf
CORS Missing Allow Origin
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://OLD_URL/seafhttp/files/d6bf948c-…/file.pdf. (Reason: CORS header ‘Access-Control-Allow-Origin’ missing). Status code: 403.

I’ve tried:

find . -name '__pycache__' |xargs rm -rf "$1"
find . -name '*.pyc' |xargs rm "$1"

grep 'OLD_URL' my-dump-files.sql 
rgrep 'OLD_URL' my-install-dir

… but nothing except in:
ccnet/misc/10e07180e06f33…peer:service-url https://OLD_URL
ccnet/misc/8e4b13b49ca79f…peer:service-url https://OLD_URL
It doesn’t change anything if I change these values !

Any ideas ?
Regards,
Benjamin

config:

  • linux debian 12 + seafile-pro-server-10.0.8 + mariadb 10.11.6
2

I found the solution : FILE_SERVER_ROOT in System Administration > Parameters