crest
-
Posts
10 -
Joined
-
Last visited
Posts posted by crest
-
-
Hi,
I'm using 1.4.83 on FreeBSD 9.2 and 9.3 (NAS4Free). If I use "directory_root" in a config file it works in principle BUT nevertheless it is possible to define a path starting from "/" e.g.:
directory_root = /mnt/DATA -> if I want to add a new folder then it correctly displays "/mnt/DATA" but it is possible to overrule this if you enter a path in the inputbox! IMHO the implementation should remove leading slashes "/" so that it would be only possible to create a new folder starting from the directory_root = /mnt/DATA.
Regards
crest
-
Hi,
https now works on FreeBSD => http://forum.bittorrent.com/topic/31328-sync-1472-force-https-not-working-no-access-to-webui/, great work!!!
Regards
crest
-
If you don't use the link sharing feature (and only share keys directly), you can continue to change the device name.
Once you generate/share a link, the device name becomes fixed.
It's possible to show a user defined name for other clients if you use "device_name" in sync.conf (see also => http://forums.nas4free.org/viewtopic.php?f=71&t=5704&p=42777#p42775). Do you see any problems to do this?
Regards
crest
-
create a config file and write a new password in this file, this should overrule the current password (you must restart btsync with the option --config YourSyncFile.conf.
Works at least up to version 1.3xxx.
Regards
crest
-
Wirh the actual version 1.4.83 https is working !!!
Great work, thank you guys!
Regards
crest
-
Hi all!
I'm on FreeBSD 9.2 / 9.3 (NAS4Free) and tried to get https access to the WebUI running. Configured a sync.conf file accordingly but until now - no success. When I try "https://MyLocalIP:8888/gui/" the browser (IE, Firefox, Chrome) always shows loading but didn't finish to the WebUI. With http everthing is working.
My sync.conf:
{"storage_path": "/Path/To/btsync/.sync/","pid_file": "/Path/To/btsync/.sync/sync.pid","webui": {"listen": "MyLocalIP:8888","force_https" : true,"ssl_certificate" : "/Path/To/btsync/keys/cert.pem","ssl_private_key" : "/Path/To/btsync/keys/private.key"},"disk_low_priority": true,"folder_rescan_interval": 600,"lan_encrypt_data": true,"lan_use_tcp": false,"max_file_size_diff_for_patching": 1000,"max_file_size_for_versioning": 1000,"rate_limit_local_peers": false,"recv_buf_size": 5,"send_buf_size": 5,"sync_max_time_diff": 600,"sync_trash_ttl": 30}There are no errors in the log and sync is running - I see it is connected to another peer.
Any ideas ???
-
Bittorrent Sync is running perfectly well on NAS4Free (FreeBSD 9.1 and 9.2). I wrote an extension for it > http://forums.nas4free.org/viewtopic.php?f=71&t=5704&sid=bff403d20f48afb006a34ce5d31b5b85#p30737
For installation, configuration, maintenance, scheduling and log viewing.
A great advance would be https for the WebUI but beside of this it's an amazing piece of software !!!
Regard
crest
-
lol! Patience... it's coming!
Great, can't await this. Can we suppose that the Linux / FreeBSD versions will auto update or is this only for Windows possible?
-
First of all thank you for this GREAT app!!
I use BTSync mainly as a backup solution with Windows and Android clients which are backuped to my NAS (NAS4FREE) but also to sync folders between two NAS4FREE (FreeBSD based) servers. Since this is a wishlist I would really appreciate to see the following features implemented in BTS:
- https access for the builtin webserver!!! ++1
- advanced settings implemented in the webGUI (like in the windows client) because the use of a config file (can) interferes sometimes with the options which are configurable via the webGUI -> webGUI overrides the config-file settings ...
- hierarchical severity levels for the log file (like INFO, WARNING, ERROR, DEBUG, ...)
- consistent (=the same) information in logs for all kind of clients (Windows, FreeBSD, ...)
- if a sync folder will be removed from syncing at the client/webGUI the hidden files created by BTS should be removed as well by BTS
Thanks in advance!
Latest Desktop Build 1.4.83
in Sync General Discussion
Posted
Understood, BUT wouldn't it a good way together with "dir_whitelist" to have some system security ... and not difficult to implement I think ...
Regards
crest