Remote devices showing disconnected

SumiSujith · February 8, 2018, 4:15am

I connected 8 devices.7 among them show Up to Date and 1 show disconnected.(All folders are Up to Date) Then i removed all devices and again i added 8 devices. At that time 6 devices show Up to Date and 2 devices shows the same issue as mentioned above (Last seen -never). I have files in folders. only 6 machines got that files.what can i do to connect all devices??As it is important to sync folders in all remote devices .

brunod · February 8, 2018, 6:09am

Well, strange. Maybe I was not clear because I think we maybe say the same. I run a few devices in my LAN and what I describe is just what I 've seen. I start a transfer from a LAN Master, it’s quite quickly synced to another LAN pc, then this one is connected to a WAN device but the same WAN device appears disconnected from the LAN Master. And transfer runs from the second LAN device. So from the Master device point of vue, the WAN device seems not connected, but this WAN device is still downloading from LAN device 2. So even if it’s disconnected from the Master, the sync process is still working from other devices.

imsodin · February 8, 2018, 8:02am

@SumiSujith As Audrius said, your earlier logs show that those are likely kcp related failures. This will be “fixed” (kcp removed) soon, in the mean time replace default as listen address in the web UI connection settings with tcp://:22000, dynamic+https://relays.syncthing.net/endpoint.

@brunod That means there is a real connection problem between LAN pc and WAN device, while connection is fine between LAN device 2 and WAN device. You don’t notice any immediate problems as you still get in sync on LAN pc via LAN device 2, but it’s definitely not “normal” and you should check addresses and firewalls/port forwardings/whatever applies to your situation between LAN pc and WAN device.

brunod · February 8, 2018, 9:40am

Thanks @imsodin Simon, But I think it’s normal. Because if no other LAN device but the Master is on, the transfer goes fine with the WAN device (tested). According what you say, now I think this behaviour might be related to the fact syncthing runs on a nas and the traffic for it is set on low priority by the router, which is not the case of the other LAN devices. Thanks anyway for your explanation And thanks for your good job !

SumiSujith · February 9, 2018, 6:42am

I change the listen address from default to tcp://:22000, dynamic+https://relays.syncthing.net/endpoint of both remote device and own device. After that add the remote device.But still the remote device didn’t get my folders and it shows disconnected.No pop up come in the remote device.

The remote device image is given below

My device id is:-3QLXFOG-BNZQZYG-7ASFXAK-RMYNJCD-RPEYIGV-UG5VL2E-FU62YNT-PO3AXAI and the device id of remote device is MNGB4X2-GPTU2RR-GQCH3I6-LSGDPLA-X5O36F7-PX74HEA-2LFUJMT-XX4VNAA

The log of my device is given below

