suhrim

Members
 View Profile  See their activity

  • Posts

    14

  • Joined

  • Last visited

 Content Type 

Posts posted by suhrim

  3. Btsync On Debian Api Key Issues

    in Developers

    Posted

    Hello

     

    Sorry for my absence I haven't really had any time for this.

     

    My troubles seems to be related to my hardware in some way. I'm going to try to install on another machine that has the same Asus motherboard as I have in my server.

     

    Asus E35M1-I with latest bios and 8Gb of ram.

     

    I did run memtest on it for more than 12 hours without errors and everything else works fine.


    I tried with the file you sent me again (I had to upgrade glibc to a newer version) it works however.

  5. Btsync On Debian Api Key Issues

    in Developers

    Posted

    logged traffik when restarting the service.

     

    18:00:29.415107 IP 8.8.8.8.53 > 192.168.10.32.34965: 20696 3/0/0 CNAME syncdev-1159813985.us-east-1.elb.amazonaws.com., A 50.16.235.95, A 50.17.249.15 (129)
    18:00:29.448157 IP 8.8.8.8.53 > 192.168.10.32.39291: 64680 3/0/0 CNAME syncdev-1159813985.us-east-1.elb.amazonaws.com., A 50.16.235.95, A 50.17.249.15 (129)
    18:00:29.605404 IP 50.16.235.95.443 > 192.168.10.32.54110: Flags [s.], seq 1340296521, ack 1218851029, win 14480, options [mss 1460,sackOK,TS val 249083623 ecr 374119,nop,wscale 8], length 0
    18:00:29.717213 IP 50.16.235.95.443 > 192.168.10.32.54110: Flags [.], ack 322, win 61, options [nop,nop,TS val 249083651 ecr 374147], length 0
    18:00:30.075726 IP 50.16.235.95.443 > 192.168.10.32.54110: Flags [F.], seq 4274, ack 1307, win 77, options [nop,nop,TS val 249083741 ecr 374236], length 0

  6. Btsync On Debian Api Key Issues

    in Developers

    Posted

     

    @suhrim

     

    Try stopping all instances and run a new one from console, like:

    killall btsync./btsync --no-daemon --config <config_path_and_filename>
    root@nas:/usr/lib/btsync# ./btsync-daemon --nodaemon --config /etc/btsync/debconf-default.conf
    Warning: config option 'lan_use_tcp' is deprecated
    total physical memory 536870912 max disk cache 2097152
    Using IP address 83.254.XXX.XX
    Loading config file version 1.3.105
    Loaded folder /mnt/media/johan/foton
    Invalid API key. Terminating
    Shutdown. Saving config sync.dat
    root@nas:/usr/lib/btsync#
     
    what hostname does it verify the api key against? I would like to check if I can contact tha host at all.

  7. Btsync On Debian Api Key Issues

    in Developers

    Posted

    @RomanZ

     

    I have tried putting the server at home on a public ip and it still doesn't work. The one I installed at work is configured the same way and it works there. What host is used for verifying thet api key? I would like to test if I can contact it from my isp at home.

  12. Btsync On Debian Api Key Issues

    in Developers

    Posted

    @suhrim

     

    I suggest that you've copypasted the key to avoid any possible typos. Please also make sure that the text editor did not put any extra line breaks in the API key.

     

    If all of the above is not the case - please send me your config file with the key, I'll test it in my lab. Please use syncapp@bittorrent.com mail address and refer to this forum topic.

    Thanks for the respons.

     

    I run dpkg-reconfigure btsync to configure and pasted the API key from the mail I got. When looking in the config file afterwords I can't see any extra characters of line breaks in the api key. I'm mailing you my config file now.

  14. Btsync On Debian Api Key Issues

    in Developers

    Posted

    You need an api key to get it working right? Got a key from bittorrent but it still says invalid api key in the logs.

     

    Requested the key from:

    http://www.bittorrent.com/sync/developers

    and the keys looks something like this:

    XOCRD6XRFD5HXCLW7WD5XBI52YPKEGARFK3SFE6BSEVRQIVXQNMMLNEXO6PPXB4IG6XXO25CQQ4KFBRDYCXK2W4KR7NXM3XMYE7MYBENETLG6X43FUGY5PDE27ALK6L6YAC3WVA

     

    this is not my real key though I have edited it a bit.

     

    [20140621 00:30:11.016] Invalid API key. Terminating
     
    any ideas? have I missed something trivial there?