You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following up on #615, I just had the following error in the docker logs:
π Successfully pinged Uptime Kuma
β° Checking the IP addresses in about 5m0s . . .
π Failed to send HTTP(S) request to "https://1.1.1.1/cdn-cgi/trace": context deadline exceeded
π Failed to detect the IPv4 address
π Successfully pinged Uptime Kuma
β° Checking the IP addresses in about 4m55s . . .
π Detected the IPv4 address: 71.x.y.86
π€· The A records of "ddns.domain.com" are already up to date
π Successfully pinged Uptime Kuma
β° Checking the IP addresses in about 5m0s . . .
Which is totally fine (I rebooted my router, so the container was running, but it couldn't reach the internet for that one interval).
However this is what Uptime Kuma showed:
(So it sent an OK instead of the actual issue of "context deadline exceeded" (or request timed out, or whatever makes sense as error message))
The text was updated successfully, but these errors were encountered:
Yes I'm running 1.11.0. And the problem is mostly fixed. It works for other errors. Just this one doesn't have an appropriate Message string when reporting a down condition.
favonia
changed the title
Feature request: Monitoring fix
Sometimse the updator sends "OK" when it's failing.
Nov 27, 2023
favonia
changed the title
Sometimse the updator sends "OK" when it's failing.
Sometimse the updator sends the message "OK" for failing messages
Nov 27, 2023
favonia
changed the title
Sometimse the updator sends the message "OK" for failing messages
Sometimse the updator sends the message "OK" when failing
Nov 27, 2023
@JvdMaat Hi, I wonder how annoying this bug is to you? I'm in the middle of (extremely slowly) adding shoutrrr (see #632) and I prefer not to release a version with lots of non-functional code. However, the non-working code does not affect other functionalities and nothing prevents me from releasing a bugfix, either.
This bug has little to no impact on me. Just a cleanup of missing error messages as far as I'm concerned. File it with nice to have.
JvdMaat
changed the title
Sometimse the updator sends the message "OK" when failing
Sometimes the updater sends the message "OK" when failing
Nov 30, 2023
Following up on #615, I just had the following error in the docker logs:
Which is totally fine (I rebooted my router, so the container was running, but it couldn't reach the internet for that one interval).
However this is what Uptime Kuma showed:
(So it sent an OK instead of the actual issue of "context deadline exceeded" (or request timed out, or whatever makes sense as error message))
The text was updated successfully, but these errors were encountered: