Seahub web interface broken

Seafile Server
21

Which one did you try? The NGinx config or permissions… or both? The first one is probably not the problem, but it may save you from headaches in the future.

22

I tried both, neither of them worked.

23

If the same thing happens when you try internally, then NGinx is probably not the problem. What other changes did you make to Seafile when you installed NGinx?

Can you post the contents of the following two config files for me?

ccnet.conf
seahub_settings.py

24
  1. ccnet.conf:

[General]
USER_NAME = files
ID = 527786fbe4753af37ab353709895a4d85da69ec4
NAME = files
SERVICE_URL = https://files.uc-x.net

[Client]
PORT = 13419

[Database]
ENGINE = mysql
HOST = 10.90.0.25
PORT = 3306
USER = seafile
PASSWD = Friday@17h00
DB = ccnet-db
CONNECTION_CHARSET = utf8

  1. seahub_settings.py

-- coding: utf-8 --

SECRET_KEY = “lxbwfxrnagakae786=afhlk#j*k4f@og57xk_-(n41gkpv+%2d”
HTTP_SERVER_ROOT = ‘https://files.uc-x.net/seafhttp’
DATABASES = {
‘default’: {
‘ENGINE’: ‘django.db.backends.mysql’,
‘NAME’: ‘seahub-db’,
‘USER’: ‘seafile’,
‘PASSWORD’: ‘Friday@17h00’,
‘HOST’: ‘10.90.0.25’,
‘PORT’: ‘3306’
}
}
CLOUD_MODE = True
MULTI_TENANCY = True

ORG_MEMBER_QUOTA_ENABLED = True

25

The only changes I made was as per the instructions, and that was just changing the http to https in ccnet.conf

And then I added the multi tenancy and HTTP_SERVER_ROOT in seahub_settings.py

26

Where did “HTTP_SERVER_ROOT” come from in seahub_settings.py? According to the manual, you should have “FILE_SERVER_ROOT”

What version of Seafile Server are you running?

27

I am running the latest version 6.2.0

28

The latest version of Seafile is 6.2.5. I would have to check the changelog to see if there were some bug fixes related to your problem.

I haven’t seen HTTP_SERVER_ROOT used in seahub setting for several years now. Try changing it to FILE_SERVER_ROOT, restart Seafile, and then let me know the results. Is there any way you can navigate through the jumbled up web interface and check the service url and also the file server root settings?

29

One other thing you could try, since this appears to be a css related issue and you’ve already checked permissions… You could stop seafile server and seahub, remove the folder called seahub_cache which is located in /tmp, clear your browser cookies, history, cache, etc, restart seahub and seafile, and then try it. It’s possible that the cache is corrupt. You could also look in there to see what dates and times are on the files. They should be dates and times from the last couple of days or so, if you’ve been trying the web ui.