Yes i did, i ran it on a pi4 do see if id get the same results, syncthing throwing the same error.
Sorry, but this is beyond me.
I am fairly certain it will be something on the device itself, potentially hijacking syncthingâs https traffic to discovery servers.
Whether its a firewall, ip tables rules, some proxy, I donât know.
Sorry, I know this is not a very helpful answer, but I am out of suggestions.
no worries, thanks for your time. Iâll try some things and hopefully sort it out.
Just as a datapoint, Iâm getting the exact same issue with the same connection issues. My client is the 64-bit linux client and my firewall is normal linux machine running iptables and NAT. I even opened a firewall port (22000) from my firewall back into my machine running syncthing to see if that would help, but no. My firewall (linux w/ iptables) doesnât do any man-in-the-middle SSL interception.
steve@plex02:~/.config/syncthing$ curl -k https://discovery-v4.syncthing.net/v2/
Not Found
steve@plex02:~/.config/syncthing$ curl -kI https://discovery-v4.syncthing.net/v2/
HTTP/1.1 405 Method Not Allowed
Server: nginx/1.10.3 (Ubuntu)
Date: Wed, 14 Jul 2021 16:21:40 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 19
Connection: keep-alive
X-Content-Type-Options: nosniff
Ok, the call to the discovery-v4.syncthing.net is taking > 5 seconds, which is the timeout value in the code, so the discovery server is probably getting hammered. Thatâs why this issue is so sporadic by users in the forums. Increase the timeout or fix the server maybe?
steve@plex02:~/.config/syncthing$ time curl -kI https://discovery-v4.syncthing.net/v2/
HTTP/1.1 405 Method Not Allowed
Server: nginx/1.10.3 (Ubuntu)
Date: Wed, 14 Jul 2021 16:45:04 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 19
Connection: keep-alive
X-Content-Type-Options: nosniff
real 0m6.253s
user 0m0.072s
sys 0m0.016s
So, FYI. After rebuilding from source and changeing the timeout from 5 seconds to 30 seconds, it connected and Iâm up and running with no other modifications. I suggest changing it in the source or fixing your discover-v4 server to make it less laggy.
There are two global servers serving discovery, both of them look healthy in terms of response times, as per stats:
https://monitor.syncthing.net/dashboard/db/discovery?orgId=1
There must be something wrong your end, as otherwise weâd have tons of people complaining.
Perhaps your DNS resolution is acting up and taking a while?
Just for reference, from my end:
root@box:~# time curl -kI https://discovery-v4.syncthing.net/v2/
HTTP/1.1 405 Method Not Allowed
Server: nginx/1.10.3 (Ubuntu)
Date: Wed, 14 Jul 2021 18:09:15 GMT
Content-Type: text/plain; charset=utf-8
Content-Length: 19
Connection: keep-alive
X-Content-Type-Options: nosniff
real 0m0.117s
user 0m0.024s
sys 0m0.006s
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.