Monitor showing offline but its online #1848

Kaseax · 2022-06-28T14:29:35Z

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

I have the problem, that all of my monitors except 1 showing as offline. i can reach the website normally.
Can someone help me by that?

One Monitor showing "error request aborted"

The other two showing "timeout of 48000ms exceeded"

🐻 Uptime-Kuma Version

1.16.1

💻 Operating System and Arch

Debian 10 x86_64

🌐 Browser

Microsoft Edge 103.0.1264.37

🐋 Docker Version

20.10.17

🟩 NodeJS Version

No response

GVALFER · 2022-06-28T14:31:31Z

Check if you can ping it directly from your server via ssh

Kaseax · 2022-06-28T14:32:41Z

You mean with the ping command? if yes, yes. i can ping every server

dariusdumitru · 2022-06-29T06:45:19Z

I got the same exact problem every morning at 5-6 AM for an hour. It says that it's down, but it's not. With the same error "timeout of 48000ms exceeded". Usually there are 2 websites, but it happens to be only 1 or 3 sometimes. I've increased the Heartbeat Interval and Retries, but no luck. Anyone can help?

d-delaey · 2022-06-29T07:29:20Z

I got the same exact problem every morning at 5-6 AM for an hour. It says that it's down, but it's not. With the same error "timeout of 48000ms exceeded". Usually there are 2 websites, but it happens to be only 1 or 3 sometimes. I've increased the Heartbeat Interval and Retries, but no luck. Anyone can help?

We got the same thing last night for maybe 40-50 Websites.

Kaseax · 2022-06-29T11:29:37Z

With me it is not only over night but permanent.

Kaseax · 2022-07-01T08:35:15Z

Now my Discord-Webhook showing sometimes, that the Services are online but then it says there are offline.

Nuklon · 2022-07-05T08:45:52Z

Same issue here, see: #1621

kfra71 · 2022-08-02T07:26:03Z

Same issue here, suddenly we are getting "timeout of 48000ms exceeded" on most of the checks.

Anyone has any clue?

louislam · 2022-08-02T10:18:30Z

Same issue here, suddenly we are getting "timeout of 48000ms exceeded" on most of the checks.

Anyone has any clue?

This may help:
https://github.com/louislam/uptime-kuma/wiki/Troubleshooting

kfra71 · 2022-08-02T11:12:45Z

Hi I have tried to run the cmd without apparently any issue. Best regards, Francesco. ***@***.*** ~]$ curl https://google.com <HTML><HEAD><meta http-equiv="content-type" content="text/html;charset=utf-8"> <TITLE>301 Moved</TITLE></HEAD><BODY> <H1>301 Moved</H1> The document has moved <A HREF="https://www.google.com/">here</A>. </BODY></HTML> ***@***.*** ~]$ ping google.com PING google.com (172.217.168.206) 56(84) bytes of data. 64 bytes from ams16s32-in-f14.1e100.net (172.217.168.206): icmp_seq=1 ttl=53 time=2.77 ms 64 bytes from ams16s32-in-f14.1e100.net (172.217.168.206): icmp_seq=2 ttl=53 time=2.52 ms 64 bytes from ams16s32-in-f14.1e100.net (172.217.168.206): icmp_seq=3 ttl=53 time=2.80 ms 64 bytes from ams16s32-in-f14.1e100.net (172.217.168.206): icmp_seq=4 ttl=53 time=2.36 ms 64 bytes from ams16s32-in-f14.1e100.net (172.217.168.206): icmp_seq=5 ttl=53 time=2.36 ms 64 bytes from ams16s32-in-f14.1e100.net (172.217.168.206): icmp_seq=6 ttl=53 time=2.42 ms 64 bytes from ams16s32-in-f14.1e100.net (172.217.168.206): icmp_seq=7 ttl=53 time=2.63 ms 64 bytes from ams16s32-in-f14.1e100.net (172.217.168.206): icmp_seq=8 ttl=53 time=2.67 ms 64 bytes from ams16s32-in-f14.1e100.net (172.217.168.206): icmp_seq=9 ttl=53 time=2.33 ms ^C

…

