Help post about discovery services

Support
1

I have deployed the discosrv service in k3s, and I have fully ensured the implementation of the following configurations:

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;

When I manually execute the request:

curl --location --request POST 'https://meserver.com/' \
--header 'Content-Type: application/json' \
--header 'Accept: */*' \
--header 'Cache-Control: no-cache' \
--header 'Host: meserver.com' \
--header 'Connection: keep-alive' \
--data-raw '{
    "addresses": [
        "relay://1.1.1.1:11111/?id=xxxxxxxxx",
        "tcp://0.0.0.0:22000",
        "tcp://1.1.1.1:22000",
        "tcp://1.1.1.1:22000",
        "tcp://0.0.0.0:0",
        "quic://0.0.0.0:22000"
    ]
}'

image

As shown in the figure, it seems that the registration was successful, and my client certificate has been successfully passed to the discovery service. However, when I configure the discovery service into Syncthing, I keep getting errors:

image

I think this should not be because a certain request header was not passed, it seems that the Syncthing client did not pass the certificate to the discovery service! Could you please tell me how I should handle this issue?

2

Oh, I forgot to mention, in the curl command, I passed the parameters: --cert new-client.crt --key new-client.key. This certificate was locally issued by me for testing whether the X-SSL-Cert header could be correctly passed.