g2nightmare

Just to clarify, btsync-gui is the same thing except supported? Is it up to date?

bump

I see that you updated the repositories (I think?) There are some bugs you may or may not be aware of. I used a clean install of Kali Linux (debian based) and did an install of btsync-user. Upon installing, the gui icon has an explanation point through it and says "Communication Error 500." Upon providing my secret key and restarting the machine, I always get a "communication error 401" on the gui. Weirdly enough, btsync actually runs. I ran it via terminal and I get something that says: blah blah forked to background (good) /usr/lib/btsync-user/btsyncindicator.py:138 warning at /tmp/buildd/glib2.0-2.33.12+really2.32.4/ ./gobject/gsignal.c:2459 signal child-added is invalid for instance '0x2e93110' self.ind.set_menu(self.menu) Displaying the log file, the only bad thing was: frontend not running but LOCKFILE detected! Strange! btsyncindicator should handle it. So then it says Starting frontend with default config file /root/.config/btsync/btsync-auto.conf Weirdly enough, when I edit that file, and restart btsync, it just changes back to the default file. Seeing as a 401 is an unauthorized, it may have something to do with that.

Everything is the most recent version. The ARM version and the Windows version were downloaded from the website last night. The debian version I got through apt-get. I force checked for updates.

I have this very weird issue. I have a netbook (with Debian), a raspberry pi (with ARM), and a desktop (with the windows client). I use the raspberry pi as a node, so that I can get an asynchronous connection between the netbook and desktop. When on the same network, my netbook is after to sync with my desktop AND my raspberry pi (my raspberry pi is NOT on the same network, but is able to locate it) When I'm on a different network (i.e. a school network with my netbook), I cannot locate my raspberry pi. I think this tells me that there is an issue with the school network blocking the data. This wasn't an issue in the past, but it is an issue after upgrading. How can I fix this issue? My raspberry pi has a domain name associated with it, and I do have ports forwarded for specific reasons (i.e. port 80 for my webserver, port 8888 for a front facing btsync admin page). I have tried setting a manual port for my raspberry pi's btsync configuration, and then adding a pre-defined host of my domainname.com:port of the port I specified.

Sorry I took so long to get back to this. I'll have to try what you suggested tomorrow and thanks for all of your work. I'm excited to get this to work. I had been using an alias in my bashrc to solve the problem.

Has anybody gotten this to work on Fedora 18/19? I ended up using a script very similar to this: https://gist.github.com/ricco386/5467477 And added it to chkconfig using this: http://unix.stackexchange.com/questions/20357/how-can-i-make-a-script-in-etc-init-d-start-at-boot At startup, it appears to work. The problem is that 50% of the time, sync never gets forced, so I need to find a way to restart the service. Doing: service btsync stop says that it occurs, but upon checking "top," the process still runs and the service is never killed. It seems to me that killproc never actually reads the pid file (yes I pointed it to the right directory) and never actually kills anything. Does anybody have a working script?