On 2 Aug 2022, at 12:18, Louis Lam ***@***.***> wrote: Same issue here, suddenly we are getting "timeout of 48000ms exceeded" on most of the checks. Anyone has any clue? This may help: https://github.com/louislam/uptime-kuma/wiki/Troubleshooting <https://github.com/louislam/uptime-kuma/wiki/Troubleshooting> — Reply to this email directly, view it on GitHub <#1848 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFCDTMMWIQ2MPJZW2KPTRX3VXDYYDANCNFSM52CMU2PA>. You are receiving this because you commented.

Nuklon · 2022-08-02T11:51:38Z

Yeah, that works for me as well. It's really that Uptime Kuma gets bogged down, and it happens more frequently when the container is running for a longer period of time. I've not found anything useful in the logs either, it just times out.

Nuklon · 2022-08-02T11:56:49Z

30s monitor (both monitors have the same settings and site, except for the interval):

1m monitor:

guydeschepper · 2022-09-22T10:07:08Z

Same issue here.
When I try to ping the url from within the docker container, as suggested here, I also do get a timeout.

BUT... the same website can be reached and pinged from other systems AND I can still ping other monitored websites from within the Uptime Kuma docker container, so it's not a general networking issue with the container / server / hosting.

So it seems something is getting bogged down in Uptime Kuma itself.

Note
Most of our monitored websites are behind Cloudflare, but some are not.
And until now I only experienced the issue with websites that are not behind Cloudflare.
Though not all those "non-cloudflare" websites are affected at the same time.
At the moment 2 of the non-cloudflare websites are affected, but several weeks ago we had the same issue with one of those 2 websites (and another one), but not the other.

We also see different errors prior to the timeout issues:

140059089770432:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:677

and

getaddrinfo EAI_AGAIN <hostname>

d-delaey · 2022-09-26T08:59:08Z

Same issue here. When I try to ping the url from within the docker container, as suggested here, I also do get a timeout.

BUT... the same website can be reached and pinged from other systems AND I can still ping other monitored websites from within the Uptime Kuma docker container, so it's not a general networking issue with the container / server / hosting.

So it seems something is getting bogged down in Uptime Kuma itself.

Note Most of our monitored websites are behind Cloudflare, but some are not. And until now I only experienced the issue with websites that are not behind Cloudflare. Though not all those "non-cloudflare" websites are affected at the same time. At the moment 2 of the non-cloudflare websites are affected, but several weeks ago we had the same issue with one of those 2 websites (and another one), but not the other.

We also see different errors prior to the timeout issues:

140059089770432:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:677

and

getaddrinfo EAI_AGAIN <hostname>

Hey, we "fixed" that issue by simply not using docker. But sometimes we are still getting the timeout error but not as often as using docker.

guydeschepper · 2022-09-26T09:48:21Z

@d-delaey thanks for the suggestion, but we're running Uptime Kuma as part of a dockerized environment, so not using docker is not an option for us in this case.

github-actions · 2022-12-25T12:00:31Z

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

guydeschepper · 2022-12-25T17:29:30Z

Please don't close this issue as it is still not fixed!

louislam · 2022-12-26T12:48:17Z

Same issue here. When I try to ping the url from within the docker container, as suggested here, I also do get a timeout.

BUT... the same website can be reached and pinged from other systems AND I can still ping other monitored websites from within the Uptime Kuma docker container, so it's not a general networking issue with the container / server / hosting.

So it seems something is getting bogged down in Uptime Kuma itself.

Note Most of our monitored websites are behind Cloudflare, but some are not. And until now I only experienced the issue with websites that are not behind Cloudflare. Though not all those "non-cloudflare" websites are affected at the same time. At the moment 2 of the non-cloudflare websites are affected, but several weeks ago we had the same issue with one of those 2 websites (and another one), but not the other.

We also see different errors prior to the timeout issues:

140059089770432:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:677

and

getaddrinfo EAI_AGAIN <hostname>

Make sure you are not using Alpine based image.

For SSL error, please double check http:// vs https://

guydeschepper · 2022-12-26T15:44:28Z

