Disconnected devices

Support
1

Hello, I’m on v1.24.0 Linux, with two shares folders. Since one week, after I reboot my own server, I can’t succeed to connect my two devices. They’re still in disconnect state.

Here some log, hope help :

2023-09-18 15:56:02 failed to connect to XxX 30 2023-09-18 15:56:02 dialing XxX quic://LanIP:22000 prio 40 2023-09-18 15:56:02 dialing XxX quic://WanIP:22000 prio 40 2023-09-18 15:56:02 dialing XxX quic://[XxX]:22000 prio 40 2023-09-18 15:56:02 dialing XxX quic://[XxX]:22000 error: dial: INTERNAL_ERROR (local): write udp [::]:22000->[XxX]:22000: sendmsg: cannot assign requested address 2023-09-18 15:56:07 dialing XxX quic://WanIP:22000 error: dial: timeout: no recent network activity 2023-09-18 15:56:07 dialing XxX quic://LanIP:22000 error: dial: timeout: no recent network activity 2023-09-18 15:56:07 failed to connect to XxX 40 2023-09-18 15:56:07 Next connection loop in 20s 2023-09-18 15:56:27 Connection loop 2023-09-18 15:56:27 Resolved device XxX addresses: [quic://LanIP:22000 quic://WanIP:22000 quic://[XxX]:22000 relay://49.12.93.194:22067/?id=XxX tcp://LanIP:22000 tcp://WanIP:22000 tcp://[XxX]:22000] 2023-09-18 15:56:27 Not dialing XxX via relay://49.12.93.194:22067/?id=XxX as it’s not time yet 2023-09-18 15:56:27 Not dialing XxX via tcp://LanIP:22000 as it’s not time yet 2023-09-18 15:56:27 Not dialing XxX via tcp://WanIP:22000 as it’s not time yet 2023-09-18 15:56:27 Not dialing XxX via tcp://[XxX]:22000 as it’s not time yet 2023-09-18 15:56:27 dialing XxX quic://LanIP:22000 prio 40 2023-09-18 15:56:27 dialing XxX quic://WanIP:22000 prio 40 2023-09-18 15:56:27 dialing XxX quic://[XxX]:22000 prio 40 2023-09-18 15:56:27 dialing XxX quic://[XxX]:22000 error: dial: INTERNAL_ERROR (local): write udp [::]:22000->[XxX]:22000: sendmsg: cannot assign requested address 2023-09-18 15:56:32 dialing XxX quic://LanIP:22000 error: dial: timeout: no recent network activity 2023-09-18 15:56:32 dialing XxX quic://WanIP:22000 error: dial: timeout: no recent network activity 2023-09-18 15:56:32 failed to connect to XxX 40 2023-09-18 15:56:32 Next connection loop in 20s 2023-09-18 15:56:52 Connection loop 2023-09-18 15:56:52 Resolved device XxX addresses: [quic://LanIP:22000 quic://WanIP:22000 quic://[XxX]:22000 relay://49.12.93.194:22067/?id=XxX tcp://LanIP:22000 tcp://WanIP:22000 tcp://[XxX]:22000] 2023-09-18 15:56:52 Dialer for relay://49.12.93.194:22067/?id=XxX: unsupported protocol: disabled by configuration 2023-09-18 15:56:52 dialing XxX tcp://[XxX]:22000 prio 30 2023-09-18 15:56:52 dialing XxX tcp://WanIP:22000 prio 30 2023-09-18 15:56:52 dialing XxX tcp://LanIP:22000 prio 30 2023-09-18 15:56:52 Dialing reuse result tcp [XxX]:22000: dial tcp [::]:22000->[XxX]:22000: connect: cannot assign requested address 2023-09-18 15:56:52 Dialing non-reuse result tcp [XxX]:22000: dial tcp [XxX]:22000: connect: cannot assign requested address 2023-09-18 15:56:52 dialing XxX tcp://[XxX]:22000 error: dial tcp [XxX]:22000: connect: cannot assign requested address

2

Did you hardcode the listening address? Sounds like your server got a new IP after the reboot.

3

I use device ID to connect my two devices

4

Firewall?

5

Do you have a non-standard listen address configured? Are you using some sort of VPN?

Syncthing tries to connect out on the same address it is listening on, and seems it is not allowed.

6

The error might be caused by dialing a public IPv6 on a host without a GUA IPv6. But that still doesn’t explain why it’s not working for IPv4.

7

Maybe, I needed to reboot my internet box. How can I see Syncthing dialing with ipv6?

8

Could you post the logs and only redact parts of the IPs?

9

Here we go

2023-09-18 16:10:51 My ID: 7UYSQAK-xxx 2023-09-18 16:10:52 Single thread SHA256 performance is 1493 MB/s using minio/sha256-simd (364 MB/s using crypto/sha256). 2023-09-18 16:10:53 Hashing performance is 899.61 MB/s 2023-09-18 16:10:53 Device 3YCP6SQ-xxx send rate limit is 20000 KiB/s, receive rate limit is 20000 KiB/s 2023-09-18 16:10:53 Overall send rate limit is 20000 KiB/s, receive rate limit is 20000 KiB/s 2023-09-18 16:10:53 Rate limits do not apply to LAN connections 2023-09-18 16:10:53 Using discovery mechanism: global discovery server https://discovery.syncthing.net/v2/?noannounce&id=LYXKCHX-xxx 2023-09-18 16:10:53 Using discovery mechanism: global discovery server https://discovery-v4.syncthing.net/v2/?nolookup&id=LYXKCHX-xxx 2023-09-18 16:10:53 Using discovery mechanism: global discovery server https://discovery-v6.syncthing.net/v2/?nolookup&id=LYXKCHX-xxx 2023-09-18 16:10:53 Ready to synchronize “US-Movies” (hm3ek-2xzpp) (sendonly) 2023-09-18 16:10:53 … 2023-09-18 16:10:53 QUIC listener ([::]:22000) starting 2023-09-18 16:10:53 TCP listener ([::]:22000) starting 2023-09-18 16:10:53 Ready to synchronize “US-TvShows” (ymeru-qdgcj) (sendonly) 2023-09-18 16:10:53 GUI and API listening on [::]:8384 2023-09-18 16:10:53 Access the GUI via the following URL: http://127.0.0.1:8384/ 2023-09-18 16:10:53 My name is “Ultra Seedbox” 2023-09-18 16:10:53 Device 3YCP6SQ-xxx is “Proxmox” at [dynamic] 2023-09-18 16:10:54 Completed initial scan of sendonly folder “US-Movies” (hm3ek-2xzpp) 2023-09-18 16:10:56 Completed initial scan of sendonly folder “US-TvShows” (ymeru-qdgcj) 2023-09-18 16:11:03 quic://0.0.0.0:22000 detected NAT type: Symmetric NAT 2023-09-18 16:11:07 Detected 1 NAT service 2023-09-18 16:53:24 Ready to synchronize “US-Movies” (hm3ek-2xzpp) (sendonly) 2023-09-18 16:53:24 Restarted folder “US-Movies” (hm3ek-2xzpp) (sendonly) 2023-09-18 16:53:24 Ready to synchronize “US-TvShows” (ymeru-qdgcj) (sendonly) 2023-09-18 16:53:24 Restarted folder “US-TvShows” (ymeru-qdgcj) (sendonly) 2023-09-18 16:53:27 Completed initial scan of sendonly folder “US-Movies” (hm3ek-2xzpp) 2023-09-18 16:53:30 Completed initial scan of sendonly folder “US-TvShows” (ymeru-qdgcj) 2023-09-18 16:53:51 Device 3YCP6SQ-xxx send rate limit is 20000 KiB/s, receive rate limit is 20000 KiB/s 2023-09-18 16:53:51 Ready to synchronize “US-Movies” (hm3ek-2xzpp) (sendonly) 2023-09-18 16:53:51 Restarted folder “US-Movies” (hm3ek-2xzpp) (sendonly) 2023-09-18 16:53:51 Ready to synchronize “US-TvShows” (ymeru-qdgcj) (sendonly) 2023-09-18 16:53:51 Restarted folder “US-TvShows” (ymeru-qdgcj) (sendonly) 2023-09-18 16:53:51 Completed initial scan of sendonly folder “US-Movies” (hm3ek-2xzpp) 2023-09-18 16:53:52 Completed initial scan of sendonly folder “US-TvShows” (ymeru-qdgcj) 2023-09-18 19:43:17 Listen (BEP/tcp): TLS handshake: read tcp 172.17.1.75:22000->167.248.133.39:32892: read: connection reset by peer 2023-09-18 19:43:18 Peer at 172.17.1.75:22000-167.248.133.39:55844/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P30 did not negotiate bep/1.0 2023-09-18 19:43:18 Got peer certificate list of length 0 != 1 from peer at 172.17.1.75:22000-167.248.133.39:55844/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P30; protocol error 2023-09-18 19:43:19 Peer at 172.17.1.75:22000-167.248.133.39:52212/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P30 did not negotiate bep/1.0 2023-09-18 19:43:19 Got peer certificate list of length 0 != 1 from peer at 172.17.1.75:22000-167.248.133.39:52212/tcp-server/TLS1.3-TLS_CHACHA20_POLY1305_SHA256/WAN-P30; protocol error 2023-09-18 19:43:20 Listen (BEP/tcp): TLS handshake: tls: first record does not look like a TLS handshake 2023-09-18 19:43:21 Listen (BEP/tcp): TLS handshake: read tcp 172.17.1.75:22000->167.248.133.39:41226: read: connection reset by peer 2023-09-19 00:17:12 Listen (BEP/tcp): TLS handshake: tls: client offered only unsupported versions: [303 302 301] 2023-09-19 00:17:13 Listen (BEP/tcp): TLS handshake: tls: client offered only unsupported versions: [301 302 303] 2023-09-19 00:17:13 Listen (BEP/tcp): TLS handshake: tls: client offered only unsupported versions: [303 302 301] 2023-09-19 00:17:13 Listen (BEP/tcp): TLS handshake: tls: client offered only unsupported versions: [303 302 301] 2023-09-19 00:17:13 Listen (BEP/tcp): TLS handshake: tls: client offered only unsupported versions: [303 302 301] 2023-09-19 00:17:14 Listen (BEP/tcp): TLS handshake: tls: client offered only unsupported versions: [302 301] 2023-09-19 00:17:14 Listen (BEP/tcp): TLS handshake: tls: client requested unsupported application protocols ([hq h2c h2 spdy/3 spdy/2 spdy/1 http/1.1 http/1.0 http/0.9]) 2023-09-19 00:17:14 Listen (BEP/tcp): TLS handshake: tls: client requested unsupported application protocols ([http/0.9 http/1.0 http/1.1 spdy/1 spdy/2 spdy/3 h2 h2c hq]) 2023-09-19 00:17:14 Listen (BEP/tcp): TLS handshake: tls: no cipher suite supported by both client and server 2023-09-19 00:17:15 Listen (BEP/tcp): TLS handshake: tls: client requested unsupported application protocols ([hq h2c h2 spdy/3 spdy/2 spdy/1 http/1.1 http/1.0 http/0.9]) 2023-09-19 09:00:15 Wrong credentials supplied during API authorization from 172.17.0.1:26880 2023-09-19 09:02:13 Pausing 3YCP6SQ-xxx 2023-09-19 09:02:15 Resuming 3YCP6SQ-xxx 2023-09-19 09:45:15 Enabled debug data for “dialer” 2023-09-19 09:45:16 Enabled debug data for “discover” 2023-09-19 09:45:18 Enabled debug data for “connections” 2023-09-19 09:45:19 dialing 3YCP6SQ-xxx quic://82.64.xxx:22000 error: dial: timeout: no recent network activity 2023-09-19 09:45:19 dialing 3YCP6SQ-xxx quic://192.168.xxx:22000 error: dial: timeout: no recent network activity 2023-09-19 09:45:19 failed to connect to 3YCP6SQ-xxx 40 2023-09-19 09:45:19 Next connection loop in 20s 2023-09-19 09:45:39 Connection loop 2023-09-19 09:45:39 negative cache entry for 3YCP6SQ-xxx at global@https://discovery-v6.syncthing.net/v2/ valid until 2023-09-19 09:13:36.32435095 +0200 CEST m=+61364.592302979 or 2023-09-19 10:12:36.32435102 +0200 CEST m=+64904.592303039 2023-09-19 09:45:39 cached discovery entry for 3YCP6SQ-xxx at global@https://discovery.syncthing.net/v2/ 2023-09-19 09:45:39 cache: {[quic://192.168.xxx:22000 quic://82.64.xxx:22000 quic://82.64.xxx:22000 quic://[2a01:xxx]:22000 relay://212.5.154.218:443/?id=W42JIMZ-CAX2EUD-BRRVKZB-7OPY2EG-WTXRK65-VVKNURK-DF44QQH-6U2BYQ6 tcp://192.168.xxx:22000 tcp://82.64.xxx:22000 tcp://82.64.xxx:22000 tcp://[2a01:xxx]:22000 tcp://[2a01:xxx]:22000] {13923566662241067615 63108028801020 0x1a30900} true {0 0 } 0} 2023-09-19 09:45:39 negative cache entry for 3YCP6SQ-xxx at global@https://discovery-v4.syncthing.net/v2/ valid until 2023-09-19 09:13:36.324349597 +0200 CEST m=+61364.592301626 or 2023-09-19 10:12:36.324350188 +0200 CEST m=+64904.592302207 2023-09-19 09:45:39 lookup results for 3YCP6SQ-xxx 2023-09-19 09:45:39 addresses: [quic://192.168.xxx:22000 quic://82.64.xxx:22000 quic://[2a01:xxx]:22000 relay://212.5.154.218:443/?id=W42JIMZ-CAX2EUD-BRRVKZB-7OPY2EG-WTXRK65-VVKNURK-DF44QQH-6U2BYQ6 tcp://192.168.xxx:22000 tcp://82.64.xxx:22000 tcp://[2a01:xxx]:22000] 2023-09-19 09:45:39 Resolved device 3YCP6SQ-xxx addresses: [quic://192.168.xxx:22000 quic://82.64.xxx:22000 quic://[2a01:xxx]:22000 relay://212.5.154.218:443/?id=W42JIMZ-CAX2EUD-BRRVKZB-7OPY2EG-WTXRK65-VVKNURK-DF44QQH-6U2BYQ6 tcp://192.168.xxx:22000 tcp://82.64.xxx:22000 tcp://[2a01:xxx]:22000] 2023-09-19 09:45:39 Dialer for relay://212.5.154.218:443/?id=W42JIMZ-CAX2EUD-BRRVKZB-7OPY2EG-WTXRK65-VVKNURK-DF44QQH-6U2BYQ6: unsupported protocol: disabled by configuration 2023-09-19 09:45:39 dialing 3YCP6SQ-xxx tcp://[2a01:xxx]:22000 prio 30 2023-09-19 09:45:39 dialing 3YCP6SQ-xxx tcp://82.64.xxx:22000 prio 30 2023-09-19 09:45:39 Dialing reuse result tcp [2a01:xxx]:22000: dial tcp [::]:22000->[2a01:xxx]:22000: connect: cannot assign requested address 2023-09-19 09:45:39 dialing 3YCP6SQ-xxx tcp://192.168.xxx:22000 prio 30 2023-09-19 09:45:39 Dialing non-reuse result tcp [2a01:xxx]:22000: dial tcp [2a01:xxx]:22000: connect: cannot assign requested address 2023-09-19 09:45:39 dialing 3YCP6SQ-xxx tcp://[2a01:xxx]:22000 error: dial tcp [2a01:xxx]:22000: connect: cannot assign requested address 2023-09-19 09:45:39 Dialing reuse result tcp 82.64.xxx:22000: dial tcp [::]:22000->82.64.xxx:22000: connect: cannot assign requested address 2023-09-19 09:45:49 Dialing non-reuse result tcp 82.64.xxx:22000: dial tcp 82.64.xxx:22000: i/o timeout 2023-09-19 09:45:49 Dialing non-reuse result tcp 192.168.xxx:22000: dial tcp 192.168.xxx:22000: i/o timeout 2023-09-19 09:45:49 Dialing reuse result tcp 192.168.xxx:22000: dial tcp [::]:22000->192.168.xxx:22000: i/o timeout 2023-09-19 09:45:49 dialing 3YCP6SQ-xxx tcp://192.168.xxx:22000 error: dial tcp 192.168.xxx:22000: i/o timeout 2023-09-19 09:45:49 dialing 3YCP6SQ-xxx tcp://82.64.xxx:22000 error: dial tcp 82.64.xxx:22000: i/o timeout 2023-09-19 09:45:49 failed to connect to 3YCP6SQ-xxx 30 2023-09-19 09:45:49 dialing 3YCP6SQ-xxx quic://82.64.xxx:22000 prio 40 2023-09-19 09:45:49 dialing 3YCP6SQ-xxx quic://192.168.xxx:22000 prio 40 2023-09-19 09:45:49 dialing 3YCP6SQ-xxx quic://[2a01:xxx]:22000 prio 40 2023-09-19 09:45:49 dialing 3YCP6SQ-xxx quic://[2a01:xxx]:22000 error: dial: INTERNAL_ERROR (local): write udp [::]:22000->[2a01:xxx]:22000: sendmsg: cannot assign requested address 2023-09-19 09:45:54 dialing 3YCP6SQ-xxx quic://82.64.xxx:22000 error: dial: timeout: no recent network activity 2023-09-19 09:45:54 dialing 3YCP6SQ-xxx quic://192.168.xxx:22000 error: dial: timeout: no recent network activity 2023-09-19 09:45:54 failed to connect to 3YCP6SQ-xxx 40 2023-09-19 09:45:54 Next connection loop in 20s 2023-09-19 09:45:56 global@https://discovery-v6.syncthing.net/v2/ Announcement: {[quic://0.0.0.0:22000 quic://172.17.1.75:22000 tcp://0.0.0.0:22000 tcp://172.17.1.75:22000 tcp://0.0.0.0:0]} 2023-09-19 09:45:56 Dialing reuse result tcp discovery-v6.syncthing.net:443: dial tcp [::]:22000->[2a03:b0c0:0:1010::bb:4001]:443: connect: cannot assign requested address 2023-09-19 09:45:56 Dialing non-reuse result tcp discovery-v6.syncthing.net:443: dial tcp [2400:6180:100:d0::741:a001]:443: connect: cannot assign requested address 2023-09-19 09:45:56 global@https://discovery-v6.syncthing.net/v2/ announce POST: Post “https://discovery-v6.syncthing.net/v2/”: dial tcp [2400:6180:100:d0::741:a001]:443: connect: cannot assign requested address

10

The 172.17.17.75 looks like an internal docker IP. Could you share the command you’re using or the compose file if that’s the case?

11

I think it is address of my external node on ultraseedbox. I just install package by they own services.

12

Looks like you need to configure the address manually:

If that doesn’t work :man_shrugging:

13

Where I can configure it manually?

14

I’d try to follow the linked documentation of your provider. Check the Setting up Syncthing on Slot section.

1 Like
16

After uninstall and install Syncthing on my remote node. I can see my nodes. First sync is in progress. Hope problem is solved.

Thanks for your time and your help.