Someone from your team (maybe you) replied to my email that he’s investigating the API.
Having the same issue with a new token generated today then forcing a rule update eliminates the possibility of it being disabled.
A new problem with opnsense telemetry came up since yesterday around that time : 2025-09-17T20:16:03 (GMT+2).
Since then, heartbeats systematically fail every hour and telemetry ruleset download fails.
send_heartbeat.py connection error sending heartbeat to https://opnsense.emergingthreats.net/api/v1/telemetry
rule-updater.py
download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/version (HTTPSConnectionPool(host=‘opnsense.emergingthreats.net’, port=443): Max retries exceeded with url: /api/v1/ruleset/version (Caused by SSLError(SSLCertVerificationError(1, ‘[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1016)’))))
The problem is only with telemetry. ET open ruleset updates fine :
rule-updater.py download completed for https://rules.emergingthreats.net/open/suricata-7.0/emerging.rules.tar.gz
rule-updater.py version response for https://rules.emergingthreats.net/open/suricata-7.0/version.txt : 11018
Same,
I addressed it here.
Might be a Sectigo cert trust issue.
1 Like
All back to normal now. Thanks for the quick fix.
1 Like
Thanks for the feedback!