Same issue here. When I try to ping the url from within the docker container, as suggested here, I also do get a timeout.
BUT... the same website can be reached and pinged from other systems AND I can still ping other monitored websites from within the Uptime Kuma docker container, so it's not a general networking issue with the container / server / hosting.
So it seems something is getting bogged down in Uptime Kuma itself.
Note Most of our monitored websites are behind Cloudflare, but some are not. And until now I only experienced the issue with websites that are not behind Cloudflare. Though not all those "non-cloudflare" websites are affected at the same time. At the moment 2 of the non-cloudflare websites are affected, but several weeks ago we had the same issue with one of those 2 websites (and another one), but not the other.
We also see different errors prior to the timeout issues:
140059089770432:error:1408F119:SSL routines:ssl3_get_record:decryption failed or bad record mac:../deps/openssl/openssl/ssl/record/ssl3_record.c:677
and
getaddrinfo EAI_AGAIN <hostname>

Make sure you are not using Alpine based image.

I'm not since I'm running Uptime Kuma with Cloudron, which uses Ubuntu based docker images

For SSL error, please double check http:// vs https://

All sites in Uptime Kuma are configured with https, so there shoudn't be any reason for Uptime Kuma trying to access the sites over http.

mrafols · 2023-01-24T08:00:17Z

For me still happening

d-delaey · 2023-01-24T08:59:19Z

For me still happening

Yes it still happening to me aswell

xeruf · 2023-02-01T08:03:38Z

Getting this error when trying to send a webhook, as in #1697, running via pm2

webysther · 2023-02-01T21:07:31Z

Start to happen to me after update the docker image.

webysther · 2023-02-01T21:12:30Z

Same issue here, suddenly we are getting "timeout of 48000ms exceeded" on most of the checks.
Anyone has any clue?

This may help: https://github.com/louislam/uptime-kuma/wiki/Troubleshooting

No curl installed in docker

webysther · 2023-02-01T21:17:26Z

After stop docker, pull new image and start docker.

webysther · 2023-02-01T21:22:54Z

webysther · 2023-02-01T21:24:15Z

webysther · 2023-02-01T21:24:55Z

ping and curl working from inside the container, nothing is working from this.

alwynispat · 2023-03-19T12:36:41Z

same here using the latest image.
https://github.com/louislam/uptime-kuma/wiki/Troubleshooting
using the troubleshooting guide above, the container was able to curl and ping the urls, however, the urls still appear as down in kuma

m-primo · 2023-03-22T22:38:03Z

I have the same issue for months.. At first I thought this issue from my VPS provider, but after I had big fights with multiple VPS providers, I found out it's only happening from Uptime Kuma.

I think I'll just look for another tool and apologize to the VPS providers!

XtremeOwnageDotCom · 2023-03-27T21:20:42Z

Just a ping- its still a problem.

But, container logs, do tell me to report it. So. Here it is.

Deleting and recreating the monitor did nothing to help.

However, after deleting the pod, and letting it recreate, monitor did start working.

ofifoto · 2023-05-01T23:37:20Z

related: #2346

github-actions · 2023-07-31T00:00:29Z

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

ofifoto · 2023-07-31T00:02:11Z

stalebot, really?

CommanderStorm · 2023-07-31T00:23:13Z

stalebot, really?

Stalebot is active on all issues using the help template.
=> Closing stale help requests is by design because often people don't answer or issues are not reproduce or we fix things in further releases but forget to close them leading to immortal zombies.