2018-02-09 06:05:01 syncthing v0.14.44 "Dysprosium Dragonfly" (go1.9.2 linux-amd64) teamcity@build.syncthing.net 2018-01-19 06:21:05 UTC
2018-02-09 06:05:01 My ID: 3QLXFOG-BNZQZYG-7ASFXAK-RMYNJCD-RPEYIGV-UG5VL2E-FU62YNT-PO3AXAI
2018-02-09 06:05:02 Single thread SHA256 performance is 81 MB/s using minio/sha256-simd (80 MB/s using crypto/sha256).
2018-02-09 06:05:03 Hashing performance with weak hash is 69.27 MB/s
2018-02-09 06:05:04 Hashing performance without weak hash is 80.37 MB/s
2018-02-09 06:05:04 Weak hash enabled, as it has an acceptable performance impact.
2018-02-09 06:05:04 Ready to synchronize "branch-oooooooooooo-vertical" (branch-oooooooooooo-vertical) (readonly)
2018-02-09 06:05:04 Ready to synchronize "branch-prv-br-vertical" (branch-prv-br-vertical) (readonly)
2018-02-09 06:05:04 Ready to synchronize "zone-prv1-vertical" (zone-prv1-vertical) (readonly)
2018-02-09 06:05:04 Ready to synchronize "CHECK" (mtyrx-zjggx) (readwrite)
2018-02-09 06:05:04 ...
2018-02-09 06:21:00 Connection from QXIG2MO-V7AROCU-TZ3OEYW-6DVEBHA-AYV4FKC-RVYEBNK-ZPL6QM6-5FW7EQX at 202.83.55.151:52242 (tcp-server) rejected: unknown device
2018-02-09 06:29:24 Failed to exchange Hello messages with TAJFFYN-IANXWM5-6CEST6A-UVTUDJ5-FIUVNEW-4Y2JGBF-V5LO5GK-JG7PFAG at 198.211.115.107:22000-202.83.55.151:58492/tcp-server: read tcp 198.211.115.107:22000->202.83.55.151:58492: i/o timeout
2018-02-09 06:29:24 Connection from TAJFFYN-IANXWM5-6CEST6A-UVTUDJ5-FIUVNEW-4Y2JGBF-V5LO5GK-JG7PFAG at 202.83.55.151:22000 (tcp-client) rejected: unknown device
2018-02-09 06:35:52 Connection from QXIG2MO-V7AROCU-TZ3OEYW-6DVEBHA-AYV4FKC-RVYEBNK-ZPL6QM6-5FW7EQX at 202.83.55.151:52366 (tcp-server) rejected: unknown device
2018-02-09 06:35:57 Enabled debug data for "connections"
2018-02-09 06:35:57 Listen (BEP/tcp): connect from 202.83.55.151:58692
2018-02-09 06:35:58 Listen (BEP/tcp): connect from 202.83.55.151:52367
2018-02-09 06:35:59 dialing MNGB4X2-GPTU2RR-GQCH3I6-LSGDPLA-X5O36F7-PX74HEA-2LFUJMT-XX4VNAA tcp://202.83.55.151:42597 error: dial tcp 202.83.55.151:42597: i/o timeout
2018-02-09 06:35:59 dialing MNGB4X2-GPTU2RR-GQCH3I6-LSGDPLA-X5O36F7-PX74HEA-2LFUJMT-XX4VNAA tcp://202.83.55.151:53702 error: dial tcp 202.83.55.151:53702: i/o timeout
2018-02-09 06:35:59 dialing MNGB4X2-GPTU2RR-GQCH3I6-LSGDPLA-X5O36F7-PX74HEA-2LFUJMT-XX4VNAA tcp://202.83.55.151:65462 error: dial tcp 202.83.55.151:65462: i/o timeout
2018-02-09 06:35:59 discarding 0 connections while connecting to MNGB4X2-GPTU2RR-GQCH3I6-LSGDPLA-X5O36F7-PX74HEA-2LFUJMT-XX4VNAA 10
2018-02-09 06:35:59 Connection from TAJFFYN-IANXWM5-6CEST6A-UVTUDJ5-FIUVNEW-4Y2JGBF-V5LO5GK-JG7PFAG at 202.83.55.151:58692 (tcp-server) rejected: unknown device
2018-02-09 06:36:00 Connection from QXIG2MO-V7AROCU-TZ3OEYW-6DVEBHA-AYV4FKC-RVYEBNK-ZPL6QM6-5FW7EQX at 202.83.55.151:52367 (tcp-server) rejected: unknown device
2018-02-09 06:36:05 Listen (BEP/tcp): connect from 202.83.55.151:58693

The log of remote device is given below

