just curious if anyone even uses this product anymore, I have had nothing but issues, and not very encouraged when i see all the unanswered threads, I might jump ship to a more stable product
I cannot even get it to install correctly!!!
This forum maybe has such low activity because there are not many problems 
I have Seafile installed multiple times without any problems. So what is the part of the installation which is problematic?
Hey Jack, wow awesome, i wish that was the case for me
I am trying to install Seafile, the first attempt I was all setup but could not get the local login page to appear
I wiped out that version and tried again, I can launch seafile in my tray, but cannot get it to conenct to mysql
The original guide I followed did not tell me to set anything up, just pick my drive, and then login, which I was never able to do.
Any help would be great, this is not being setup on some small box, i own my own dedicated box
I have just deleted the directory and removed everything, including python, to try once more
If the problems remain please post your log files here. There can be many reasons for “cannot connect”.
Let me do another full install then I will post the logs,
logs are attached, I have no clue what they all mean, I followed every step, I smell a buggy software!
ccnet.log
[03/31/17 04:47:31] …/common/session.c(132): using config file D:/seafile-server\conf\ccnet.conf
[03/31/17 04:47:37] …/common/session.c(418): Listen on 127.0.0.1 13418
[03/31/17 04:47:37] …/common/session.c(290): Update pubinfo file
[03/31/17 04:47:37] …/common/connect-mgr.c(515): Opened port 10001 to listen for incoming peer connections
[03/31/17 04:47:37] …/common/session.c(398): Accepted a local client
[03/31/17 04:47:37] …/common/session.c(398): Accepted a local client
[03/31/17 04:47:37] …/common/session.c(398): Accepted a local client
[03/31/17 04:47:37] …/common/session.c(398): Accepted a local client
[03/31/17 04:47:37] …/common/session.c(398): Accepted a local client
[03/31/17 04:47:37] …/common/session.c(398): Accepted a local client
[03/31/17 04:47:37] …/common/session.c(398): Accepted a local client
[03/31/17 06:03:28] …/common/peer.c(941): libevent got an error! what=33, errno=0 (No error)
[03/31/17 06:03:28] …/common/peer.c(943): Local peer down
[03/31/17 06:03:28] …/common/peer.c(941): libevent got an error! what=33, errno=0 (No error)
[03/31/17 06:03:28] …/common/peer.c(943): Local peer down
[03/31/17 06:06:14] …/common/session.c(398): Accepted a local client
[03/31/17 06:06:14] …/common/session.c(398): Accepted a local client
[03/31/17 06:06:40] …/common/session.c(369): Exit at Fri Mar 31 06:06:40 2017
[03/31/17 06:06:40] …/common/session.c(132): using config file D:/seafile-server\conf\ccnet.conf
[03/31/17 06:06:40] …/common/session.c(418): Listen on 127.0.0.1 13418
[03/31/17 06:06:40] …/common/session.c(290): Update pubinfo file
[03/31/17 06:06:40] …/common/connect-mgr.c(515): Opened port 10001 to listen for incoming peer connections
[03/31/17 06:06:41] …/common/session.c(398): Accepted a local client
[03/31/17 06:06:41] …/common/session.c(398): Accepted a local client
[03/31/17 06:06:41] …/common/session.c(398): Accepted a local client
[03/31/17 06:06:41] …/common/session.c(398): Accepted a local client
[03/31/17 06:06:41] …/common/session.c(398): Accepted a local client
[03/31/17 06:06:43] …/common/session.c(398): Accepted a local client
[03/31/17 06:06:43] …/common/session.c(398): Accepted a local client
[03/31/17 06:07:09] …/common/peer.c(941): libevent got an error! what=33, errno=0 (No error)
[03/31/17 06:07:09] …/common/peer.c(943): Local peer down
[03/31/17 06:07:09] …/common/peer.c(941): libevent got an error! what=33, errno=0 (No error)
[03/31/17 06:07:09] …/common/peer.c(943): Local peer down
[03/31/17 06:08:23] …/common/peer.c(941): libevent got an error! what=33, errno=0 (No error)
[03/31/17 06:08:23] …/common/peer.c(943): Local peer down
[03/31/17 06:08:23] …/common/peer.c(941): libevent got an error! what=33, errno=0 (No error)
[03/31/17 06:08:23] …/common/peer.c(943): Local peer down
[03/31/17 06:08:23] …/common/peer.c(941): libevent got an error! what=33, errno=0 (No error)
[03/31/17 06:08:23] …/common/peer.c(943): Local peer down
[03/31/17 06:08:23] …/common/peer.c(941): libevent got an error! what=33, errno=0 (No error)
[03/31/17 06:08:23] …/common/peer.c(943): Local peer down
[03/31/17 06:08:23] …/common/peer.c(941): libevent got an error! what=33, errno=0 (No error)
[03/31/17 06:08:23] …/common/peer.c(943): Local peer down
this damn forum wont even let me paste the logs, and this is a “tried and true” software
I THINK NOT!
It is very difficult to help you if you don’t give any information
Which OS? (I think you use Windows, as the path in the log file says something like “D:/seafile-server/…”)
Which Server-Version?
Are there any entries in the seafile.log, seahub.log, controller.log, …?
1 Like
Jack
Yes it is windows, I could have sworn I gave the specs
It is windows server 2008 standard, 32gb ram, 100tb NAS, 1tb main drive partition, the server is running Plesk 12 with 10 websites, 1 email server, 1 ftp server, 1 shoutcast DNAS, and it also has php, mysql, and IIS on it
As for what is happening I am following the guide at this page to the LETTER
https://manual.seafile.com/deploy_windows/download_and_setup_seafile_windows_server.html
After I complete everything on this page here is what takes place
I can install it, I can install python, I can add the storage drive, I can add an admin user,
I change the SERVICE URL to my DEDICATED PUBLIC IP (the server only has 1 NIC card in it with the PUBLIC IP) and the port is :8000 in the format SERVICE_URL = http://mypublicserverIP:8000
After this i attempt to login to the web interface via 127.0.0,1:8000 or using my publicip:8000 and i get a page saying it cannot connect. I know the seahub is operational because the deamons are active
What I do not get is how this thing could even operate if there is no database setup
BTW I did try to set up the mysql following the mysql deployment page as well, but that also was a dead end
I know this can work, and I bet it is something so tiny that is screwing all this up, any help would be great as to what steps to follow next!
J
Have you checked your firewall?
Well do you mean the server firewall , can you elaborate why this would matter as its failing on the LOCAL address, and port 8000 has always worked before
Then I’d check if there’s another service running on Port 8000.
maybe it is as tiny as typing 127.0.0,1:8000 instead of 127.0.0.1:8000
ok so i did some research, i ran resmon, seaf-server.exe shows a ton of ports , so does ccnet, but NONE are the 8000, and NO I am not typing the 127 address wrong
I think whoever setup that install doc was not paying attention, that is actually par for the course with open source software
I am at the conclusion that this software is very unstable, i have yet to see a single instance it works, I am losing my patience with one line answers
- not the install (followed to the letter)
- not the port not even showing up on netstat or resmon
- not a typon on the address
any other takers
I will happily provide backend access to anyone who thinks they have an idea,
I really think Seafile is not for you 
. With your attitude you will have really difficulty finding support from other community members.
I’m running seafile on Windows Server 2012. And yes, it took a little learning, specially getting IIS configured to work with https and other small items. But I’m more than satisfied with the solution. Running rock-solid managing TBs of data of the complete family across geographies and many different devices.
6 Likes
I disagree
I think the software is amazingly buggy, and the docs are not written to be complete
I am glad you got it working, now would you mind please sharing how you went about that process
if its so robust why is it like pulling teeth
Did you even test connection to seafile with internal IP?
This is obviously the first step, before playing with public IPs in any server configuration. Public IP acces behind NAT is quite often broken, if ruter does not support NAT traversal correctly.
Set everything to internal IPs(check ccnet, seafile and seahub settings) than try connect, if not working try different port, if still not working post all 3 configuration files here and i think we will quickly see the problem.
Most configuration errors in seafile happen when people do not realize you have 3 config files, at least they are all in same folder now:)
-
The server is not near us. It is at a data center , it only has 1 IP, the external one
-
I’ll triple check the ports
-
If your referring to the files in the “conf” folder , sea file ccnet and the py settings , I attempted to share them here and the stupid forum wouldn’t let me
I’ll await further instructions
I wrote a step by step tutorial which works very fine for all my friends: Tutorial for Seafile CE + Nginx + dynamic DNS (on ARM / Cubietruck / RaspberryPi)
This is for GNU/Linux but I installed Seafile server on Windows as well later so maybe it is not a bad idea to take a RPi or a VM with Debian and test everything step by step (snapshots ftw) which would provide you detailed knowledge for later setups.
Seafile server setup is not easy but worth to take the challenge.