Syncthing discover server -- How best to debug and test

[kevdog]

So I’m in the process of setting up a syncthing discovery server. Syncthing is not being run on the docker host of the syncthing server. I’ve put the discovery server behind an nginx reverse proxy (npm).

I’m using a slightly modified docker image found here: https://github.com/t4skforce/syncthing-discovery

I’m starting with the parameters: ${USER_HOME}/server/discosrv
-listen=":${SERV_PORT}"
-db-dir="${USER_HOME}/db/discosrv.db"
-http

Anyway container is up and running:

stdiscosrv v1.8.0 "Fermium Flea" (go1.13.8 linux-amd64) teamcity@build.syncthing.net 2020-08-07 06:09:12 UTC
Failed to load keypair. Generating one, this might take a while...
Server device ID is DAL5CM2-GRBAGMM-SH52QZK-ZYCRVX7-W4QTKR3-S2EVKKY-AXYDXTJ-T2FEOQR

I’ve added the reverse proxy with the modified headers as explained:

proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Client-Port $remote_port;
proxy_set_header X-SSL-Cert $ssl_client_cert;
ssl_verify_client optional_no_ca;

I’ve aimed my syncthing macbook installation at the disco server:

Soooo – What’s best method to try to debug this to see if it works?

[calmh (Jakob Borg)]

STTRACE=discovery on the Syncthing instance for trace logs of the discovery process. You can ask the discovery server for a device which should be announcing itself there:

% curl -k https://discovery.syncthing.net/v2?device=3A5JXRK-...etc
{"seen":"2021-01-17T20:18:36.013035551Z","addresses":...