todorb

yes, that's my setup. the automatic forwardings work. i verified that by telneting from outside to the public port. the router (RT-AC66U) shows the forwardings: Destination Proto. Port range Redirect to Local port...ALL TCP 14563 192.168.1.100 14563 ALL UDP 14563 192.168.1.100 14563 ... and the process listens there: [~] # lsof -P -i 4|grep 14563btsync 4689 admin 7u IPv4 3494377 0t0 TCP *:14563 (LISTEN)btsync 4689 admin 9u IPv4 2134800 0t0 UDP *:14563 the process is version 1.3.106, provided by qnap.

1.4.75 crashes too.

and i had some limited success. after sitting for several days with a proxy configuration my shares were synced and showed peers. but then i had to reboot the work pc and the peers were lost. after many days they are still not reconnected. and what is more interesting is that for one of the shares the work node claims that it has a peer at home, but the home node says it has no peers.

+1 for this request. but that's only a start. for true backup we need to be able to: 1. access past versions of files. think of some file content becoming garbage, instead of the file getting deleted. the remote node should be able to hold some configurable number of periodic "snapshots" of the tree, and the ui should have a nice way to say "get a copy of this folder as it looked a week/month/... ago". 2. occasionally verify that the remote node has the correct file contents. either automatically or on demand btsync should be able to compare local to remote files by hashing the full content. and there should be ui for reporting mismatches and taking action. backing up to an untrusted location is a killer feature for me. but we're not there yet. what i currently do is btsync to an offsite encypted node, and also periodically rsync to an external hdd at home, and for some syncs use the --checksum option to see that both hdds are readable. that gives me kind of nice backup, but requires manual work. it would be great if a btsync node (really, the encrypted one) can be designated as having a backup role and automatically does what a good backup needs.

consider yourself lucky, because you can sync one more folder than me i'm trying to run the latest btsync on my work pc, through a socks5 proxy that provides unrestricted internet access. other programs work though this proxy. btsync finds no peers and i see similar errors in the debug log: [2014-08-29 18:05:37] Closing TCP tracker connection to 54.225.92.50:3000. Error 10054[2014-08-29 18:05:59] Closing uTP tracker connection to 54.225.92.50:3000. Error 138 my folders have default settings, except that "search lan" is turned off, but it didn't make a difference. netstat shows that there's a connection between btsync and the proxy. wireshark doesn't capture packets to the tracker when the proxy option is selected. when i deselect the proxy option wireshark starts showing such packets. so obviously the proxy is being used. the remote nodes i want to connect to are at home (behind nat) and they have configured port forwardings for themselves using upnp. i see them in the router's ui. non-work devices connect to them just fine. can some btsync devs give ideas on how to debug this issue? are there any special requirements for running behind proxy?