Innus
-
Posts
4 -
Joined
-
Last visited
Posts posted by Innus
-
-
Just to close this issue - the problem turned out to be my VPS host - they were blocking outgoing UDP traffic on their router and it was completely destroying btsync. I'm on their whitelist now and its working great. Hopefully this helps someone else - check with your host!
-
I'm having the same problems you describe. The logs on the server and client indicate that they see each other, but nothing happens in the UI to suggest a transfer needs to happen. And thus it doesn't sync.
-
I'm having some problems getting btsync working. Here is my setup:
Server::
I've been trying to setup btsync on a headless Ubuntu (12.04 64 Bit) server using BitTorrent Sync 1.1.48 [btsync_x64.tar.gz]
Client::
I'm using the OSX Bittorrent Sync 1.1.48 (1.1.48) client.
Problem::
I've been able to get client and server both running, I've been able to connect and configure the server using the Web UI, and I've (after that didn't sync - see config JSON given below) also tried setting up the server using a sync.conf file too. I've got no error messages.
The problem is that they just won't see each other/sync, so I suspect it's a firewall/router issue. I've included my iptables rules below.
I've done all the regular stuff with setting up sharing (generating a hash, adding it on both servers etc), but just nothing starts up.
I'd sure appreciate it if anyone could just check there's nothing obvious that I might have missed.
More info:
Here is my sync.conf file, which I am loading like so: ~/.btsync/btsync --config ~/.btsync/sync.conf (comments removed)
sync.conf file:
{
"device_name": "Capsicum Sync Server",
"listening_port" : 44738,
"storage_path" : "/home/ian/.btsync",
"check_for_updates" : true,
"use_upnp" : true,
"download_limit" : 0,
"upload_limit" : 0,
"webui" :
{
// "listen" : "0.0.0.0:8888",
"login" : "admin",
"password" : "password"
}
,
"shared_folders" :
[
{
"secret" : "ADDK4FEGH3LY7JEJ5ZCXWUKDCSVSQZTZL",
"dir" : "/home/ian/BTSync_two",
"use_relay_server" : true,
"use_tracker" : true,
"use_dht" : true,
"search_lan" : false,
"use_sync_trash" : true,
"known_hosts" :
[
"46.165.251.69:51547"
]
}
]
}MY IPTABLES RULES:
*filter
# Allows all loopback (lo0) traffic and drop all traffic to 127/8 that doesn't use lo0
-A INPUT -i lo -j ACCEPT
-A INPUT ! -i lo -d 127.0.0.0/8 -j REJECT
# Accepts all established inbound connections
-A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
# Allows all outbound traffic
# You can modify this to only allow certain traffic
-A OUTPUT -j ACCEPT
# Allows HTTP and HTTPS connections from anywhere (the normal ports for websites)
-A INPUT -p tcp --dport 80 -j ACCEPT
-A INPUT -p tcp --dport 443 -j ACCEPT
# Allows SSH connections
#
# THE -dport NUMBER IS THE SAME ONE YOU SET UP IN THE SSHD_CONFIG FILE
#
-A INPUT -p tcp -m state --state NEW --dport 22 -j ACCEPT
# Allow ping
-A INPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT
# btsync:
-A INPUT -p tcp --dport 3838 -j ACCEPT
-A INPUT -p udp --dport 3838 -j ACCEPT
-A INPUT -p tcp --dport 44738 -j ACCEPT
-A INPUT -p udp --dport 44738 -j ACCEPT
# log iptables denied calls
-A INPUT -m limit --limit 5/min -j LOG --log-prefix "iptables denied: " --log-level 7
# Reject all other inbound - default deny unless explicitly allowed policy
-A INPUT -j REJECT
-A FORWARD -j REJECT
COMMIT"Please let Sync collect logs for at least 15 minutes to get enough information."
OK - I've attached these files, both for the server and the OSX client. (after enabling debugging with echo "FFFF" > .sync/debug.txt on the server).
Note, I'm seeing this on OSX - does this mean it's at least *seeing* the server:
Got list of 1 peers from 54.225.92.50:3000
Got list of 1 peers from 54.225.100.8:3000
Got list of 1 peers from 54.225.100.8:3000
Here's hopefully..
Ian, @id
BTSync - DNS 343 NAS w/Debian CHROOT - Working but not transferring any files
in Sync General Discussion
Posted
Just to follow up: the problem for me turned out to be my VPS host - they were blocking outgoing UDP traffic on their router and it was completely destroying btsync. I'm on their whitelist now and its working great. Hopefully this helps someone else - check with your host just in case they're doing the same to you!