Help here the same, today people call and say they needed to mail files back and forth with other friends or family as they wouldnt see their shared folder and their changes on either side.
I am looking at two select machines here, one linux x64 and one windows x64, they both upgraded and arrived at 0.14.40 automagically.
On both sides nothing network-wise has changed, same home router, home gateway, the linux machine has opened up tcp port 22000 ever since initial install on the internet router (portforward) the other user on the windows side is more like a notebook roaming roadwarrior user.
The syncthing process on both sides is running, i see the localhost config and information webpage of it.
The odd stuff is, the linux and the windows machine, on the right lower side, where the other machines/peers are listed, that the last contact was all like one day ago. Just before or when the 0.14.40 release was pushed to the public?
The peers are not paused. Restarted syncthing but they wouldnt connect.
Normal small network home network scenario here, so no fancy network rules or blocking of anything, be it udp or tcp. Only thing has changed methinks is the new 0.14.40 release and maybe we have a race condition or faulty decsision process on what transport udp tcp kcp to use somewhere in the code?
One more thing: the windows machine, (i am administrating the syncthing process there) would show a hovering layer on the syncthing config page, that the anon stat data type or whatever internally has changed and if I wanted to swap over to the new data format or something the like. Maybe this decision is blocking the rest of the functionality when it has not been decided and actively surfed and answered yet? Just wondering.
What can I report more? Thanks for resorting this quickly.
p.s. i have copied over and pseudonymised some log lines that are currently visible on the linux syncthing. it fails with hello messages the log says.
[A1B2C3] 10:35:56 INFO: Failed to exchange Hello messages with XXXXX-BBBBB-AAAAAA-CCCCC (188.8.131.52:7729): i/o timeout
[A1B2C3] 10:36:16 INFO: Failed to exchange Hello messages with YYYYYY-FFFFF-BBBBBB-DDDDDDDD (192.168.1.2:22020): i/o timeout
[A1B2C3] 10:37:11 INFO: Failed to exchange Hello messages with XXXXX-BBBBB-AAAAAA-CCCCC (184.108.40.206:22067): read tcp 192.168.1.3:59728->220.127.116.11:22067: i/o timeout
[A1B2C3] 10:37:31 INFO: Failed to exchange Hello messages with YYYYYY-FFFFF-BBBBBB-DDDDDDDD (192.168.1.2:22000): read tcp 192.168.1.3:53590->192.168.1.2:22000: i/o timeout
more info: restarted the linux syncthing, and two external (other) machines one macosx and one win x64 (but different than above) do connect from externally, both reporting them being as well on 0.14.40, they connect via tcp ipv4, maybe this is another hint. The first x64 machine externally is also having ipv6 address by its ISP.
The log with the failing hello I posted from above is from that failing win x64 machine for example but also from other ones.