2018-02-09 11:34:49 syncthing v0.14.44 "Dysprosium Dragonfly" (go1.9.2 linux-amd64) teamcity@build.syncthing.net 2018-01-19 06:21:05 UTC
2018-02-09 11:34:49 My ID: MNGB4X2-GPTU2RR-GQCH3I6-LSGDPLA-X5O36F7-PX74HEA-2LFUJMT-XX4VNAA
2018-02-09 11:34:50 Single thread SHA256 performance is 438 MB/s using minio/sha256-simd (372 MB/s using crypto/sha256).
2018-02-09 11:34:50 Hashing performance with weak hash is 348.77 MB/s
2018-02-09 11:34:51 Hashing performance without weak hash is 421.92 MB/s
2018-02-09 11:34:51 Weak hash enabled, as it has an acceptable performance impact.
2018-02-09 11:34:51 Ready to synchronize "Default Folder" (default) (readwrite)
2018-02-09 11:34:51 Send rate is unlimited, receive rate is unlimited
2018-02-09 11:34:51 Rate limits do not apply to LAN connections
2018-02-09 11:34:51 Using discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
2018-02-09 11:34:51 ...
2018-02-09 11:34:51 Using discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
2018-02-09 11:34:51 Using discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
2018-02-09 11:34:51 TCP listener ([::]:22000) starting
2018-02-09 11:34:51 Relay listener (dynamic+https://relays.syncthing.net/endpoint.) starting
2018-02-09 11:34:51 Completed initial scan of readwrite folder "Default Folder" (default)
2018-02-09 11:34:51 Device MNGB4X2-GPTU2RR-GQCH3I6-LSGDPLA-X5O36F7-PX74HEA-2LFUJMT-XX4VNAA is "ajmalsha" at [dynamic]
2018-02-09 11:34:51 Syncthing should not run as a privileged or system user. Please consider using a normal user account.
2018-02-09 11:34:51 GUI and API listening on 192.168.1.213:8384
2018-02-09 11:34:51 Access the GUI via the following URL: http://192.168.1.213:8384/
2018-02-09 11:34:52 Relay listener (dynamic+https://relays.syncthing.net/endpoint.) shutting down
2018-02-09 11:34:52 c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint.' (1.000000 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint. dynamic+https://relays.syncthing.net/endpoint.} returned unexpectedly", stacktrace: [unknown stack trace]
2018-02-09 12:04:55 Exiting backoff state.
2018-02-09 12:04:55 Relay listener (dynamic+https://relays.syncthing.net/endpoint.) starting
2018-02-09 12:04:55 Relay listener (dynamic+https://relays.syncthing.net/endpoint.) shutting down
2018-02-09 12:04:55 c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint.' (1.000000 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint. dynamic+https://relays.syncthing.net/endpoint.} returned unexpectedly", 
2018-02-09 12:05:02 UPnP parse: unrecognized UPnP device of type urn:schemas-upnp-org:device:InternetGatewayDevice:1
2018-02-09 12:05:07 UPnP parse: unrecognized UPnP device of type upnp:rootdevice
2018-02-09 12:05:07 UPnP parse: unrecognized UPnP device of type upnp:rootdevice
2018-02-09 12:05:07 UPnP parse: unrecognized UPnP device of type uuid:00000000-0000-1000-0000-60e3279f2e6a
2018-02-09 12:05:07 UPnP parse: unrecognized UPnP device of type uuid:00000000-0000-1000-0000-60e3279f2e6a
2018-02-09 12:05:07 UPnP parse: unrecognized UPnP device of type urn:schemas-wifialliance-org:device:WFADevice:1
2018-02-09 12:05:07 UPnP parse: unrecognized UPnP device of type urn:schemas-wifialliance-org:device:WFADevice:1
2018-02-09 12:05:07 UPnP parse: unrecognized UPnP device of type urn:schemas-wifialliance-org:service:WFAWLANConfig:1
2018-02-09 12:05:07 UPnP parse: unrecognized UPnP device of type urn:schemas-wifialliance-org:service:WFAWLANConfig:1
2018-02-09 12:09:21 Enabled debug data for "connections"

imsodin · February 9, 2018, 7:26am

There should be no . at the end of dynamic+https://relays.syncthing.net/endpoint, that’s why the relay listener fails. However I don’t understand why there are no (failed) tcp attempts, maybe those just aren’t logged at info level. Please enable the connections debug facility on startup via STTRACE=connections environment variable, such that there is more details on the initial connection attempt. Alternatively you can also enable that in the web UI as you do now and then pause and resume an affected device to trigger a new connection and posts logs of what happens after that.

@AudriusButkevicius Any ideas about the UPnP problems? I guess that’s what preventing successful tcp connection.

AudriusButkevicius · February 9, 2018, 8:05am

No this is just informational.

AudriusButkevicius · February 9, 2018, 8:06am

Does the other side have discovery disabled etc? It seems you messed around with settings alot so I am just thinking you caused this by yourself by messing up the config on both sides.

SumiSujith · February 9, 2018, 11:46am

Thanks for the replies.I removed the dot. I connected one device as web and one device as android(Remote Device). Its shows disconnected,and folder not synced. Remote-Devices

Both devices setting configuration’s listen address is given as dynamic+https://relays.syncthing.net/endpoint, tcp://:22000

My device id(Web) is FY7I4C6-EKKNG3D-IVUQV54-B7RRZ6G-GWYC3HC-KGGJNQN-DVL7Z7U-MQGWEQ2

I use syncthing version v0.14.44, Linux (64 bit).

My log is given below

2018-02-09 11:07:46 syncthing v0.14.44 "Dysprosium Dragonfly" (go1.9.2 linux-amd64) teamcity@build.syncthing.net 2018-01-19 06:21:05 UTC
2018-02-09 11:07:46 My ID: FY7I4C6-EKKNG3D-IVUQV54-B7RRZ6G-GWYC3HC-KGGJNQN-DVL7Z7U-MQGWEQ2
2018-02-09 11:07:48 Single thread SHA256 performance is 86 MB/s using crypto/sha256 (83 MB/s using minio/sha256-simd).
2018-02-09 11:07:49 Hashing performance with weak hash is 69.00 MB/s
2018-02-09 11:07:50 Hashing performance without weak hash is 81.25 MB/s
2018-02-09 11:07:50 Weak hash enabled, as it has an acceptable performance impact.
2018-02-09 11:07:50 Ready to synchronize "Default Folder" (default) (readwrite)
2018-02-09 11:07:50 Ready to synchronize "all-horizontal" (all-horizontal) (readonly)
2018-02-09 11:07:50 Ready to synchronize "all-vertical" (all-vertical) (readonly)
2018-02-09 11:07:50 Send rate is unlimited, receive rate is unlimited
2018-02-09 11:07:50 ...
2018-02-09 11:19:00 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46868 (tcp-server) rejected: device is ignored
2018-02-09 11:19:06 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46872 (tcp-server) rejected: device is ignored
2018-02-09 11:19:13 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46880 (tcp-server) rejected: device is ignored
2018-02-09 11:19:19 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46886 (tcp-server) rejected: device is ignored
2018-02-09 11:19:25 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46890 (tcp-server) rejected: device is ignored
2018-02-09 11:19:31 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46904 (tcp-server) rejected: device is ignored
2018-02-09 11:19:38 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46910 (tcp-server) rejected: device is ignored
2018-02-09 11:19:44 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46914 (tcp-server) rejected: device is ignored
2018-02-09 11:19:46 Connection from 6NV37RU-2AXVJKR-FRB7DHM-PP2ZW4X-HHNDLZD-FUBLGZH-3JVDKLS-FWZJXQL at 202.83.55.151:55123 (tcp-server) rejected: device is ignored
2018-02-09 11:19:48 Connection from MNGB4X2-GPTU2RR-GQCH3I6-LSGDPLA-X5O36F7-PX74HEA-2LFUJMT-XX4VNAA at 202.83.55.151:47542 (tcp-server) rejected: device is ignored
2018-02-09 11:19:50 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46918 (tcp-server) rejected: device is ignored
2018-02-09 11:19:57 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46922 (tcp-server) rejected: device is ignored
2018-02-09 11:20:03 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46930 (tcp-server) rejected: device is ignored
2018-02-09 11:20:09 Connection from H5JTUBC-AR2WQPK-3N4VACS-FSI2GA4-LMZ3WMB-DSJETBI-HCTG3GM-YDIF2AF at 118.102.223.138:46934 (tcp-server) rejected: device is ignored
2018-02-09 11:39:50 Enabled debug data for "connections"
2018-02-09 11:39:50 Listen (BEP/tcp): connect from 202.83.55.151:55485
2018-02-09 11:39:51 Listen (BEP/tcp): connect from 202.83.55.151:52396
2018-02-09 11:39:51 Connection from 6NV37RU-2AXVJKR-FRB7DHM-PP2ZW4X-HHNDLZD-FUBLGZH-3JVDKLS-FWZJXQL at 202.83.55.151:55485 (tcp-server) rejected: device is ignored

The remote device is android device and use the syncthing version v.0.10.4

Remote Device id (Android) is RZTKGOJ-T2L3DU6-IZ3AD2S-XXBEPKM-GFNZUJM-FZYQCMK-JAH45CT-MEZQXAV

Its log is given below

[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) shutting down
[RZTKG] INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint,tcp://:22000' (1.000000 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint,tcp://:22000 dynamic+https://relays.syncthing.net/endpoint,tcp://:22000} returned unexpectedly", stacktrace: [unknown stack trace]
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) starting
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) shutting down
[RZTKG] INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint,tcp://:22000' (1.990922 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint,tcp://:22000 dynamic+https://relays.syncthing.net/endpoint,tcp://:22000} returned unexpectedly", stacktrace: [unknown stack trace]
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) starting
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) shutting down
[RZTKG] INFO: Entering the backoff state.
[RZTKG] INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint,tcp://:22000' (2.974527 failures of 2.000000), restarting: false, error: "{dynamic+https://relays.syncthing.net/endpoint,tcp://:22000 dynamic+https://relays.syncthing.net/endpoint,tcp://:22000} returned unexpectedly", stacktrace: [unknown stack trace]
[RZTKG] INFO: syncthing v0.14.44-rc.2+21-g14a5561 "Dysprosium Dragonfly" (go1.9 android-arm) noufal@noufal 2018-01-28 11:26:01 UTC [noupgrade]
[RZTKG] INFO: My ID: RZTKGOJ-T2L3DU6-IZ3AD2S-XXBEPKM-GFNZUJM-FZYQCMK-JAH45CT-MEZQXAV
[RZTKG] INFO: Disabling weak hash
[RZTKG] INFO: Starting deadlock detector with 20m0s timeout
[RZTKG] INFO: Ready to synchronize "Camera" (motog3-te-photos) (readonly)
[RZTKG] INFO: Send rate is unlimited, receive rate is unlimited
[RZTKG] INFO: Rate limits do not apply to LAN connections
[RZTKG] INFO: Using discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[RZTKG] INFO: Using discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[RZTKG] INFO: Using discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-VI3NYZR-ALCJBHF-WMZYSPK-QG6QJA3-MPFYMSO-U56GTUK-NA2MIAW
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) starting
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) shutting down
[RZTKG] INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint,tcp://:22000' (1.000000 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint,tcp://:22000 dynamic+https://relays.syncthing.net/endpoint,tcp://:22000} returned unexpectedly", stacktrace: [unknown stack trace]
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) starting
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) shutting down
[RZTKG] INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint,tcp://:22000' (1.999818 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint,tcp://:22000 dynamic+https://relays.syncthing.net/endpoint,tcp://:22000} returned unexpectedly", stacktrace: [unknown stack trace]
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) starting
[RZTKG] INFO: Relay listener (dynamic+https://relays.syncthing.net/endpoint,tcp://:22000) shutting down
[RZTKG] INFO: Entering the backoff state.
[RZTKG] INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint,tcp://:22000' (2.999596 failures of 2.000000), restarting: false, error: "{dynamic+https://relays.syncthing.net/endpoint,tcp://:22000 dynamic+https://relays.syncthing.net/endpoint,tcp://:22000} returned unexpectedly", stacktrace: [unknown stack trace]
[RZTKG] INFO: Completed initial scan of readonly folder "Camera" (motog3-te-photos)
[RZTKG] INFO: Device RZTKGOJ-T2L3DU6-IZ3AD2S-XXBEPKM-GFNZUJM-FZYQCMK-JAH45CT-MEZQXAV is "MotoG3-TE" at [dynamic]
[RZTKG] INFO: Anonymous usage reporting is always enabled for candidate releases.
[RZTKG] INFO: GUI and API listening on 127.0.0.1:8384
[RZTKG] INFO: Access the GUI via the following URL: http://127.0.0.1:8384/
[RZTKG] INFO: No automatic upgrades; STNOUPGRADE environment variable defined.

AudriusButkevicius · February 9, 2018, 2:01pm

On android the listen address is incorrect, and should probably be space separated.

SumiSujith · February 9, 2018, 2:12pm

Prior this attempt we had used space in listen address.

there also we got issue, we found %20(encode character) is coming in the listen address.

imsodin · February 9, 2018, 2:14pm

~~I just had a look, and in the web UI you need to mandatory use comma and a space (", "). That’s a bit silly, I think we should allow either comma or just a space and any amount of spaces.~~ We already do that, as seen by calmh’s comment below and actually looking at the code xD

github.com

syncthing/syncthing/blob/master/gui/default/syncthing/core/syncthingController.js#L1216


    if ($scope.config.gui.useTLS !== $scope.tmpGUI.useTLS) {
        $scope.protocolChanged = true;
    }


    // Apply new settings locally
    $scope.thisDevice().name = $scope.tmpOptions.deviceName;
    $scope.config.options = angular.copy($scope.tmpOptions);
    $scope.config.gui = angular.copy($scope.tmpGUI);


    ['listenAddresses', 'globalAnnounceServers'].forEach(function (key) {
        $scope.config.options[key] = $scope.config.options["_" + key + "Str"].split(/[ ,]+/).map(function (x) {
            return x.trim();
        });
    });


    $scope.saveConfig(function () {
        if (themeChanged) {
            document.location.reload(true);
        }
    });
}

