Telemetry widget fails to load on dashboard

[allenlook]

As of this morning the widget data is populated again.

[MaxMax99]

Hi,

The widget still dosen't load.

What about you guys?

[franco]

Haven't updated the widget yet, but you can always inspect he API response if you need the information now.


Cheers,
Franco

[allenlook]

Widget is still OK for me.

[franco]

Here's the discussed change for 25.7.5:

https://github.com/opnsense/plugins/commit/a75a87d0b

That should show any type of status returned by the server.


Cheers,
Franco

[MaxMax99]

Hi,

The widget now works proprely, thank you :)

[BrandyWine]

In my suricata logs I see err 403's for heartbeat.py and other URI's for getting rules.
I am v25.7.3_7

Does the update to 25.7.5 fix all that (discussion has been about the widget). Am I right when I say the widget wasn't really the problem, but the plugin was. Is 25.7.5 a dependency for plugin v1.8 ?

These 403's keep showing up in system log file
<11>1 2025-10-09T03:12:49+00:00 Rice.localdomain send_heartbeat.py 39534 - [meta sequenceId="1"] unexpected result from https://opnsense.emergingthreats.net/api/v1/telemetry (http_code 403)

My widget still broken

[franco]

> Does the update to 25.7.5 fix all that (discussion has been about the widget).

No, the fix in 25.7.5 doesn't deal with invalid responses and I would consider a 403 a proper failed to load widget error in this case.


Cheers,
Franco

[BrandyWine]

I currently removed the widget, and still see errors in log file

<11>1 2025-10-09T12:16:29+00:00 Rice.localdomain rule-updater.py 62960 - [meta sequenceId="116"] download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/version (http_code: 403)

Any call out to thst url (from the fw for suricata stuff) always gets 403.

403's are "not authorized" err, so maybe an issue with API key?

[franco]

Could be, but wouldn't know why their server returned that.


Cheers,
Franco

[MaxMax99]

Yes, maybe. Check API key.

I currently removed the widget, and still see errors in log file

<11>1 2025-10-09T12:16:29+00:00 Rice.localdomain rule-updater.py 62960 - [meta sequenceId="116"] download failed for https://opnsense.emergingthreats.net/api/v1/ruleset/version (http_code: 403)

Any call out to thst url (from the fw for suricata stuff) always gets 403.

403's are "not authorized" err, so maybe an issue with API key?

[BrandyWine]

Yes, maybe. Check API key.

With the 403's I suspect key issue, but it was working and now it's not, so if that's the case then that's odd, would seem my registered sensor was revoked.
From OPN github page (https://github.com/opnsense/docs/blob/master/source/manual/etpro_telemetry.rst) it's not clear to me how sensor registration is managed, but does seem clear the keys are generated & registered from OPNsense acct at proofpoint.