frater

Members
  • Posts

    41
  • Joined

  • Last visited

  • Days Won

    1

Posts posted by frater

  1. I just upgraded bittorrent sync on several machines and I think I like the new GUI of it.

    Just now I upgraded it as well on my Multimedia PC which is connected to a UHD TV.

    It's running a high resolution (3840 x 2160) and it turns out it doesn't scale well.

     

    In fact it's unusable as everything is so tiny (it is viewed from a distance)

    Some other programs have some glitches but not in this way where it's impossible to use it.

    Can this get fixed?

    post-35992-0-81138500-1412922830_thumb.p

  2. Not based on facts, but on gut feeling, I would do the first when btsync is mature (I guess that's next year) and do the latter now.

    I still have 1 combo where one side claims the folders are synced and the other side says it needs another gigabyte.

    Before running btsync these folders were synced using rsync because it was much faster.

    It's because 1 side only has 1 Mbit upload I'm not doing a complete resync.

    Cheers

  3. @frater,

    As for replacement - it is surprising. The "webui.zip" is not open for usage by BTSync. Why do you want to delete it? Why not just update the binary?

    The binary was already replaced and running. It looked strange.

    I noticed that webui.zip was quite old so I stopped the daemon and delete the file so it could get rebuilt.

    I wasn't able to delete it as a superuser. Finally I copied the complete .sync folder, removed webui.zip in that copy. Then renamed .sync to another name. Named the copied folder .sync and restarted the device.

    Now it's running fine.

    BTW.I had to repeat this whole procedure on a 2nd NAS (also a Qnap) that had exactly the same problem.

    All other Linux devices were easy to upgrade.

    Cheers

  4. I agree with all the posts in this thread. What really should get fixed is the sharing of the secrets in plain text.

    Using a reverse proxy is still a good idea. Software like nginx is getting many more reviews by the community and should therefore be more safe against hackers.

    Having another user (nginx) listen to the big bad world is giving you an extra level of security.

    Cheers

  5. I solved the "ssl problem" in 10 minutes on my system. It was already running nginx though.

    I never used apache as reverse proxy. In fact nowadays it's common practice to run nginx in front of apache to protect it from hackers.

    A reverse proxy has less code than a full-fledged webserver. The user that's running the nginx process doesn't have access to the files of your website. A potential hacker that's using buffer underpin techniques will only get access as an nginx user.

    Apache itself will not have a TCP-connection with the world. It will only receive clean http directives from the reverse proxy. I have experience with pound, nginx and varnish. I never used apache for this task.

    Why do you insist on using apache?

    It's like driving a bus to work. You'll probably get there, but not that practical.

    In this forum there's a how-to for nginx.

    Cheers

  6. I don't know exactly how it works, but I'm running Titanium Backup on my Android device.

    This Titanium can connect to Dropbox and then I only have to allow it and it's done.

    No credentials are given. These stay in Dropbox.

     

    There's probably some kind of API that makes this possible.

     

    I don't know any details, I'm speculating here.

    But would't if be fairly easy for other APPS to connect to btsync if it supports this?

  7. I am still able to add a new folder....

    I did set the the webui's root folder (I believe this is a new option).

     

     

    Edit:  I just reread your remark... No, I can't type it. Just browse..  But the option to set the directory_root might still be a solution to your problem. That's why I keep this message posted.

     

     

    grep -A10 webui /etc/btsync.conf | grep -B10 '}' | sed '/password/d'
      "webui" :  {    "directory_root" : "/var/btsync/",    "listen" : "127.0.0.1:57889",    "login" : "admin",  }
  8. If anyone's interested, here's my startup script you can put into /etc/init.d

    It will write a config-file for you..

    For security reasons the initial config will let the webif listen to 127.0.0.1

     

    You do need to create the user "btsync" with the command


    useradd btsync -s /bin/false
     
    # cat /etc/init.d/btsync
     
    #! /bin/sh export PATH="${PATH:+$PATH:}/usr/sbin:/sbin"echo $PATH | grep -q local || export PATH=/usr/local/sbin:/usr/local/bin:${PATH} set -e NAME=btsyncUSER=${NAME}GROUP=${USER}CONFIG=/etc/${NAME}.confDAEMON=/usr/local/sbin/$NAMEDESC="Bittorrent Sync Agent" test -x $DAEMON                  || exit 0grep -q "^${USER}"  /etc/passwd  || exit 0grep -q "^${GROUP}" /etc/group   || exit 0 DIR=/var/${NAME}PIDDIR=/var/run/${NAME}PID=${PIDDIR}/${NAME}.pidRETRY=15 if [ ! -f ${CONFIG} ] ; then  echo "There's no config-file, I will write one for you!" >&2   $DAEMON --dump-sample-config | sed "s/0.0.0.0:8888/127.0.0.1:57889/g"          >${CONFIG}  sed -i "s/\/\/ \"directory.*/    \"directory_root\" : \"\/var\/${NAME}\/\",/g"  ${CONFIG}  sed -i "s/storage_path.*/storage_path\" : \"\/var\/${NAME}\/.sync\",/g"         ${CONFIG}  sed -i 's/\/\/ \"pid/    \"pid/g'                                               ${CONFIG}   chown ${USER}:${GROUP} ${CONFIG}  chmod o-rw ${CONFIG}fi [ -d "$PIDDIR" ]    || mkdir "$PIDDIR"[ -d "$DIR/.sync" ] || mkdir -p "$DIR/.sync" chown -R ${USER}:${GROUP} "$PIDDIR"chown -R ${USER}:${GROUP} "$DIR" case "$1" in  start)    echo "Starting $DESC" "$NAME"    sudo -u ${USER} ${DAEMON} --config ${CONFIG}        ;;   stop)    if [ -f ${PID} ] ; then      kill `cat ${PID}`    else      killall $NAME    fi        ;;   restart|force-reload)    if [ -f ${PID} ] ; then      PROGID=`egrep '^[0-9]+$' ${PID}`      if [ ! -z "${PROGID}" ] ; then        n=1        while ps ${PROGID} 2>&1 >/dev/null ; do          echo -n "."          kill ${PROGID}          sleep 2          let n+=1          if [ $(($n % 10)) -eq 0 ] ; then            kill -9 ${PROGID} 2>&1 >/dev/null            rm -f "${PID}" 2>/dev/null          fi        done        sudo -u ${USER} ${DAEMON} --config ${CONFIG}      fi    else      echo "There's no ${PID}, sorry" >&2      exit 1    fi        ;;  *)    echo "Usage: /etc/init.d/$NAME {start|stop|restart|force-reload}" >&2        exit 1        ;;esac exit 0
  9. I just installed the new btsync 1.3.105 on a 64-bit system and on a 32-bit system.

    Only the 64-bit version has the improved interface.

    Why?

     

    PS...   I also noticed that the size is given in bytes Even if it is more a gigabyte. (on the "old" webinterface). I don't think it was that way in previous versions....

     

    PS PS...   I'm somehow unable to delete .sync/webui.zip on that NAS even though I am superuser... I assume this is also the reason why the webif isn't replaced. It's too late now to further troubleshoot.

  10. Modern Plesk servers already run nginx in front of Apache and I just investigated how I could add this to the existing setup without breaking their management shell. I didn't even have to stop any services.

     

    They have everything well organized in separate config folders that are included and the only thing I had to do was add a file in /etc/nginx/conf.d/

    I didn't even have to write the config file from scratch.

     

    First I modified /etc/btsync.conf so it will listen to 127.0.0.1 and not on all interfaces anymore.

    sed -i 's/0.0.0.0:57889/127.0.0.1:57889/g' /etc/btsync.confkillall -HUP btsyncnetstat -lntp | grep btsync

    You should see btsync only on 127.0.0.1 on port 57889

     

    Don't forget to modify your firewall and stop it from opening port 57889

     

    I copied the file /etc/plesk.conf.d/webmail.conf to /etc/nginx/conf.d/bittorrentsync.conf

    cp -p /etc/nginx/plesk.conf.d/webmail.conf /etc/nginx/conf.d/bittorrentsync.confsed -i 's/proxy_pass.*/proxy_pass http://127.0.0.1:57889;/g' /etc/nginx/conf.d/bittorrentsync.conf

    Then modify the file /etc/nginx/conf.d/bittorrentsync.conf by removing the complete section where it is listening on port 80 with http.

     

    Change the name to the FQDN you would like to use and maybe you also have a proper certificate.

    Then give:

    killall -HUP nginx

    That's it

     

    For those that don't have Plesk but still would like to see the result.

    This is the file to add:

     

     

    # cat /etc/nginx/conf.d/bittorrentsync.conf
    server {    listen 80.169.140.53:443 ssl;    server_name my_fqdn.nl;     ssl_certificate             /root/.ssh/mycert.nl.pem;    ssl_certificate_key         /root/.ssh/mycert.nl-key.pem;    ssl_session_timeout         5m;     ssl_protocols               SSLv2 SSLv3 TLSv1;    ssl_ciphers                 HIGH:!aNULL:!MD5;    ssl_prefer_server_ciphers   on;     client_max_body_size 128m;     location / {        proxy_pass http://127.0.0.1:57889;        proxy_set_header Host $host;        proxy_set_header X-Real-IP $remote_addr;        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;    }}
  11. Do read-only nodes send data to other nodes? If not, why?

    At first glance one would assume no, because these files can be deleted or changed.

    In normal use all the read-only nodes have the same structure and content. To speed up distribution they could send all the data that it knows is in sync.

    I hope the answer "yes".

    Does the 4 MB chunks apply here as well or do these files have to be completely in sync?

    Cheers

  12. NeoXid created an alternate tracker which could be used instead of the servers of bittorrent.

    I would like to use btsync to backup medical data, but the fact that currently the secret keys are handled by a foreign server I can't do this.

    The current clients have to be either patched or misled by a firewall or dns.

    It would be nice if the current clients get native support for alternate trackers. Preferably at a share level.

    Does a url already exist for bittorrent sync keys?

    It would be nice if the alternate tracker could be included...

    Cheers