升级到7.0.2后网页显示空白

社区版本
从seafile-server-6.2.5升级到seafile-server-7.0.2后网页访问,可以输入用户名密码,然后页面就一片空白
是否新增了ip访问限制?

==> /var/log/nginx/error.log <==
2019/07/04 05:41:20 [error] 22395#22395: *21 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.10.202, server: , request: “POST /seafhttp/repo/head-commits-multi/ HTTP/1.1”, upstream: “http://192.168.10.141:8082/repo/head-commits-multi/”, host: “192.168.10.141”

==> /var/log/nginx/seahub.access.log <==
192.168.10.202 - - [04/Jul/2019:05:45:18 +0800] “GET /api2/repos/ HTTP/1.1” 200 9351 “-” “Mozilla/5.0”
192.168.10.202 - - [04/Jul/2019:05:48:16 +0800] “GET /api2/ping/ HTTP/1.1” 200 6 “-” “Mozilla/5.0”
192.168.10.202 - - [04/Jul/2019:05:48:16 +0800] “GET /api2/account/info/ HTTP/1.1” 200 419 “-” “Mozilla/5.0”
192.168.10.202 - - [04/Jul/2019:05:50:18 +0800] “GET /api2/repos/ HTTP/1.1” 200 9345 “-” “Mozilla/5.0”
192.168.10.202 - - [04/Jul/2019:05:51:16 +0800] “GET /api2/ping/ HTTP/1.1” 200 6 “-” “Mozilla/5.0”
192.168.10.202 - - [04/Jul/2019:05:51:16 +0800] “GET /api2/account/info/ HTTP/1.1” 200 419 “-” “Mozilla/5.0”
192.168.10.202 - - [04/Jul/2019:05:54:16 +0800] “GET /api2/ping/ HTTP/1.1” 200 6 “-” “Mozilla/5.0”
192.168.10.202 - - [04/Jul/2019:05:54:16 +0800] “GET /api2/account/info/ HTTP/1.1” 502 166 “-” “Mozilla/5.0”
192.168.10.202 - - [04/Jul/2019:05:55:19 +0800] “GET /api2/repos/ HTTP/1.1” 200 9345 “-” “Mozilla/5.0”

==> /var/log/nginx/seahub.error.log <==
2019/07/04 05:54:16 [error] 22397#22397: *93 upstream prematurely closed connection while reading response header from upstream, client: 192.168.10.202, server: , request: “GET /api2/account/info/ HTTP/1.1”, upstream: “http://127.0.0.1:8000/api2/account/info/”, host: “192.168.10.141”

另外7.0.2似乎新增了一个事件模块,但是开源版本没有
==> /seafile/logs/seahub.log <==
2019-07-04 06:07:25,708 [ERROR] root:68 Failed to import seafevents package.
Traceback (most recent call last):
File “/seafile/seafile-server-7.0.2/seahub/seahub/utils/init.py”, line 65, in
from seafevents import seafevents_api
ImportError: No module named seafevents
2019-07-04 06:07:25,713 [ERROR] root:566 Failed to import seafevents package.
Traceback (most recent call last):
File “/seafile/seafile-server-7.0.2/seahub/seahub/utils/init.py”, line 562, in
import seafevents
ImportError: No module named seafevents

==> /seafile/logs/controller.log <==
[07/04/19 06:07:42] seafile-controller.c(453): pid file /seafile/pids/seafevents.pid does not exist
[07/04/19 06:07:42] seafile-controller.c(486): seafevents need restart…
[07/04/19 06:07:42] seafile-controller.c(79): spawn_process: /usr/bin/python2.7 -m seafevents.main --config-file /seafile/conf/seafevents.conf --logfile /seafile/logs/seafevents.log -P /seafile/pids/seafevents.pid
[07/04/19 06:07:42] seafile-controller.c(94): spawned /usr/bin/python2.7, pid 23613
[07/04/19 06:07:52] seafile-controller.c(453): pid file /seafile/pids/seafevents.pid does not exist
[07/04/19 06:07:52] seafile-controller.c(486): seafevents need restart…

修改了/seafile/conf/gunicorn.conf
bind = “0.0.0.0:8000”
重启服务后还是不行

把错误界面和报错日志信息发来看下,感觉可能是数据库的问题

桌面客户端一直正常
网页登录前是正常的,输入用户名密码登录后浏览器网页里面就只剩下空白了

刚发现有个临时的办法
我在浏览器地址栏里面随意伪造一个链接(就在后面随便加个字符 ),可以看到


此时点击左右的图标又可以正常访问

然后这个浏览器用这个帐号暂时就正常了
关闭浏览器一段时间或者换个浏览器还得同样操作

感觉是http权限相关,可是这个临时的办法可以绕过?这算不算一个安全例外?

您好,我从6.3.4升级到7.0.4也出现了这个问题,您这个问题解决了么?
是如何解决的呢?

目前只有我前面说的办法,还有就是用firefox

好吧,多谢,您说那个办法确实可以…不过我Firefox和Safari上都是这个情况。

看看地址栏的地址 跟你设置的是不是有出入