I enabled TLS in the httpsd section and when I curl curl -s 'http://<fqdn in cert>:9182/api/v1/sd' | jq . I get a set of empty brackets []. I also enabled TLS for the Exporter section and curl -s 'https://<fqdn in cert>:13001/metrics' provides everything for that poller just fine. When I remove the TLS config from the httpsd section, all the poller metric endpoints populate the []. Am I missing something?
#No Output when using SSL cert for Admin
small prawn
solemn fiber
Hi @small prawn can you check your harvest config by running, bin/harvest doctor and then paste your config by running bin/harvest doctor --print and pasting the results?
small prawn
solemn fiber
thanks! That looks good. Can you share the admin node log file and one of the poller log files? They can be uploaded to https://upload.nabox.org/toti-xija-jeki
small prawn
Hmm, I don't see where the admin node log file is...I see the poller logs
solemn fiber
the admin node logs to stdout and will depend on how you started it. If you started it in a terminal, you should see the logs there. E.g.
small prawn
Uploaded...I am running harvest admin as a service
solemn fiber
thanks. did you create the certs via bin/harvest admin tls create server?
Looks like there is a problem with the certificate - from your poller log file
time=2025-09-02T18:09:05.461Z level=ERROR source=poller.go:1271 msg="Failed connecting to admin node" Poller=fas01-dt err="tls: failed to verify certificate: x509: cannot validate certificate for 0.0.0.
0 because it doesn't contain any IP SANs" admin=0.0.0.0:9182
small prawn
Ah, so I need to update the IP's to fqdn's in the poller configs?
I just realized I have FQDN's in the addr: config already
solemn fiber
this failure is when the poller attempts to talk to the admin node via the admin node's heartbeat URL so that TLS failed message is saying the poller attempts an HTTPS PUT to the admin node, but the TLS handshake fails. When you created the admin node certificates did you specify --ip or --dnsname or did you take the defaults?
Earlier you mentioned that you did curl -s 'http://<fqdn in cert>:9182/api/v1/sd' | jq . did you mean via https, i.e. curl -s 'https://<fqdn in cert>:9182/api/v1/sd' | jq .
small prawn
Oh, yes, sorry
solemn fiber
no worries
small prawn
My certs are signed
solemn fiber
did you create them via bin/harvest admin tls create server?
small prawn
No, Issuer: C = GB, ST = Greater Manchester, L = Salford, O = COMODO CA Limited, CN = COMODO RSA Organization Validation Secure Server CA
Is it the case where I should re issue the Cert and include the harvest servers IP in the SAN?
solemn fiber
Try changing this section of your harvest.yml to match the IP defined in your cert
