Hi, thank you seafile team for creating this product.
First and foremost, my seafile and seahub started without a hitch. But whenever i access
10.0.0.18:8000 or 10.0.0.18:8082 from my chrome nothing working, connect from client nothing working. When i start seafile i have a message shown on terminal not sure it matter or not.
** Message : 09:58:38.265: seafile-controller.c(572): No seafevents.
Hi Dennis, welcome to the Seafile Forum!
For the following answers, I assume you do not run Seafile behind a proxy.
The seafdav.conf is irrelevant because webdav is disabled.
The seafile.conf and the ccnet.conf look ok.
More important are the gunicorn.conf.py and the seahub_settings.py. Please post them too (after removing passwords from seahub_settings.py).
I’d say that your gunicorn only listens to requests from localhost.
Hi rdb, thank you for your prompt reply. I’m very thankful for your technical help.
I’m currently running everything locally, no proxy, everything connected to same network.
Firewall is already unblocked on port 8000, and 8002 as well. I don’t think it matters at this point.
Make sure that you replace WHATEVERNAME and YOURPASSWORD above. I also assume a.) you use MySQL/MariaDB (as opposed to SQLite) and b.) you run your DB on localhost under the default port 3306. The password required in the database block is the password of the database user created when executing ./setup-seafile-mysql.sh This may be the Seafile user, but maybe you gave it a different name.