-
-
Notifications
You must be signed in to change notification settings - Fork 4.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SSL error which occurs pretty often causing many false alerts. #4731
Comments
And this is an less frequent but occuring error too:
|
Regarding the ssl eror: This sounds pretty similar to #4520 |
Regarding
This error message means that the dns request has failed. Node.js itself doesn't perform any DNS caching, it delegates everything DNS related to the OS.
Increasing the retry setting is also a valid approach to solve this in both cases. |
Thanks for your responses! How can I check the ping-poinging between certs and how can I adjust these DNS settings if I run it Proxmox using the HA LXC container? |
Pleaese see the comment I hinted at above:
You can adjust the DNS settings where you set up your DNS routes => at your DNS-Provider. In case by the comment about |
📑 I have found these related issues/pull requests
Related to #2872
🛡️ Security Policy
Description
Hey there, thanks for crafting such an awesome application! Currently, I'm hosting it on HomeAssistant within my local environment, alongside a plethora of other services. However, I've encountered an issue with SSL errors popping up in Uptime Kuma for my public HTTPS sites.
Just a heads-up: I've tried replicating the issue across various browsers without success. The sites are functioning smoothly, and their SSL certificates are both valid and operational. These sites are hosted on CloudFlare. The hiccup is that Uptime Kuma throws SSL errors and flags the sites as down, despite having "ignore SSL errors" checked(and of course, despite having valid certs xD).
Now, to cut to the chase, I've set up Discord webhooks to receive notifications. Here's an example from a notification I received regarding an SSL error:
A minute later, during the next check, everything is back to normal, and the service is reported as online again.
This issue doesn't show up consistently but it does so frequently. Is there a known fix for this, or could the developers take a look at it? Really annoying to get spammed with downtime notifications if they're actually up.
👟 Reproduction steps
Add an HTTPS site, give it some time and get SSL errors.
👀 Expected behavior
It shouldn't throw SSL errors.
😓 Actual Behavior
It threw SSL errors.
🐻 Uptime-Kuma Version
1.23.13
💻 Operating System and Arch
HomeAssistant,
🌐 Browser
Chrome on my Windows PC.
🖥️ Deployment Environment
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: