Syncthing running but gui not available

canton7 · June 29, 2015, 9:49am

You want to pass -no-restart to syncthing, not to su.

uok · June 29, 2015, 10:26am

not closed for me, I will check for running processes and report SIGABRT logs if it happens again (~ once per week)

Eddy2909 · June 29, 2015, 9:58pm

topic revive got syncthing running once - and yes I’m sure but gui isn’t answering with ERR_TIMED_OUT (as described above) and logs full of

http: TLS handshake error from 109.XXX.XXX.33:55002: read tcp 109.XXX.XXX.33:55002: i/o timeout

AudriusButkevicius · June 29, 2015, 10:05pm

It seems that you fail to get past the TLS handshake. Firewall, proxy issue? If you run linux, just try to do curl -v <address> and get the output.

Eddy2909 · June 29, 2015, 10:15pm

the problem appears since the last 11.10. update on linux Debian GNU/Linux 7.8 (wheezy)(server@datacenter). so I dont believe that they chenged their securitysettings… any other idea without curl? (dont have it installed ) what does curl -v do?

AudriusButkevicius · June 29, 2015, 10:15pm

Prints the handshake.

Eddy2909 · June 29, 2015, 10:17pm

curl -v address of server right? but do I got it right: I need to run curl on the problem-server or on another pc?

AudriusButkevicius · June 29, 2015, 10:19pm

On the UI you cannot access.

Eddy2909 · June 29, 2015, 10:34pm

syncusr@cloud:~$ curl -v *   Trying 85.XX.XX.204...
-bash: curl: command not found
syncusr@cloud:~$ * connected
-bash: SYNC: command not found
syncusr@cloud:~$ * Connected to cloud.mailify.de (85.XX.XX.204) port 8384 (#0)
-bash: syntax error near unexpected token `('
syncusr@cloud:~$ * successfully set certificate verify locations:
-bash: SYNC: command not found
syncusr@cloud:~$ *   CAfile: none
-bash: SYNC: command not found
syncusr@cloud:~$   CApath: /etc/ssl/certs
-bash: CApath:: command not found
syncusr@cloud:~$ * SSLv3, TLS handshake, Client hello (1):
-bash: syntax error near unexpected token `('
syncusr@cloud:~$ * SSLv3, TLS handshake, Server hello (2):
-bash: syntax error near unexpected token `('
syncusr@cloud:~$ * SSLv3, TLS handshake, CERT (11):
-bash: syntax error near unexpected token `('
syncusr@cloud:~$ * SSLv3, TLS alert, Server hello (2):
-bash: syntax error near unexpected token `('
syncusr@cloud:~$ * SSL certificate problem: unable to get local issuer certifica                                                                                        te
-bash: SYNC: command not found
syncusr@cloud:~$ * Closing connection #0
-bash: SYNC: command not found
syncusr@cloud:~$ curl: (60) SSL certificate problem: unable to get local issuer                                                                                         certificate
-bash: syntax error near unexpected token `60'
syncusr@cloud:~$ More details here: http://curl.haxx.se/docs/sslcerts.html
-bash: More: command not found

fyi: I already restarted syncthing… (needed to restart server to install curl) should this be done when hanging?

AudriusButkevicius · June 29, 2015, 10:50pm

Don’t know what you did, but the log is a mess.

Try -v -k options, in a separate console window.

Eddy2909 · June 29, 2015, 11:01pm

ok - to get sure: my server is running under https://cloud.mailify.de:8384 / 85.93.13.204 which one is the right call: curl -v https://cloud.mailify.de:8384 or just curl -v 85.93.13.204 ? sorry for such a mess of questions - I’m semibeginner at debian

AudriusButkevicius · June 29, 2015, 11:02pm

As I said, whichever address you access syncthing on. With -k -v options.

Eddy2909 · June 29, 2015, 11:07pm

finally

root@cloud:~# curl -v https://cloud.mailify.de:8384
* About to connect() to cloud.mailify.de port 8384 (#0)
*   Trying 85.93.13.204...
* connected
* Connected to cloud.mailify.de (85.93.13.204) port 8384 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS alert, Server hello (2):
* SSL certificate problem: unable to get local issuer certificate
* Closing connection #0
curl: (60) SSL certificate problem: unable to get local issuer certificate
More details here: http://curl.haxx.se/docs/sslcerts.html

curl performs SSL certificate verification by default, using a "bundle"
 of Certificate Authority (CA) public keys (CA certs). If the default
 bundle file isn't adequate, you can specify an alternate file
 using the --cacert option.
If this HTTPS server uses a certificate signed by a CA represented in
 the bundle, the certificate verification probably failed due to a
 problem with the certificate (it might be expired, or the name might
 not match the domain name in the URL).
If you'd like to turn off curl's verification of the certificate, use
 the -k (or --insecure) option.

curl -k gives: “Not Authorized”

AudriusButkevicius · June 30, 2015, 6:47am

Right, so it is accessible and it is listening. The problem must be with your browser/proxy/firewall which is outside of scope of syncthing.

You can add -k -u guiusername:guipassword which should get you the html output of the page.

Eddy2909 · June 30, 2015, 7:29am

remember:

at the moment syncthing stucks… these are my results:

result of pgrep:

output of netstat -tulpn | grep ‘8080|8384’

tcp6      0      0 :::8384       :::*     LISTEN    260/syncthing

output of curl -v https://cloud.mailify.de:8384:

root@cloud:~# curl -v https://cloud.mailify.de:8384
* About to connect() to cloud.mailify.de port 8384 (#0)
*   Trying 85.93.13.204...
* connected
* Connected to cloud.mailify.de (85.93.13.204) port 8384 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSL connection timeout
* Closing connection #0
curl: (28) SSL connection timeout

curl -k -u:

-bash: !0: event not found

Eddy2909 · June 30, 2015, 7:48am

and I found

2015/06/29 19:00:39 http: TLS handshake error from 109.90.119.33:34075: read tcp 109.90.119.33:34075: i/o timeout
2015/06/29 19:01:55 http: TLS handshake error from 194.126.249.10:41537: remote error: unknown certificate authority

Session terminated, terminating shell... ...terminated.

this was exactly at 1:00 am this night…

AudriusButkevicius · June 30, 2015, 9:39am

It does seem that there is something in between you and syncthing that’s causing the issue. Can you verify that the same thing happends when connecting via curl -v -k https://127.0.0.1:8384 from the same machine that runs syncthing.

Eddy2909 · June 30, 2015, 10:08am

root@cloud:~# curl -v -k https://127.0.0.1:8384
* About to connect() to 127.0.0.1 port 8384 (#0)
*   Trying 127.0.0.1...
* connected
* Connected to 127.0.0.1 (127.0.0.1) port 8384 (#0)
* successfully set certificate verify locations:
*   CAfile: none
  CApath: /etc/ssl/certs
* SSLv3, TLS handshake, Client hello (1):
* SSL connection timeout
* Closing connection #0
curl: (28) SSL connection timeout

while

root@cloud:~# pgrep syncthing
260

and

netstat -tulpn | grep '8080\|8384'
tcp6       0      0 :::8384           :::*        LISTEN      260/syncthing

bit wired

AudriusButkevicius · June 30, 2015, 10:19am

Can you get the SIGABRT dump? Via kill -6 as explained earlier.

Eddy2909 · June 30, 2015, 10:37am

hmm:

[7QCUL] 06:35:06 INFO: syncthing v0.11.11 (go1.4.2 linux-amd64 default) unknown-user@syncthing-builder 2015-06-28 19:10:57 UTC
[7QCUL] 06:35:06 INFO: My ID: 7QCULIP-XXXXXXXXXXXXXXXXXXXXXXXXXXX-GJC57AF
[7QCUL] 06:35:06 INFO: Database block cache capacity 8192 KiB
[7QCUL] 06:35:10 OK: Ready to synchronize mp3s (read-write)
[7QCUL] 06:35:10 OK: Ready to synchronize s.a (read-write)
[7QCUL] 06:35:10 OK: Ready to synchronize wedding (read-write)
[7QCUL] 06:35:11 OK: Ready to synchronize MatadorSync (read-write)
[7QCUL] 06:35:11 OK: Ready to synchronize SarahCloud (read-write)
[7QCUL] 06:35:11 INFO: Starting web GUI on https://0.0.0.0:8384/
[7QCUL] 06:35:11 INFO: Completed initial scan (rw) of folder s.a
[7QCUL] 06:35:11 INFO: Completed initial scan (rw) of folder wedding
[7QCUL] 06:35:11 INFO: Completed initial scan (rw) of folder MatadorSync
[7QCUL] 06:35:11 INFO: Completed initial scan (rw) of folder SarahCloud
[7QCUL] 06:35:12 INFO: Starting local discovery announcements
[7QCUL] 06:35:12 INFO: API listening on [::]:8384
[7QCUL] 06:35:12 INFO: Local discovery over IPv6 unavailable
[7QCUL] 06:35:12 INFO: Starting global discovery announcements
[7QCUL] 06:35:12 INFO: Device 2VSZP3U-XXXXXXXXXXXXXXXXXXXXXXXXXXX-AQ2QYQB is "JonasPC" at [dynamic]
[7QCUL] 06:35:12 INFO: Device 7QCULIP-XXXXXXXXXXXXXXXXXXXXXXXXXXX-GJC57AF is "BigCloud" at [dynamic]
[7QCUL] 06:35:12 INFO: Device A7EWFMD-XXXXXXXXXXXXXXXXXXXXXXXXXXX-YAZIOA7 is "MatadorPC" at [dynamic]
[7QCUL] 06:35:12 INFO: Device EXWD3FJ-XXXXXXXXXXXXXXXXXXXXXXXXXXX-QFWMIQK is "MatadorMobile" at [dynamic]
[7QCUL] 06:35:12 INFO: Device ICX6X4Q-XXXXXXXXXXXXXXXXXXXXXXXXXXX-XGQNTQI is "MatadorSmartie" at [dynamic]
[7QCUL] 06:35:12 INFO: Device LD6BG55-XXXXXXXXXXXXXXXXXXXXXXXXXXX-PYIZ3QO is "himbeerchen" at [dynamic]
[7QCUL] 06:35:12 INFO: Device XNQRTTG-XXXXXXXXXXXXXXXXXXXXXXXXXXX-6U4UPQA is "SarahMac" at [dynamic]
[7QCUL] 06:35:12 INFO: Starting usage reporting
[7QCUL] 06:35:13 INFO: Completed initial scan (rw) of folder mp3s

this is what I got didnt produced what you expected - right?