XigmaNAS

liver wrote:

crest wrote: Do you mean the name you can see in BitTorrent Sync? If yes, just open the WebUI of BitTorrent Sync (standard http://YourIPAddress:8888) open OPTIONS | PREFERENCES and there you can edit the device name.

In NAS4FREE version it impossible. Readonly preference.

NAS preference

liver wrote:This property is now a part of x.509 certificate. It can be set only once on any platform. If you want to change it - you need to reinstall with settings cleanup.

    "device_name": "YourDeviceName",

su root -c '/Path/To/Your/Extensions/btsync/btsync --config /Path/To/Your/Extensions/btsync/sync.conf' 

chrisf4lc0n wrote:#server.modules += ( "mod_rewrite")
# Workaround to have a working reverse-proxy that matches an URL does URL rewriting in Ligghtpd.
#
# Ligtthpd 1.4.28 cannot perform both matching and URL rewriting at the same time.
# Therefore we need to define 2 proxies, one does the matching and bounce the request
# to the other one, in charge of rewriting the URL before proxying the request to the target server.
#
...

That is what I have found, tried to implement it and started getting the 500 error, which is something, as before it just kept looping itself!
Will work on it...

"force_https" : true,
"ssl_certificate" : "/Path/To/btsync/keys/cert.pem",
"ssl_private_key" : "/Path/To/btsync/keys/private.key"

{
    "device_name": "YourDeviceName",
    "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
}

chrisf4lc0n wrote:I did promise to do that on a reverse Apache Proxy from my Pi, but have not had time to wrap my head around it...
This way it will be much easier anyway... Currently at work, but will test it before going home Thanks a ton crest! I would love to have your knowledge mate!

chrisf4lc0n wrote: ...
EDIT: You can also use *.pem and *.key files from under the System>General tabs...
EDIT2: Tested it... and it seems to be working, but for the external/internet access you will need to change the line "listen" to:
...
are not even needed, unless you want your own certificate there.
If you do not specify them the BTSync will use the generic BTSync certs.
...

Vasily1 wrote: In current version (v0.6.1) of THIS Extension not working selection of virtual interfaces (vlan, lagg, etc.)
To correct this issue need change file "btsync.php" ("path_to_extensions_folder/btsync/ext/" or "/usr/local/www/ext/btsync/" if you don't need to save it after restart or if you need see results immediately):
search raw 278 with:

Andy22 wrote: Since BTsync 1.4.82+ the default Btsync client UI does not properly support (does not save) a specific listening port, which results in problematic sync behaviour for my NAS machine. So can you add a option, where we can specify the listening port via config file?

Andy22 wrote: A general text-field that simply adds the entered options to the end of the btsync config file would also solve such problems and would even allow to add future options without the need to update the extension. The Webserver service has something like this called "Auxiliary parameters" and this helps adds whatever option we may need in a more general way.

cd /mnt/DATA/extensions && fetch https://raw.github.com/crestAT/nas4free-bittorrent-sync/master/bts_install.php && chmod 770 bts_install.php && echo "fetch OK"

/mnt/DATA/extensions/bts_install.php

crest wrote: This is not neccessary because you can directly edit the sync.conf file and add every parameter directly via the N4F WebGUI (in ADVANCED | File editor). Just copy the full path and name of the conf file - which you can see at the bottom of the configuration page of the BTS extension under NOTE - into the file path of the editor, make your changes and - voilá .
Since the sync.conf file is stored in a persistant place your changes stay permanent.

• If you hit "start and save" via the Btsync service pane once, all your settings are gone and will be overridden. (Is this changed in the new version?)
  You need to manually start the service after each change via command-line and use the correct service user. (Is this changed in the new version?)
  Its way more complex and needs extra maintenance to edit the config file and after several months remember that you actually did this, compared to actually see what special/extra option you added on top of the supported from the UI.
  Its inconsistent to have some settings "generated" via the webinterface and than adding only a few special via config file manually.
  You need to actually understand the structure and syntax of the config file, compared to let the php code do most of the work and just adding 1-2 lines in a separate field via the UI.
  Its easier to write a example or guide, since you only need to explain the extra config options you added, which are clearly visible in the UI.

Andy22 wrote: ...
Here are some problems why editing config files manually is not a good solution for a mainly webbased managed NAS system.
...
If you hit "start and save" via the Btsync service pane once, all your settings are gone and will be overridden. (Is this changed in the new version?)/i]

Yes, this is changed, all manual editings in sync.conf are preserved (see in What's new in this version: )

Andy22 wrote:
You need to manually start the service after each change via command-line and use the correct service user. (Is this changed in the new version?)/i]

Andy22 wrote:
Its way more complex and needs extra maintenance to edit the config file and after several months remember that you actually did this, compared to actually see what special/extra option you added on top of the supported from the UI.
Its inconsistent to have some settings "generated" via the webinterface and than adding only a few special via config file manually.
You need to actually understand the structure and syntax of the config file, compared to let the php code do most of the work and just adding 1-2 lines in a separate field via the UI.

Andy22 wrote:
You need to actually understand the structure and syntax of the config file, compared to let the php code do most of the work and just adding 1-2 lines in a separate field via the UI.

Andy22 wrote:
Its easier to write a example or guide, since you only need to explain the extra config options you added, which are clearly visible in the UI.

..only parameter which isn't implemented (nor by my extension neither by the BTS WebUI) is "shared_folders". I don't think that many users need this because if you use this parameter the BTS WebUI will be disabled.

Andy22 wrote: Thx for the answers, like noted i simply like the flexibility and ease of use of such extra option field, compared to editing config files 3-4 times a year. I understand the extra work needed now and just mentioned this idea, since i used it in the webserver service and hoped it would be relatively easy to add.

Andy22 wrote: So the main problems are addressed in your new version, so i'm happy you had time to update the extension!

Andy22 wrote: ...
my Nas is just the always on Btsync readonly seed and the webinterface is a security risk.
...

crest wrote:IMHO the extension should cover most features for let's say 90% of the use cases.

Andy22 wrote: Just testing the new version and here are some problems i have.

I had to manually create the "btsync/.sync" folder, since it was not created.

Andy22 wrote: I cant get the extension to download and install any btsync version or check the extension server version?

Andy22 wrote: "Unable to retrieve version from server!" for the extension and "n/a - push 'fetch' button to check for new version" via "fetch" option. It lists 1.4.72 installed, but wont fetch any new version?

Andy22 wrote: I manually grabbed and put the "btsync" bin in the extension/btsync folder and now it seems to start, but despite it being the 1.4.92 version, the UI still lists 1.4.72, so i assume the bt version is stored somewhere else and not grabbed from the btsync bin file?
...
PS: I use the default "http://download-new.utorrent.com/endpoi ... ack/stable" url, but nothing gets downloaded or installed?
PS2: lol, BTSync 1.4.93 came out minutes ago and now should have the random port fixed, but still need to manually install and download the bin, since the Ui wont fetch+install?

MikeMac wrote: Had installed 0.6.3.6, upgraded via GUI to 0.6.3.6a, upgraded BTS to btsync-1.4.93 - works fine.

MikeMac wrote: Switched to Russian - looks like there is need for additions to language file. Please, provide me with semi-translated file then you will finalize messages and texts

crest wrote: I assume you didn't change the extensions path properly to your existing extensions directory as mentioned in my post. Perhaps you tried to test the new version in another directory while you are already using an older version in another extension directory ... ?

Andy22 wrote:I only wish there would also be a "Duplicati 2.0" extension for nas4free :p

MikeMac wrote:

Andy22 wrote:I only wish there would also be a "Duplicati 2.0" extension for nas4free :p

I am afraid, it is not possible as far as there is no FreeBSD support. And even WebDAV support on FreeBSD IMHO is far from perfect (fusefs-wdfs)

Andy22 wrote:I made a WebDav server tutorial over here

I also run "Duplicati 2.0" in a Jail just fine on my nas4free server, which backups my WebDAV and BTSync data to amazon S3

liver wrote:change "Device name" in extension settings not working.

Andy22 wrote: PS: Did a clean reinstall and now everything seems fine, thx again for the updated extension, which helps a lot managing my BTserver node. I only wish there would also be a "Duplicati 2.0" extension for nas4free :p

crest wrote:

liver wrote:change "Device name" in extension settings not working.

Did you check if the name appears to other clients (under specific circumstances it does not appear in the BTS WebUI, which is a restriction from BTSync application itself as you know - see also this post viewtopic.php?f=71&t=5704&start=50#p42775.
Which version of BTSync application do you use now?