Firon
-
Posts
59 -
Joined
-
Last visited
-
Days Won
1
Posts posted by Firon
-
-
It's not a DDoS. Configure your firewall to be less aggressive or whitelist Sync.
-
It's supposed to be for personal sync. It's also in the name - sync is short for synchronization. That includes deletes.
-
If you didn't write down/save the full code anywhere, then it is lost for good. You'll need to regenerate the secrets and redistribute them to the clients.
If you can backup Sync's data on your Android device and restore it to your new device (this would need root), then you could restore that on the new device.
-
You cannot. Sync is meant to synchronize all clients to be identical.
It will keep deleted files in .SyncArchive for a period of time, though.
-
You might wanna check your config file. Why do you have doctype headers in it?
-
As mentioned in the post right above yours, this is an Android limitation. There is no workaround beyond that.
-
Unfortunately on Windows, reading a file locks it and prevents writes.
You can add it to the syncignore list (using wildcards) to prevent it from being synced.
-
Don't use sudo to run it. you'll also need to chown btsync's files to be owned by the user you're trying to run it as.
-
Just add the same sync secrets to your iOS clients that you have on the Android one.
-
The whole point of Sync is that there is no cloud, only your own machines.
-
No. The client requires the torrent protocol, as that's how it's built to sync data. It'd require a massive overhaul in the way that Sync works just to allow for this very specific case.
-
The Synology NAS supports Sync quite well.
-
I'd strongly recommend writing an upstart script over the old sysv init stuff. It's a lot cleaner, and you can use it on Ubuntu.
-
btsync does not use atime for anything.
-
sdcard/Android/com.bittorrent.sync
or something like that is the dir you need to use.
-
Intel only. Very few applications support PPC macs nowadays.
-
Totally unrelated. Sync doesn't use TLS.
-
Update to the newest version of Sync. You're on a very old version. Newest desktop build is 1.3.87
Keeping autoupdates on is a good way of ensuring you always are.
-
Might need to replace the webUI zip too.
-
The relay is used when you have two nodes that can't talk to each other directly (even with STUN and other forms of hole punching). It's to ensure your devices can still sync.
You can disable it, but your devices will no longer be able to sync until you resolve the connection issue.
-
Not for Windows, no. It does not use OpenSSL on Windows.
For non-Windows machines, all you'd need to do is restart btsync after updating OpenSSL if you were using one of the vulnerable versions.
-
As a workaround, you can increase your ulimit for open files. I guess the newest BTSync isn't closing files correctly.
-
It's probably inheriting limits from the system process that actually started it.
The easiest fix is to modify the init script to explicitly set ulimit. A lot of start scripts already provide a mechanism to specify it via the defaults file, but YMMV.
-
Hmm, okay.
Does it match what you see in /proc/$pid/limits too?
Ignore Junction In Windows 7 (Syncignore)
in Sync Troubleshooting
Posted
Why are you using a junction there? You can just tell Windows to move those directories and update the system variables, instead of using a junction (from the properties dialog).
Or use a native symlink instead of a junction point. mklink /D link target