Announcements widget: Increase the timeout

[oQJamesQo]

OPNSense version: OPNsense 24.7.12_2-amd64

Issue location: https://192.168.1.1/ui/core/dashboard

https://192.168.1.1/api/core/dashboard/product_info_feed takes around 10 seconds to complete on my router but the widget cancels the request at 5 seconds and retries 3 times.

Requesting a way to increase the timeout for this widget.

[OPNsense-bot]

Thank you for creating an issue.
Since the ticket doesn't seem to be using one of our templates, we're marking this issue as low priority until further notice.

For more information about the policies for this repository,
please read https://github.com/opnsense/core/blob/master/CONTRIBUTING.md for further details.

The easiest option to gain traction is to close this ticket and open a new one using one of our templates.

[Monviech]

Why does it take 10 seconds for you? Does your WAN connection experience a very high latency? Does your DNS resolution work slowly? IPv6 issues with eventual IPv4 fallback?

[oQJamesQo]

Sorry about the late reply.

My WAN connection doesn't seem to have issues which I use for work as well as playing games online. I am not sure about the IPv6 part. I will check and report back.

I am using pihole DNS and don't see any errors during the query. Most of the time resolution comes from the cache. Just refreshed the dashboard and this is what I see in pihole log.

Jan 30 18:28:41: query[A] forum.opnsense.org from 192.168.0.3
Jan 30 18:28:41: cached forum.opnsense.org is 89.149.225.137
Jan 30 18:28:46: query[AAAA] forum.opnsense.org from 192.168.0.3
Jan 30 18:28:46: cached forum.opnsense.org is 2001:1af8:2050:a001:1::1
Jan 30 18:28:46: query[A] forum.opnsense.org from 192.168.0.3
Jan 30 18:28:46: cached forum.opnsense.org is 89.149.225.137
Jan 30 18:28:51: query[AAAA] forum.opnsense.org from 192.168.0.3
Jan 30 18:28:51: cached forum.opnsense.org is 2001:1af8:2050:a001:1::1
Jan 30 18:28:53: query[A] forum.opnsense.org from 192.168.0.3
Jan 30 18:28:53: cached forum.opnsense.org is 89.149.225.137

[oQJamesQo]

Thank you. Looks like it was ipv6. I disabled ipv6 everywhere and it loaded immediately. Need to figure out a way to get ipv6 working. Shall I close the issue or is this still a useful request?

[fichtner]

@swhite2 it might be useful to have a longer timeout on special widget cases. our standard connection timeout is 30 seconds for firmware related fetch operations for example.