calmh · February 9, 2018, 2:16pm

That splits on any sequence of commas and spaces, so it’s quite generous.

imsodin · February 9, 2018, 2:20pm

You’re right of course, I should actually read what’s there instead of just assuming it confirms what I suspected…

SumiSujith · February 9, 2018, 2:20pm

I have given listen address in UI is dynamic+https://relays.syncthing.net/endpoint, tcp://:22000

imsodin · February 9, 2018, 2:36pm

Something went wrong, as the following line from your log shows:

[RZTKG] INFO: c.S.listenerSupervisor: Failed service 'dynamic+https://relays.syncthing.net/endpoint,tcp://:22000' (1.000000 failures of 2.000000), restarting: true, error: "{dynamic+https://relays.syncthing.net/endpoint,tcp://:22000 dynamic+https://relays.syncthing.net/endpoint,tcp://:22000} returned unexpectedly", stacktrace: [unknown stack trace]

The two parts weren’t separated somehow. So please reopen the web UI on that device and re-enter/-check the listen address.

@AudriusButkevicius @calmh Would it make sense to check for commas/spaces in the listen address (and maybe other addresses) during the config cleaning stage?

calmh · February 9, 2018, 2:41pm

Honestly I’d rather not, at least the relay pool thing is a regular HTTPS URL and commas could be included in it. The (web) GUI wouldn’t handle that unless quoted. But when it reaches us via the API or from the config file it’s as lists of strings. I don’t think we should second guess the contents of the strings themselves really.

Do we know how this string ended up being in the config?

system · March 11, 2018, 2:41pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.