Closed ITBOX-ITBOY closed 3 years ago
Hello,
is your seafile running behind a reverse-proxy? If yes you maybe have to edit the 'SERVICE_URL' and 'FILE_SERVER_ROOT' in your administration ui. I had the same issue after seafile installation.
I'm running seafile behind a nginx reverse-proxy (ssl termination) and therefore the installation is running on plain http, but is still https encrypted through reverse-proxy. Both of the urls are therefore pointed to the http:// url instead of the https:// ones without ports (in my case, because I only opened https port 443). This is my current configuration: