tuxpoldo

Before you ask: the btsync-common package for 1.2.91 will come tomorrow, since I will get tomorrow the custom build for AMD Geode that will be included there....

Before you ask: the btsync-common package for 1.2.91 will come tomorrow, since I will get tomorrow the custom build for AMD Geode that will be included there....

PLEASE PLEASE PLEASE provide also a binary for Geode - otherwise it is really a huge problem to release the package for Debian/Ubuntu/etc.

OK - I found two postings from RomanZ that document this behaviour... http://forum.bittorrent.com/topic/16836-support-for-untrusted-encrypted-node/?p=79067 and http://forum.bittorrent.com/topic/16836-support-for-untrusted-encrypted-node/?p=79125 In any case it is not a good idea to crash. And also the official applications crash if you enter an invalid secret.

As far as I could test it with the iOS application, it seems to work... The Linux GUI is now able to generate the QR-codes

Hi Aaron! Welcome! It's great news to hear that the development community now has a contact person in the development team!

Yes. I have a very similar configuration on my server. Apparently I can't see anything wrong in your configuration file. But you must make sure, that the firewall of the server does not block the required connections. Since you have no chance to see anything, I would suggest to make a backup copy of your configuration file, remove completely the shared_folders section and activate the web UI in order to get a better overview of what is happening (you shared folder will still exist, since btsync has stored it into its internal database). After you solved your problem, you can deactivate the web UI and write the shared_folders section back. Here an example of one of my config files: //!/usr/lib/btsync/btsync-daemon --nodaemon --config//// This btsync instance provides sync services for// all common files in the YeaSoft Server Grid{ "device_name" : "yeasoft-gate2 - Server Sync", "storage_path" : "/var/lib/btsync-serversync", "listening_port" : 22144, "check_for_updates" : false, "use_upnp" : false, "download_limit" : 0, "upload_limit" : 0, "lan_encrypt_data": true, "lan_use_tcp" : true, "rate_limit_local_peers" : false, "webui" : {// "listen" : "10.65.0.16:8889",// "login" : "Administrator",// "password" : "MyTestPassword" } , "shared_folders" : [ { "secret" : "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx", "dir" : "/mnt/data/tftproot/yeaboot", "use_relay_server" : false, "use_tracker" : false, "use_dht" : false, "search_lan" : true, "use_sync_trash" : true, "known_hosts" : [// "10.65.0.16:22144", "10.65.4.1:22144", "10.65.6.1:22144", "10.65.8.1:22144", "10.65.16.1:22144", "10.65.18.1:22144" ] } ]}As you can see, I made the same test: the web UI is disabled with comments... If you activate it, you have to comment out the shared folder section. In my special case, I disabled also all external helpers/relays and work only with predefined hosts.

During the development of the Linux GUI for BitTorrent Sync I found these features missing in the API: Create one-time-secrets for a folderEnable/disable logging on the flyPause/Resume btsync replication/operationGet current transfer activity status (See Issue #75)Get current activity history (See Issue #76)

I know ;-) Et voilà: Issue #77

No.... But redirecting the log files do not solve your problems at all, since btsync does not only read and write to the log file but also to other files in the storage_path. If you want your hard disks to spin down, you cannot have any server tasks running, that access the disks on a regular basis...

And here it is! btsync-gui (0.6-1) unstable; urgency=low * Folder status now takes in account and shows folder errors (Closes #72) * Show the device status on the "Devices" tab (Closes #73) -- Leo Moll <leo.moll@yeasoft.com> Sun, 02 Mar 2014 15:33:21 +0100

Hi Knireis, yes. I guess.... let's see... I guess it will come in the next version (I'm already working on it)

Yes... the GUI shows exactly what BitTorrent Sync is doing. When you add several huge folders, you can see, that they are processed sequentially.... good for the I/O. The GUI queries once per second BitTorrent Sync. I'm thinking about making the interval dependent upon the number of folders, since in systems with many many folders this would probably generate too much system load (at least as soon as I add also the "Devices" tab...)

I know ;-) The controls are there because they are there also on Windows/MacOSX, but probably it makes no sense to keep them in the preferences, since there is a possibility in the system settings to enable/disable autostart items. If I want to implement the functionality, I have to understand how to communicate with the startup/session manager (any clues?). In Debian/Gnome you can activate/deactivate autostart in the "Startup Applications Preferences" (gnome-session-properties)... BTW: Can you please tell on which distribution/desktop you are using btsync-gui (I need the info for the compatibility list)?

This is correct: btsync-gui autogenerates secret credentials in order to protect the session. Let me explain the reasons: Security: the Web UI can also be reached by other users working on the computer. This is a security hole, since another user of the computer can "steal" your files by configuring his btsync to sync a folder from your btsync (if he can access your btsync via webui, he is able to get the secrets). Consistence: The web UI offers the possibility to change the credentials. If you do that, the GUI will not be able any more to access btsync, since it does not know the credentials. Several users of btsync-user had run into problems deriving from that...In the current alpha version, the credentials autocreated by btsync-gui are static (if you know them, you can access via web UI - look at ~/.config/btsync/btsync-agent.conf), but this will change in future. I'm currently still thinking about how to support concurrent use of the GUI and the Web UI. The concurrency of two UIs can be a great source of problems. In fact neither the Windows nor the MacOSX version offer any Web UI.... Question to anybody out there: Do you see any reason to use the web UI when the application itself offers all possibilities of the web UI?

Maybe for some of you, this post may be interesting ;-)

BTSYNC DESKTOP GUI FOR ARCH, DEBIAN, UBUNTU AND OTHER DERIVED DISTRIBUTIONS If you are using Arch Linux, Ubuntu, Debian, Raspian or other derived distributions based on Debian and you are searching for an easy way to deploy BitTorrent Sync on your systems, this topic is definitively for you. Here you will find information about a family of easy to install packages that offer both a solution for the need of typical server/cloud operators as for interactive users. The desktop gui package is explicitly intended for desktop usage and provide a user experience similar to BitTorrent Sync on Windows or Mac OSX by still giving the user the possibility to customise his installation if he has special needs. This topic covers only the desktop user package. If you are searching for the server package, please look here. THE SOFTWARE AND THE PACKAGES ARE UNOFFICIAL AND NOT THE WORK OF BITTORRENT® INC. PLEASE DO NOT CONTACT THE BITTORRENT® INC. SUPPORT WITH QUESTIONS OR PROBLEMS RELATED TO THE USE OF THE PACKAGES. YOU WILL FIND COMPETENT HELP AND SUPPORT IN THIS FORUM THREAD INSTALLATION ON ARCH LINUX The Arch Linux Package in the AUR is maintained by Martin Wimpress (@flexiondotorg). The package is named btsync-gui and can be installed from the AUR using your favourite package manager. e.g.: if you are using yaourt: sudo yaourt -S btsync-guiWhen you have finished installing, you can skip the next section below and move directly to the USAGE NOTES. INSTALLATION ON DEBIAN, UBUNTU, LINUX MINT, RASPBIAN OR OTHER DEBIAN DERIVATES The most easy and fast way to install the repository is to paste that at a terminal prompt: sh -c "$(curl -fsSL http://debian.yeasoft.net/add-btsync-repository.sh)"The script explains what it will do and then pauses before it does it asking for your permission. If you encounter any problems or prefer to do it manually, please look here. Now update the package index and install btsync-gui by pasting that at a terminal prompt: `which sudo` apt-get update`which sudo` apt-get install btsync-guiOn some systems the AppIndicator library is not available or maybe you do not want to use it. In this case, you may want to install the GTK only version of the BitTorrent Sync GUI instead: `which sudo` apt-get update`which sudo` apt-get install btsync-gui-gtkPlease keep in mind, that this will work only on GTK based desktops. If you install it on other desktops like Unity, btsync-gui-gtk will start but you will see nothing and you have no control over the application! Install btsync-gui-gtk only if you know exactly what you are doing!!! If this happened, you can fix it by installing btsync-gui and rebooting your system. After the successful installation, you have to initially start BitTorrent Sync. You have various possibilities to do this: Log out and log in again. Since BitTorrent Sync GUI is registered in the autostart group, it will start as soon as you log in.Select BitTorrent Sync from the menu or the default application launcher of your desktop.USAGE NOTES The BitTorrent Sync GUI aims to be a clone of the original BitTorrent Sync application on Windows and Mac OSX and to replace on long term the legacy package btsync-user. The GUI provides two modes of operation: Standalone Mode: This is the default mode. When the GUI starts, an underlaying BitTorrent Sync agent is started too providing an overall experience similar to the GUI applications on Windows or Mac OSX.Client Mode: The GUI can be started from the command line with parameters specifying a connection to a remote BitTorrent Sync system. In this case, the GUI does not start a local BitTorrent Sync agent, but connects to an already running agent at a remote location. This will work only, if the remote agent has activated API access by specifying a valid API key in the configuration file.The behaviour of the GUI can be influenced by specifying various options on the command line. There is also a way to make some options persistent across restarts making it superfluous to specify the options each time you start the GUI. You can get detailed help about the command line options by invoking the man page: man btsync-guiHere you find an overview of the available options: usage: btsync-gui [-h] [--log {CRITICAL,ERROR,WARNING,INFO,DEBUG}] [--host HOST] [--port PORT] [--username USERNAME] [--password PASSWORD] [--bindui BINDUI] [--webui] [--savedefaults] [--cleardefaults]optional arguments: -h, --help show this help message and exit --log {CRITICAL,ERROR,WARNING,INFO,DEBUG} Sets the logging level. By default the logging level is WARNING --host HOST Hostname for the connection to BitTorrent Sync. If not specified, a local BitTorrent Sync agent will be launched. --port PORT Optional port number for the connection to BitTorrent Sync. If not specified, port 8888 is taken for a connection to a remote BitTorrent Sync agent or (8999 + uid) is taken when creating a locally lauched agent. This option can be made persistent for local agents with --savedefaults --username USERNAME Optional user name for connecting to a remote BitTorrent Sync agent or username to use when creating a locally launched agent. This option can be made persistent for local agents with --savedefaults --password PASSWORD Optional password for connecting to a remote BitTorrent Sync agent or username to use when creating a locally launched agent. This option can be made persistent for local agents with --savedefaults --bindui BINDUI Optional bind address for the Web UI of a locally created BitTorrent Sync agent. By default the agent binds to 127.0.0.1. If you want the Web UI of the agent to be reachable by other computers, specify one of the available IP addresses of this computer or "all" to bind to all available adapters. This option can be made persistent for local agents with --savedefaults --webui Include the Web UI in the menu. This option can be made persistent with --savedefaults --savedefaults If specified, the optionally supplied credentials, bind address and port will be stored as default in the application preferences and used when launching a local BitTorrent Sync agent. --cleardefaults If specified, all internally stored credentials, bind address and port information will be cleared from the application preferences.The usage of the command line options will be explained by some examples below. STANDALONE MODE By default there is no way to access the Web UI provided by the BitTorrent Sync agent, since the agent itself defines at each start random credentials to protect the system. If you still want to access the Web UI, you can activate an extended menu option by specifying --webui on the command line. You will then have an additional menu item, that invokes a browser and connects you to the Web UI. If you want to make this setting persistent, you can invoke the following command from the console: btsync-gui --webui --savedefaultsFrom now you will not need to specify it again at each start. Sometimes it may happen, that you want to access your running BitTorrent Sync agent from another computer via the Web UI or a btsync-gui in Client Mode. By default this is not possible, because of two reasons: The BitTorrent Sync agent binds the administration interface only to the loopback adapter making it possible to connect only from the same machine (This is a security feature).The BitTorrent Sync agent is started at every time with randomly generated credentials. Without knowing them, it is impossible to access the administration interface of the agent (This is also a security feature).For users that want to access their system from another computer, there is still a possibility to configure the GUI in a way that makes the agent accessible also from other computers. In order to do so, the following parameters must be changed: The BitTorrent Sync agent must bind its administrative interface to all adapters of the system or an adapter reachable from outside.The BitTorrent Sync agent must bind its administrative interface to a well-known port. By default the port is the sum of 8999 and the uid of the user.The credentials must be set to something known.The GUI can be launched in such a mode, by specifying the following parameters: btsync-gui --bindui 0.0.0.0 --port 10888 --username Leopoldo --password SuperSecretThis configures the BitTorrent Sync agent to bind on all interfaces on port 10888 and to be accessible with the user name "Leopoldo" and the password "SuperSecret". Also these settings can be made persistent by adding the option --savedefaults WARNING: as every comfort function, you pay the comfort by lowering the security. Remember: the product of comfort and security is a constant. You cannot increase both. CLIENT MODE In client mode, the GUI can be used to access a remotely running BitTorrent Sync agent. The only prerequisites are that the remote BitTorrent Sync agent is reachable from your computer, you know the credentials and the API access is enabled on the remote agent. You can also use the GUI to connect to another machine where a BitTorrent Sync GUI is running in standalone mode, if you have configured access possibilities like shown in the example above. The connection to a remote BitTorrent Sync agent is done by entering the following command: btsync-gui --host myserver.example.com --port 8888 --username Leopoldo --password SuperSecretIf you are able to access the Web UI of a remote BitTorrent Sync system, you should know everything you need to also launch successfully the GUI. Since the connection to remote systems is slower, you will notice the following limitations: The refresh rate is slower. It adapts dynamically to the overall performance.During the status refreshes, the GUI may be a bit unresponsive.There are no local file system checks, when you add a new folder. You must be sure, that you enter a valid path on the remote machine.Some features are disabled (Pause/resume, Enable/Disable Debug) since they are not feasible on remote systems.COMPATIBILITY The GUI packages are available for the same architectures as released by BitTorrent Inc.: i386 - Intel/AMD 32 Bitamd64 - Intel/AMD 64 Bitarmel - ARM EABIarmhf - ARM hard floatpowerpc - PowerPCThe GUI packages have been tested on the following distributions: Debian Wheezy with Gnome DesktopUbuntu Raring 13.04 with Unity DesktopLinux Mint Petra with Cinnamon DesktopOther users have reported successful installations on: Xubuntu Saucy 13.10 with OpenBox+Tint2Debian Jessie with KDEUbuntu Trusty 14.04 with Cinnamon, MATE and OpenBoxArch Linux with MATEThe GUI package has also been released for other Linux distributions: Arch Linux: Packages can be found in the AURWANTED Maintainers for other Linux distributions beeing able to write a suitable packaging for their favourite distribution: Centos/RHEL (rpm)Fedora (rpm)SLES(rpm)GentooNow it's up to you to test it and give me lots of feedback in order to extend this list. Any related feedback is highly appreciated. BUG REPORTS, CONTRIBUTION AND SOURCES If you want to contribute to the development of the packages or if you are curious how this all works, you may find the current sources, the deployment scripts and packaging on GitHub. If you want to contribute to the localisation by translating changed strings or by adding support for your favourite language, you may join the localisation team on POEditor.com. If you have experienced a reproducible issue that is related to the gui or the packaging and not to BitTorrent Sync itself you are strongly encouraged to open an issue on the project's GitHub Page. Issues related to the native functionality of BitTorrent Sync should instead be discussed by creating a new topic or partecipating to an already existing topic in the BitTorrent Sync Forum.

Ahem..... I must admit, that adding btsync-user to the lucid repository was a mistake... at least after Mark's btsyncindicator was added since it depends on python-requests, which is not included in lucid. I removed the btsync-user package both from Launchpad and from the YeaSoft repository in order to avoid such problems in future. Sorry - but Lucid is really near end of life, and I cannot spend too much time supporting things that will not work... I do not want to encourage people on using Lucid for Desktop systems. Headless servers are OK, and it is absolutely no problem installing the server version, but if you are using a desktop system, you should really stay up to date... But if you really really want to make it work... you should look if you find a python-request port in Launchpad for lucid.... maybe you are lucky. But in any case you have now to download the debs for btsync-user manually.... and install them with dpkg -i

It has changed that Lanchpad ceased support for Ubuntu 13.04 (Raring) and so it was not possible any more to update the package on Launchpad. For this reason, the package btsync-user is not available any more from Launchpad. The other packages are still there, since they got no updates in the last months. You have two different possibilities to solve the problem: Update the computer of your daughter to the supported Ubuntu 13.10 (Saucy) version and update the PPAs accordingly Remove the PPA and add instead the YeaSoft repository as described in the initial posting. There you will still get updates also for older Ubuntu versions.

Hi delegatevoid, I have no real problem - I wanted only to get a confirmation that my observation was correct. I'm developing a btsync gui for Linux and I had also to develop this part. It seems that my assumption was correct, since I was able to add shared folders to the mobile app by scanning the QR codes I generated...

I forwarded your report to the developer as Issue #44 See his page on GitHub

Sorry for the late answer. The last hours I was driving towards Italy to meet my parents. Now I'm there and I have network ;-) It makes no sense to edit btsync-auto.conf, since this file (as you noticed) is rewritten/auto-generated at each start. But there is a way to supply your own configuration file. You must create a file named btsync-user.conf in the same directory. If such a file is there, it is taken instead of btsync-auto.conf. So the best way is: Copy btsync-auto.conf to btsync-user.conf Edit btsync-user.conf to your needs restart btsyncPlease let me know it this solved your problem. BTW: this behaviour is documented in the initial posting

OK - that is REALLY interesting! The big issue is the strange implementation of configuration management in btsync. Btsync itself is planned as a gui application with its internal configuration store. Since the unix version is basically headless, you need the possibility to configure some things on start, and that's the reason they added configuration file support - but in a very strange way. From observations, I understood that btsync is working this way: load meaningful defaults into the configuration data structure if a config file is supplied, overwrite the defaults with the data in the config file look if storage_path exists, and if yes, load stored configuration data from the json file stored there if a config file is supplied, overwrite the config data AGAIN with the data in the config file This explains the behaviour of btsync in certain situations. There is a way you can break it: btsnyc-user creates by default a config file with no credentials set Now you open the web interface and you define credentials btsyncindicator stops working (excalmation point) since it does not know the credentials to use The credentials are stored into the internal json file On the next start, the credentials are loaded from the json file AND NOT OVERWRITTEN by the config file, since the config file does not define any credentials btsnycindicator still shows the exclamation pointpi3tr0? Does this sound familiar? Could this be the reason for YOUR problems? You can solve the issue by defining a user defined config file that specifies credentials. In that case, the credentials you may set in the web interface are overwritten on each start and the indicator will use the credentials supplied into the config file. BTW: the port thing is interesting... But maybe the same story. @pi3tr0: maybe you are a good candidate for testing the new btsync gui implementation I'm working on. Stay tuned since I will make available the first alpha release in the next days... (Update: It's available now - follow the previous link)

I definitively think so. As described previously, the fix addresses a problem described by other users and definitively not yours. Let's make some analysis:2014-02-25 08:27:56+01:00 btsync-starter: start ... 2014-02-25 08:27:57+01:00 start_frontend: starting frontend with default config file /home/pit/.config/btsync/btsync-auto.conf 2014-02-25 08:27:57+01:00 start_frontend: process is NOT running!!!! Something went wrong! 2014-02-25 08:27:57+01:00 start_frontend: end Uppps!!!! No btsyncindicator???? 2014-02-25 08:27:57+01:00 btsync-starter: no running statefile detected - forking runner... 2014-02-25 08:27:57+01:00 btsync-starter: end btsync itself has started.... 2014-02-25 08:27:57+01:00 agent_runner: begin 2014-02-25 08:27:57+01:00 agent_runner: starting up components... 2014-02-25 08:27:58+01:00 make_user_files: User specific files and directories created try to start btsyncindicator again.... 2014-02-25 08:27:58+01:00 start_frontend: begin 2014-02-25 08:27:58+01:00 start_frontend: process is running with pid 1964 2014-02-25 08:27:58+01:00 start_frontend: end sucess! 2014-02-25 08:27:58+01:00 start_agent: begin 2014-02-25 08:27:58+01:00 start_agent: starting agent with default config file /home/pit/.config/btsync/btsync-auto.conf 2014-02-25 08:27:59+01:00 start_agent: end So we learned: On your machine the indicator applet fails to start on the first try. This may be interesting in order to understand what's wrong. In any case the delayed start seems to succeed...The exclamation mark means that the indicator is not able to communicate with btsync. This can have several reasons. Often the indicator shows on the commandline messages, if is was started from there. Please try a btsync restart on the command line and post here the visible output in the terminal in case the exclamation mark shows again Unfortunately it is not simple to test applications like these on every available distribution and combination of desktions/applications... Since you are using a very special combination of components, you should take in consideration the possibility that there may be real incompatibilities between components like python-requests or libindicator with your toolchain. Mhhh. Can you please test if btsync itself is running? pgrep -u $(id -u) -x btsync-agentIf it outputs a number (the PID) it is running. If it outputs nothing, it is NOT running... I should add this test also to the logging facility...

OK - this means: the btsync engine itself is not running. Please delete any old logging file... rm -f ~/.btsync/btsync-user.logthen activate debug logging... btsync debug 0000and than restart the whole thing: btsync restartand then post the log in ~/.btsync/btsync-user.log here.