Seafile and seahub start but nothing will connect after upgrade

Seafile Server
1

I am stumped on this, I just upgraded from 6.3 to 7.02 and now nothing works. seafile says it starts fine, same for seahub but when i try to use the desktop app or the web gui they just time out.

My ccnet.conf

[General]
USER_NAME = #######
ID = c22##############ee3d5
NAME = ########
SERVICE_URL = htt########.mynetgear.com:8000

[Client]
PORT = 13419

[Database]
ENGINE = mysql
HOST = 127.0.0.1
PORT = 3306
USER = seafile
PASSWD = ######
DB = ccnet_db
CONNECTION_CHARSET = utf8

and my seahub_settings.py

-- coding: utf-8 --

SECRET_KEY = “##########”

DATABASES = {
‘default’: {
‘ENGINE’: ‘django.db.backends.mysql’,
‘NAME’: ‘seahub_db’,
‘USER’: ‘seafile’,
‘PASSWORD’: ‘#######’,
‘HOST’: ‘127.0.0.1’,
‘PORT’: ‘3306’
}
}

2

If you are running in Linux, can you list the seafile processes that are running? Example command:

ps -aux | grep seaf
3

boris@boris-PVR:/var/log$ ps -aux | grep seaf
boris 1935 0.0 0.0 60308 3208 ? Ss 23:08 0:00 /opt/seafile/seafile-server-7.0.2/seafile/bin/seafile-controller -c /opt/seafile/ccnet -d /home/boris/seafile-data -F /opt/seafile/conf
boris 1937 0.0 0.1 168520 9228 ? Ss 23:08 0:00 ccnet-server -F /opt/seafile/conf -c /opt/seafile/ccnet -f /opt/seafile/logs/ccnet.log -d -P /opt/seafile/pids/ccnet.pid
boris 1939 0.0 0.1 1002284 9212 ? Ssl 23:08 0:00 seaf-server -F /opt/seafile/conf -c /opt/seafile/ccnet -d /home/boris/seafile-data -l /opt/seafile/logs/seafile.log -P /opt/seafile/pids/seaf-server.pid
boris 1969 0.0 0.7 100232 57804 ? S 23:09 0:00 python2.7 /opt/seafile/seafile-server-7.0.2/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf --preload
boris 1975 0.0 0.6 100444 49868 ? S 23:09 0:00 python2.7 /opt/seafile/seafile-server-7.0.2/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf --preload
boris 1976 0.0 0.6 100444 49876 ? S 23:09 0:00 python2.7 /opt/seafile/seafile-server-7.0.2/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf --preload
boris 1977 0.0 0.6 100444 49880 ? S 23:09 0:00 python2.7 /opt/seafile/seafile-server-7.0.2/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf --preload
boris 1978 0.0 0.6 100444 49884 ? S 23:09 0:00 python2.7 /opt/seafile/seafile-server-7.0.2/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf --preload
boris 1979 0.0 0.6 100444 49888 ? S 23:09 0:00 python2.7 /opt/seafile/seafile-server-7.0.2/seahub/thirdpart/gunicorn seahub.wsgi:application -c /opt/seafile/conf/gunicorn.conf --preload
boris 2222 0.0 0.0 8988 904 pts/0 R+ 23:47 0:00 grep --color=auto seaf

4

I tried logging in with Just my local network 192.168.0.138:8000 but that does not with either. It’s there anything I can check on the server itself to see if it’s a seafile issue or if its a networking problem

5

Could you post the gunicorn.conf?

I think one possible reason is that seafile 7 changes the listening address to 127.0.0.1, so it cannot be accessed from other hosts without using a proxy server.

If this is the case, you should setup a proxy server, or change the listening address to 0.0.0.0 in gunicorn.conf

2 Likes
6

That was it, it works now! thanks. I changed it to 0.0.0.0:8000 in gunicorn.conf and everything is back working.

1 Like
7

Thats it - thanks so much