Syncthing and BTSync problems


#1

Installed both Syncthing and BTSync but get errors for both. For BTSync it’s a HSTS error (I used the lets encrypt tutorial fro https) and syntching refuses to run ( The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. ) Countless re-installs didn’t do anything


#2

Turn off the tunneling traffic through CloudFlare.

I can’t confirm the same behavior. I installed this for a user this morning and set it up on Debian 8 without issue. What OS are your using? Have you tried to install with box install syncthing … additionally, you can remove it with box remove syncthing. Please use box as root user for a more reliable pass on actions.


#3

I don’t think I have anything related to cloudflare on my domain or server ( I have hetzner ).

Ubuntu 16.04. Did box install and it’s still showing as red for me meaning it’s not starting.


#4

Who are you using to host your DNS for the domain you installed the LE certificate on?

What is the output of systemctl status [email protected]?


#5

https://freedns.afraid.org/ is the dns . Namecheap is the domain name.

Ubuntu-1604-xenial-64-minimal:~# systemctl status [email protected]
[email protected] - Syncthing - Open Source Continuous File Synchroniza
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor prese
Active: inactive (dead) (Result: exit-code) since Sun 2017-01-29 23:02:12 CET
Docs: man:syncthing(1)
Process: 11289 ExecStart=/usr/bin/syncthing -no-browser -no-restart -logflags=
Main PID: 11289 (code=exited, status=1/FAILURE)

Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: Stopped Syncthing - Op
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: Failed to start Syncth
lines 1-13/13 (END)…skipping…
[email protected] - Syncthing - Open Source Continuous File Synchronization for nergal
Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Sun 2017-01-29 23:02:12 CET; 1min 15s ago
Docs: man:syncthing(1)
Process: 11289 ExecStart=/usr/bin/syncthing -no-browser -no-restart -logflags=0 (code=exited, status=1/FAILURE)
Main PID: 11289 (code=exited, status=1/FAILURE)

Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]: Unit entered failed state.
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]: Failed with result ‘exit-code’.
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]: Service hold-off time over, scheduling restart.
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: Stopped Syncthing - Open Source Continuous File Synchronization for nerga
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]: Start request repeated too quickly.
Jan 29 23:02:12 Ubuntu-1604-xenial-64-minimal systemd[1]: Failed to start Syncthing - Open Source Continuous File Synchronization f


#6

Does it produce any error in particular when you attempt to restart the service?

systemctl stop [email protected]
systemctl start [email protected]

You could just try restart instead, however, I want to see if stopping and/or starting produces an error.


#7

No error whatsoever. With stop, start and restart.


#8

Installed it without quickbox and pretty much got the same errror

[email protected] - Syncthing - Open Source Continuous File Synchronization for grim
Loaded: loaded (/lib/systemd/system/[email protected]; enabled; vendor preset: enabled)
Active: inactive (dead) (Result: exit-code) since Mon 2017-01-30 02:42:57 CET; 8s ago
Docs: man:syncthing(1)
Process: 8681 ExecStart=/usr/bin/syncthing -no-browser -no-restart -logflags=0 (code=exited, status=217/USER)
Main PID: 8681 (code=exited, status=217/USER)

Jan 30 02:42:57 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]: Unit entered failed state.
Jan 30 02:42:57 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]: Failed with result ‘exit-code’.
Jan 30 02:42:57 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]: Service hold-off time over, scheduling restart.
Jan 30 02:42:57 Ubuntu-1604-xenial-64-minimal systemd[1]: Stopped Syncthing - Open Source Continuous File Synchronization for grim.
Jan 30 02:42:57 Ubuntu-1604-xenial-64-minimal systemd[1]: [email protected]: Start request repeated too quickly.
Jan 30 02:42:57 Ubuntu-1604-xenial-64-minimal systemd[1]: Failed to start Syncthing - Open Source Continuous File Synchronization for grim.


#9

I got btsync working by just using a different browser. The syncthing error is still there.


#10

re: syncthing

I think I have the same problem as you and I think it’s a permissions / service issue.

I can actually get it started, despite the fact the installation from the dash or from (ssh) root fails with “cp: cannot stat ‘/root/QuickBox/setup/templates/sysd/syncthing.template’: No such file or directory”

If you ssh in, switch over to root and start syncthing (just type ‘syncthing’ from the command line) it should start the service. With the SSH session running, you should be able to then browse to the Quickbox dash and start the syncthing gui with no problems. It’s obviously not a fix, but it seems to highlight where the issue might lay.

The syncthing service refuses to start with my normal user. It only accepts root. Would love a solution to this problem. I’m just getting in to linux and I’m still not up on troubleshooting services

ps: should add, am also on ubuntu 16.04 running v2.94 of QB