I don’t hope that, if they do they 'll get the same issues that nextcloud etc. have.
Let Seafile just bee a sync software and stick with that.
2 Likes
There should rather be plugins to integrate Seafile itself to other apps.
1 Like
Nextcloud is the brother of owncloud. Everybody talk about it. Its a centre of attention.
I have heard about seafile on mondedie, specialized forum. So the solution is not enough know from the consumers.
I have tested both solution and seafile can do more and better than Nextcloud.
- Trusted sync via the app (no duplicate content and if there is, its mentionned)
- Easy installation (seafile.sh and seahub.sh) and userfriendly
- Synchronisation is possible via mobile for pictures and videos. (Nextcloud app is bugged)
- Security about the sync. Files are encrypted and cant be open outside the app
- Better performance on small server
I use both apps since 2 years and i always come back on seafile.
3 Likes
I agree here IF you are good with CLI, Seafile needs to improve regarding upgrades and easy setup for beginners. The installer script needs regularly updates.
Also there should be a script which installs dependencies depending on the version you are running. Right now this is missing.
2 Likes
Someone (preferentially the Seafile-Team because of security) could make a DEB-package for the server. It was stated that they will not include the server into the official Debian repository - which has a few good reasons. But creating a DEB package has the advantage that the dependencies are managed by the package manager and leads to fewer user errors. The Seafile team should have already experience with packaging (see the Seafile client for example).
Maybe this is a good idea, maybe not - Just a short idea. 
And of course there are other non Debian-based distributions, too.
2 Likes
I moved my 105 users to Owncloud from Seafile after five years.
Replies to my forum posts from moderators such as those in this thread (“Then fix it.”) tells me all I need to know about the community here and the willingness to help other users.
Sorry, I’m not sure what you want. You found out by yourself, that MCAffee has a negative effect on other applications. Obviously this is a bug in the mcaffee software. So tell them they should fix the bug.
I don’t understand why third party software should work around a bug mcaffee introduces.
3 Likes
Did you use OC with that many users before? I understand you point, but several Clients I worked as consultant for, actually switched away from MA because of similiar issues. So you cannot really blame Seafile for this problem.
If you did not use the pro version of Seafile you cannot expect immediate support, this is a community.
Anyways, hope you get your clients happy.
What proxy did you use in front of Seafile?
1 Like
It was configured with Nginx.
Honestly I prefer Seafile for the more robust sync and the ability to revert the libraries as a whole … but working in a corporate with 20,000 users the decision to install McAfee (or not) isn’t mine. I realise there’s a conflict between Seafile and McAfee on our particular systems - but it’s not really simple to say it’s one product or the other.
I wasn’t really left with much choice but to find an alternate solution. I just didn’t feel like I got that much help here, particularly with the comment I highlighted which I found quite rude and abrupt. Regardless of that I spent days of my time trying everything I could to work around the issue before throwing in the towel.
CE or pro? Did you purchase any support?
CE.
I didn’t expect someone to jump on my issue, but some politeness and community-minded suggestions would have helped.
2 Likes
I’m taking seafile for a spin currently, and there’s one killer feature that owncloud/nextcloud have (my current system) that I cannot figure out in seafile.
I run my system through NAT for external connectivity. However, when I’m in the LAN, I can easily open the broswer, or configure LAN only clients, to use the internal address and have no difficulties.
From what I can tell, this setup is not possible. I have windows apps working just fine, but when I try to use the android app I get a download failed, because the file_server_root binds to only one specific address. A usable system for my needs requires that I be able to access internally, directly, through an IP address that is always going to be different than the dyndns domain/ip address.
Also, I have users that VPN into the lan, and that trips the same situation.
If I can work around this, I really like seafile as an OC/NC replacement. Unfortunately I’m gong to have to continue my search unless I can figure a way around this.
You’ll need to set up split horizon DNS for that.
arjones85, Thanks for the pointer. It looks like that solution could work.
I’ve got to admit I think it a bit ridiculous that we have to use DNS tricks in order to be able to access the full functionality of the seafile when the other alternatives I try this is a non-issue.
Granted the back-end is more complex, but I would figure if the server can listen to any IP address, that with a logged in user it could determine the referer’s access method and use that instead of the base webUI working but file downloads not.
I am curious as to why the android client would not be working, as even if it’s getting your external IP from dyndns, the traffic should still work. It would just be leaving your router and turning right back around to grab the data from the external side. Slower then internal of course, but should still work.
You have followed the manual regarding nat setup, right? https://manual.seafile.com/deploy/deploy_seafile_behind_nat.html
I may not have been very clear, my mistake. Basically it was user error in the seahub_settings.py file
I installed the current version and deployed it with the seafile install script from github: https://github.com/haiwen/seafile-server-installer
Which worked great until I tried to use the webUI/android app over wifi on the same subnet as the server.
Turns out the script sets the bound IP address by default to 127.0.1.1 (incorrect loopback).
This threw me for a loop until I went into the config files and changed the bound address to the correct IP/hostname.
Since the windows client worked prefectly I did not think to inspect the config files initially until after I finally noticed that the webUI was pointing to the incorrect loopback. Once I figured that out it works fine over the LAN/NAT
Basically it was user error on my part, but my issue would still remain in our production setup where I need it to listen on 2 seperate interfaces, out LAN/NAT interface, and a seperate private VPN endpoint on a subnet that is not serviced by DNS and I’m restricted from editing any hosts files, especially on mobile clients where I don’t have jailbroken/rooted users.
As a home solution I’m very much leaning to migrating away from my personal OC install once I verify that seafile works well in all my use cases.
Unfortunately it may not work well for me in our business setting.
Unless…
Can I run 2 concurrent instances of seafile, each bound to different ports?
If I can do that with just some duplicate configuration files, I might be able to provide a work around that will be acceptable to our users.
Currently I’m testing out syncrify, but so far I much prefer seafile to any other solution I’ve seen.
You should always be running seafile behind an nginx or apache proxy, this is the supported method.
Configure nginx / apache to listen on what interfaces and ports you want it to listen to.
https://manual.seafile.com/deploy/deploy_with_nginx.html
Edit: I recognize now that you may still run into an issue with the SERVICE_URL and FILE_SERVER_ROOT having to be hardcoded to only one address. I am unsure how you can get around that if clients connected to your VPN endpoint will be unable to reach your external address. Only solution I can think of right now is fix your routing so that VPN clients can still reach the external address, or configure dns to hand out internal address on the internal network and external address on the external network for your seafile dns address, then nginx / apache to listen on all the interfaces it needs to listen on.
I do not believe seafile supports multiple server daemons accessing the sql database/data directory at the same time.
I’ve currently got it deployed behind nginx, with nginx handling the https, etc.
The config script in the manual sets it all up by magic, and that works like a charm.
Unfortunate about not being able to support concurrent daemons.
However, I was granted permission to install in our production env for long term testing with the typical NAT configuration, and to test with all of our non mobile connections by editing the hosts file for use over our VPN.
If this tests sucessfully I think we’ll be migrating over to seafile completely…
I appreciate all the help, this looks to be a really fantastic product.
I had ownCloud for a couple of months until I too lost some data, and then switched to SeaFile. Much easier both from a front end (to use) and back end (to maintain) perspective.
2 Likes
I’m surprised that no one here mentioned de-duplication - that is main Seafile feature for me. Wild dedup I can have “unlimited versions” for my libraries.
If I change simple mp3 tag in Owncloud/Nextcloud - they will store new file version with full size and and wasting space. Seafile will only store changed data.
2 Likes