ExtremeFiretop
Very Senior Member
We don't use --connect-timeout or --max-time on our curl requests.
So a single attempt can wait as long as curl, the system, and the network stack allow, and we have never had any related issues.
This BTW was also mentioned by @dave14305 here that a timeout of 3 is too short:
ModSyslogUI v1.1.0 [28-Feb-2026] - add-on providing System Log page UI filtering capabilities
That 5.23s explains the problem, especially when curl is using a 3 second timeout. Why do you think Google DNS is so slow? Do you live in a remote area? No idea why it's slow. Recently upgraded to T-Mobile Fiber at 2g / 2g. There were a few setup issues. Requested a static IP but speeds...
www.snbforums.com
I think it's well agreed upon with most script devs that 3 is too short, you can either extend the timeout or remove the parameter if it's causing issues.
Last edited:
