Yes, i have.
Sorry by noob’s question maybe, but i’m standard user )
I will write by on the items like it pointed out on docs.
Run stdiscosrv without any flags on server (ubuntu 16.04)
At first start stdiscosrv generated certificate files by default ./cert.pem and ./key.pem in same directory, database doesn’t generated in same directory (by discription it has to)
After that have a note:
“Server device ID is QN5PG5M-JYYZFR7-ECUMUYY-NSCQDN4-2YX7PBK-NSD5XYO-THOJ25R-DQSZAQV” and later Stats: 0.00 announces/s, 0.00 queries/s, 0.00 answers/s, 0.00 errors/s
in section “Certificates” my case is "Use any certificate pair and let clients authenticate the server based on its “device ID” (similar to Syncthing-to-Syncthing authentication). This option can be used with the certificate automatically generated by the discovery server."
The discovery server generate its device ID at start. So i write ID in the discovery server conection settings URL https://mydomein.com:8443/?id=QN5PG5M-JYYZFR7-ECUMUYY-NSCQDN4-2YX7PBK-NSD5XYO-THOJ25R-DQSZAQV
after this actions i have error that https://mydomein.com:8443/ not found. If i write for the experiment https://mydomein.com:8443 only, have an error in ssh-client “http: TLS handshake error from [2a00:f940:1:1:2::c1d]:35468: remote error: tls: bad certificate” as it should be.
But i can’t understand why discovery server not found after ID has pointed out.
0.14.44 is the latest, recommended version. That it doesn’t get the “latest release” badge is a quirk of there not being any source in that actual repo and should be fixed…
Have a VPS and domain with valid CA-signed SSL certificate.
In accordance with docs i have to change settings as https://disco.example.com, without any ID, 443 by default.
After i’ve done it, there are no any errors “global@…” or something about “TLS handshake error from [2a00:f940:1:1:2::193]:53488: remote error: tls: bad certificate” in ssh-client, but haven’t any connections too, all devices are disconnected (discovery server address for all the same).
…and in another case by default settings (remote device with my domain adress in the settings, without any “@global” errors too). In case of usage default setting on both devices all is ok as it should be.