Until now this issue has not really provided a minimally reproducible example (see https://stackoverflow.com/help/minimal-reproducible-example)
If somebody provides such an example I can have a look, but currently this issue doesn't really give enough context to debug against.
There are multiple factors (number of monitors, capacity of the host, montored system) which can lead to timeouts.

michel-thomas · 2023-08-03T08:13:39Z

I had the problem yesterday, and finally found what occurs…

After a maintenance reboot from our provider, IPv4 remains the same, but IPv6 changed. I would have never seen this change if uptime kuma didn't alert.

I don't know why yet, but my uptime kuma check https services via IPv6 while my desktop ISP still only works with IPv4.
Updating my DNS with the new IPv6 solve the problem.

github-actions · 2023-11-01T12:00:30Z

We are clearing up our old issues and your ticket has been open for 3 months with no activity. Remove stale label or comment or this will be closed in 2 days.

github-actions · 2023-11-03T18:00:30Z

This issue was closed because it has been stalled for 2 days with no activity.

pixelbart · 2024-07-08T15:27:15Z

Same issues here

fantasticrabbit · 2024-10-15T04:28:53Z

Same issue here. Was stable for 16-7 months using Node+PM2, switching to Docker was stable for 2 months and then started showing all sites down every 4-10 hours. Was not able to find anything in the container logs to troubleshoot. We're planning to switch back to just running the Node app.

Kaseax added the help label Jun 28, 2022

github-actions bot added the Stale label Dec 25, 2022

github-actions bot removed the Stale label Dec 25, 2022

thefourcraft mentioned this issue Mar 23, 2023

[Snyk] Upgrade protobufjs from 7.1.2 to 7.2.2 IMS-Network/uptime-kuma#43

Merged

snyk-bot mentioned this issue Apr 1, 2023

[Snyk] Upgrade protobufjs from 7.1.2 to 7.2.2 othmaneelmhassani/uptime-kuma#5

Open

thefourcraft mentioned this issue Jul 6, 2023

[Snyk] Security upgrade protobufjs from 7.1.2 to 7.2.4 IMS-Network/uptime-kuma#54

Closed

othmaneelmhassani mentioned this issue Jul 7, 2023

[Snyk] Security upgrade protobufjs from 7.1.2 to 7.2.4 othmaneelmhassani/uptime-kuma#22

Open

GTVolk mentioned this issue Jul 7, 2023

[Snyk] Fix for 2 vulnerabilities DevVault/uptime-kuma#18

Open

github-actions bot added the Stale label Jul 31, 2023

github-actions bot removed the Stale label Jul 31, 2023

github-actions bot added the Stale label Nov 1, 2023

github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 3, 2023

Monitor showing offline but its online #1848

Monitor showing offline but its online #1848

Comments

Kaseax commented Jun 28, 2022 • edited Loading

⚠️ Please verify that this bug has NOT been raised before.

🛡️ Security Policy

📝 Describe your problem

🐻 Uptime-Kuma Version

💻 Operating System and Arch

🌐 Browser

🐋 Docker Version

🟩 NodeJS Version

GVALFER commented Jun 28, 2022

Kaseax commented Jun 28, 2022

dariusdumitru commented Jun 29, 2022

d-delaey commented Jun 29, 2022

Kaseax commented Jun 29, 2022

Kaseax commented Jul 1, 2022

Nuklon commented Jul 5, 2022

kfra71 commented Aug 2, 2022

louislam commented Aug 2, 2022

kfra71 commented Aug 2, 2022 via email

Nuklon commented Aug 2, 2022

Nuklon commented Aug 2, 2022

guydeschepper commented Sep 22, 2022

d-delaey commented Sep 26, 2022

guydeschepper commented Sep 26, 2022

github-actions bot commented Dec 25, 2022

guydeschepper commented Dec 25, 2022

louislam commented Dec 26, 2022

guydeschepper commented Dec 26, 2022

mrafols commented Jan 24, 2023

d-delaey commented Jan 24, 2023 • edited Loading

xeruf commented Feb 1, 2023

webysther commented Feb 1, 2023

webysther commented Feb 1, 2023

webysther commented Feb 1, 2023 • edited Loading

webysther commented Feb 1, 2023

webysther commented Feb 1, 2023

webysther commented Feb 1, 2023

alwynispat commented Mar 19, 2023 • edited Loading

m-primo commented Mar 22, 2023

XtremeOwnageDotCom commented Mar 27, 2023

ofifoto commented May 1, 2023

github-actions bot commented Jul 31, 2023

ofifoto commented Jul 31, 2023

CommanderStorm commented Jul 31, 2023 • edited Loading

michel-thomas commented Aug 3, 2023

github-actions bot commented Nov 1, 2023

github-actions bot commented Nov 3, 2023

pixelbart commented Jul 8, 2024

fantasticrabbit commented Oct 15, 2024

Kaseax commented Jun 28, 2022 •

edited

Loading

d-delaey commented Jan 24, 2023 •

edited

Loading

webysther commented Feb 1, 2023 •

edited

Loading

alwynispat commented Mar 19, 2023 •

edited

Loading

CommanderStorm commented Jul 31, 2023 •

edited

Loading