I have some problems to get my private discovery server beeing available. All web-interfaces show: “Globale Auffindung 0/1” (in red font).
On debian 6 I started the discosrv with the following command:
./discosrv -db-dir="./db" -stats-file="./stats/stats" -timestamp=true -listen=":22026" &
The process runs.
IN LOG there are some informations:
=============== Jan 20, 2015 (CET) ===============
12:53:36.083023 log@legend F·NumFile S·FileSize N·Entry C·BadEntry B·BadBlock Ke·KeyError D·DroppedEntry L·Level Q·SeqNum T·TimeElapsed
12:53:36.231023 db@open opening
12:53:36.231023 journal@recovery F·1
12:53:36.231023 journal@recovery recovering @8
12:53:36.247023 db@janitor F·2 G·0
12:53:36.247023 db@open done T·16ms
The entry in the web-interface of my syncthing-installations is
where xxx.xx.xxx.xxx is for the ip of the debian server.
The address of the syncprotocol is 0.0.0.0:22000
All web-interfaces show: Globale Auffindung 0/1 (in red font).
The firewall is temporarily switched off.
The router has the following entry (see sreenshot)
UPnp is activated, but I think, its a problem of the router port configuration.
The log is a database log so it’s not awfully useful.
It seems (I don’t understand the language) that you are forwarding 22026 to 22000 which is also wrong.
Syncthing <-> Discovery communicate over 22026 UDP
Syncthing <-> Syncthing communicate over 22000 TCP
Try the -debug flag to see if the packets are arriving.
Also, try sending random UDP packets to the announce server to verify if it’s receiving them, it should print some errors about packets being too short etc, if it’s not a valid announcement.
yeah the forwarding is from 22026 to 22000, the discovery server will never read the packages since it listens to 22026 and gets packages on 22000. Change “an Port” to 22026 and it should work.
I tried plan B, (because it seems too dificult for me to solve the issue on debian): Installing the Windows 64 bit release of discosrv.exe. It works for FreeBSD, Win 8.1 32 bit, Win7, 64 bit, Win7 32 bit. (BTW: There was no need to change the router configuration.)
But there is a new problem when I try to configure the global (dyndns-)server on my samsung tablet galaxy tab 3 7" with kitkat:
17:37:55: discover udp4://dummy.dyndns.org:22026: broadcast: stat /etc/resolv.conf: no such file or directory; trying again in 1m0s
17:38:55: discover udp4://dummy.dyndns.org:22026: broadcast: stat /etc/resolv.conf: no such file or directory; trying again in 1m0s
17:40:22: discover udp4://dummy.dyndns.org:22026: broadcast: stat /etc/resolv.conf: no such file or directory; trying again in 1m0s
17:41:36: discover udp4://dummy.dyndns.org:22026: broadcast: stat /etc/resolv.conf: no such file or directory; trying again in 1m0s
(Surprisingly, there is no way to configure the global discovery server in the app; only in the web interface)
Edit: When I put in the IP-number instead of the dyndns name, the global discovery server is found by the tablet. (But only until the next change of the ip-address.) It would be helpfull, if this issue (?) would be solved.
Syncthing on Android doesn’t have DNS support: