• Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by noiime

  1. Is this supposed to still be active? It doesn't seems to work anymore!? When I try to install the key I get this: Executing: gpg --ignore-time-conflict --no-options --no-default-keyring --secret-keyring /etc/apt/secring.gpg --trustdb-name /etc/apt/trustdb.gpg --keyring /etc/apt/trusted.gpg --primary-keyring /etc/apt/trusted.gpg --keyring /etc/apt/trusted.gpg.d//innvue.gpg --keyring /etc/apt/trusted.gpg.d//pkg-mozilla-archive-keyring.gpg --keyserver --recv-keys 992A3C9A3C3DE741 gpg: requesting key 3C3DE741 from hkp server ?: Connection refused gpgkeys: HTTP fetch error 7: couldn't connect: Connection refused gpg: no valid OpenPGP data found. gpg: Total number processed: 0
  2. I don't have the issue anymore. I just let it that way and after a day the issue was resolved by itself.
  3. The fact that plugging back the HDD with 2.2.7 is working, it doesn't seems to be related with blacklisted IP or a network issue. At least on my end... I was reviewing my posts and I saw that I forgot to mention that I am using the unofficial sync repos I'm not sure it is relevant because it seems to happen with other OS.
  4. Same problem here. I have two sites that are doing the same behavior as described. - OS on both site is Debian 7 One site I just upgraded 2.27 to 2.36 and it wouldn't see any tracker/peers after the upgrade. ** Before the upgrade, it was working fine! I even tried to uninstall/reinstall and redo all the shares from scratches and it's always the same result On the other site, because of some bad clusters, I had to change the HDD and I installed rev. 2.3.6 on the new HDD. Note that the OS installation came from a staging IPX server so, except for btsync, it is exactly the same as the old HDD. If I put back the old HDD that was having 2.2.7 installed, it connect to PEERS very quickly and as soon as I reconnect the new one with 2.3.6 it show "cannot-get-the-list-of-trackers" ... It seems it can see peers but for some reason broken pipes happen. Not sure if it is related to this issue but here's what I can see in the logs. [20160404 15:00:39.424] PD[2429] [6AA5]: checking tunnel connection to peer, transport: TCP, endpoint: [20160404 15:00:39.424] PD[2429] [6AA5]: checking tunnel connection to peer, transport: TCP, endpoint: [20160404 15:01:00.422] SyncSocket[0x00007f33b8044080]: an error has occurred - code: 32, message: "Broken pipe" [20160404 15:01:00.422] SyncSocket[0x00007f33b80405e0]: an error has occurred - code: 32, message: "Broken pipe" [20160404 15:01:00.422] PD[2429] [6AA5]: failed to open TCP tunnel - endpoint: :56634, status: "Broken pipe", enc: SRP, socket: 0x00007f33b8044080, tunnels: 0 [20160404 15:01:00.422] PD[2429] [6AA5]: failed to open TCP tunnel - endpoint:, status: "Broken pipe", enc: SRP, socket: 0x00007f33b80405e0, tunnels: 0 I don't have access to the firewall so I can't test if it is working with predefined host but since it is working with 2.2.7 and not with 2.3.x the problem isn't a firewall issue.
  5. LOL The same happen with me too!!
  6. I had to install btsync from scratch on one of my peers and, am I missing something or the "Show Columns Options" are missing in btsync 2.2? I've verified on Windows & Linux version and I can't seems to find it. Am I blind or what ? Thanks Nevermind, I just found it....arrrg 2 min after sending my post!! For those like me who were wondering where theses options are, just right click on the status bar and you will see them appears!
  7. Is it possible that Windows 2008 std (Non R2) isn't supported? I am having these errors: 2015-09-14 16:27:25] SSLEH[0x0000000008233d80]: hello packet { share:A40523629553E1FD23E5D4B7FA2ACB88C95C40A8 } has been sent [2015-09-14 16:27:25] SSPI[0x000000000ca82920]: Create SSPI encryption holder [2015-09-14 16:27:25] SSPI[0x000000000ca82920]: Handshake: failed to acquire credentials handle, error - 0x80090331 [2015-09-14 16:27:25] SSPI[0x000000000ca82920]: Handshake: failed to acquire credentials handle, error - 0x80090331 [2015-09-14 16:27:25] PD[43E5] [5184]: Checking tunnel connection to peer, transport: uTP, endpoint: [2015-09-14 16:27:25] SSLEH[0x00000000080da8a0]: hello packet { share:A40523629553E1FD23E5D4B7FA2ACB88C95C40A8 } has been sent [2015-09-14 16:27:25] SSPI[0x000000000ca821b0]: Create SSPI encryption holder [2015-09-14 16:27:25] SSPI[0x000000000ca821b0]: Handshake: failed to acquire credentials handle, error - 0x80090331 [2015-09-14 16:27:25] SSPI[0x000000000ca821b0]: Handshake: failed to acquire credentials handle, error - 0x80090331 I saw those same error message on another post regarding Vista so that's why I wonder if it's the same with win2008 (non R2) It's the first time I have to install btsync on a windows 2008 std (Non R2) so before I go further into my diagnostic I will need to know if it could be an OS incompatibility or not? Thanks!
  8. Most of my peers are Debian Wheezy and I didn't have to do anything after modifying the init file. But, apparently, on Debian Jessie it's important to do a "systemctl daemon-reload" for btsync to start after the modification to the init file.
  9. @RomanZ I confirm, it's working on my side too. Thanks to you, the workaround is now completed. Keep up your good work!!
  10. @Borph thanks a lot, apparently removing the "--log sync.log" did the trick and there's no need to bypass the btsync-daemon. I didn't notice it because when you execute it manually with the "--log sync.log" option, it actually start so, I never thought removing that option from the init file would make it worked... weird!!? So finally the workaround can be resumed in 2 steps 1- Edit the config file /etc/btsync/debconf-default.conf and remove "folder_defaults.use_dht" : false, 2- Edit the init file /etc/init.d/btsync and in the "Start btsync" section, remove the --log sync.log 2- Edit the init file /etc/init.d/btsync and in the "Start btsync" section, add the complete path to the log file EDIT: In fact you don't need to remove "--log sync.log" you just need to add the complete path ie: "--log /var/lib/btsync/sync.log" If you remove it btsync will no longer log anything. I thought it would create a "sync.log" automatically somewhere but apparently it doesn't.
  11. I found a workaround! *** NEVER MIND, this is not working after a reboot and frankly, I don't know why it was working at first!? Edit the config file /etc/btsync/debconf-default.conf and remove "folder_defaults.use_dht" : false, After that you need to bypass btsync-deamon at the start-up so edit /etc/init.d/btsync and replace DAEMON=/usr/lib/btsync/btsync-daemon by DAEMON=/usr/lib/btsync/btsync-core/btsync-core sudo service btsync start VoilĂ , btsync 2.2 is now running ** I'm not sure exactly what it implies to bypass the btsync-deamon but at the moment, and as far as I can tell, it doesn't seems to generate any issues... Note that if you make a change using "dpkg-reconfigure btsync" you will have to edit the config file again. Like I said, this is just a workaround it's not a fix It work if you start it manually ie: /usr/lib/btsync-core/btsync-core --config /etc/btsync/debconf-default.conf But I can't seems to find out what in the init script is causing the issue
  12. Correction... it's not happening with the "change ownership notifications", only with "hints notifications" pop up. I sure wish I could try with another browser but, I don't know how to force the "hint notification" to appear at will. If so, I could reproduce the bug easily and see if other browser are affected. I'm sure that if I do a clean install the pop up "hints notifications" would eventually show up and then I could test it but unfortunately, for now, I have no spare time to debug this issue. As I said, it's not an important issue, it is just annoying when it happen!
  13. When a notification box appear (ex: hint or change ownership) I then click on the X to close it and, for some reason, a blank new navigation tab open within my browser!? As far as I know, this issue is present in all version of 2.1.x, including 2.1.3. ** I just experience it with sync 2.1.3 x64 linux I am using the latest firefox, I don't know if it happen with other kind of browsers. It's not a big problem but it's kind of annoying!
  14. @STUBR.BS I confirm, It's working for me also with 2.1.3. In some point in the time did you manually edited your config file? If so, you probably have an ownership or right issue with your config file. Here's the address for the previous version:
  15. @chrisvdb You are right, I didn't do my homework correctly. Still, it was functioning the way I've done it but the right way should have been like you said. Instead of replacing "/usr/lib/btsync/btsync-daemon" I should have replaced "/usr/lib/btsync-core/btsync-core" Thanks for pin pointed me my error
  16. I was experiencing problems with the latest version on the repository (2.0.93) and before diagnosing more I needed to upgrade to 2.0.120 as quick as possible. Since Toxpoldo is a busy guy, he doesn't seem to currently have spare time to update the repository for us. So I tried updating some of my clients manually without affecting the current config. For those who wish to do the same, the workaround is very easy!! - Download btsync for linux. - Extract it to the folder of your choice. - Stop btsync - Make a backup of the current executable ie: "mv /usr/lib/btsync-core/btsync-core /usr/lib/btsync-core/btsync-core-bak" - Copy the new btsync executable to /usr/lib/btsync-core/ and rename it "btsync-core" ie: "cp /home/user/btsync /usr/lib/btsync-core/btsync-core" - Start btsync and there you go, btsync 2.0.120 running and still with it's current config/shares. Note that when a new version will be posted on the repo I cannot guarantee that you will be able to upgrade it automatically via apt-get. You will probably need to replace the new executable by the old backup one. . Hope it can help some of you while waiting for the repo to be updated. *** BTW, it seems that 2.0.120 fixed the issue I was having with 2.0.93 Cheers!!
  17. @Mike2700 I had a similar issue except for me it's not the master server that is using Windows 2003 it's some of our clients . What I did to fix the issue is not elegant but it's working great and is stable. To Summarize: In Windows 2003, using Virtualbox, I've built a VM with a minimal install of Debian. Then in windows 2003 I've shared the folders needed to be synced with btsync. In the VM I've mounted the windows 2003 shares. I've installed Btsync and connected to the mounted shares and voilĂ !! Btsync 2.0 is now working for windows 2003 or Windows XP Note that for some weird reason, this set-up is even more stable than using 1.4.111 with Windows 2003
  18. Weird, I've been able to reproduce it on each server that I've tried. At least on 5 different server. Maybe it is only happening with the tuxpoldo unofficial server packages!? Since It's not really a big problem, I will wait until my next debian installation to reproduce the issue and send you back the info you ask.
  19. @Helen 1) Yes, of course, I've tried restarting btsync 2)Already tried, no effect. 3)Correct Thanks for your answer
  20. The workaround I found is to divide the limit by 10. in your case, if you want to limit the download at 20K just put 2 instead of 20
  21. I too have similar issue. It is still not resolved!
  22. I encountered the same issue after upgrading 1.3.94 to 1.3.105. If you had the address in your bookmark, you should change it for "" The old path "" isn't working anymore with BTS 1.3.105
  23. OS: Debian X64 Btsync: 1.3.105 This is really not a big bug but still it shouldn't happen that way! When adding a new folder, from the Web UI, and by accident you put a space before the secret, btsync crash instantly. In my opinion, instead of crashing, it should simply tell you that your secret key is invalid.
  24. Thanks "jaymacspurs", I was about to publish a similar post! We don't use Macbook/IOSx, but still, we also have similar behavior between some of our peers! ---slow speed/no speed---stop/start btsync---good speed again...but for how long?? I've seen this issue on OS like, Win 2008, win 8/8.1 & Debian all those running BTS 1.3.94/1.3.105. On our side, & for some reason, this issue appear only on few peers, but still, it is happening somehow! So far than I know, nothing suspicious in the debug log, It just stop transferring for some unknown reason!? Any idea's? .
  25. OS: Debian Squeeze x64 Btsync: 1.3.105 Changing the password from the preferences in the web UI is working only until you restart btsync. After a restart, btsync will regain it's old password. tx ** I forgot to mention, using "dpkg-reconfigure btsync" the password changed is applied correctly.