Skip to content
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

OK, but keyword is not in [] #4375

Closed
2 tasks done
vinznsk opened this issue Jan 16, 2024 · 4 comments
Closed
2 tasks done

OK, but keyword is not in [] #4375

vinznsk opened this issue Jan 16, 2024 · 4 comments
Labels
area:monitor Everything related to monitors cannot-reproduce help question Further information is requested Stale

Comments

@vinznsk
Copy link

vinznsk commented Jan 16, 2024

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

  • I checked and didn't find similar issue

🛡️ Security Policy

Description

I have 80 websites in Uptime Kuma, 2 websites recently started getting issues with keywords

2024-01-16-14-03-12

Websites are okay, UptimeRobot for example, doesn't show any issues, only uptime kuma. Also, I can open websites manually and there are no issues as well.

This doesn't happen with all website, just a few.

So, there are 2 issues I see:

  1. Error is not relevant to the reality, websites are okay, but Uptimie Kuma displays an error
  2. There are weird symbols in the response

P.S. I have Uptime Kuma installed on NAS and on a Ubuntu server, this issues happen on both of them.

👟 Reproduction steps

  1. Create a new alert
    • Type: Https - keyword
    • Friendly name - aronlawfirm.com
    • URL: https://www.aronlawfirm.com/
    • Interval: 60 sec
    • Retries: 3
    • Method: Get
    • Body Encoding: JSON

👀 Expected behavior

OK, but keyword is found

😓 Actual Behavior

200 - OK, but keyword is not in [����Q���F�f�h�,���������}��;����Y��A���8� ;�&]...]

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

Ubuntu 20.04

🌐 Browser

Google Chrome 120.0.6099.217

🐋 Docker Version

🟩 NodeJS Version

📝 Relevant log output

No response

@vinznsk vinznsk added the bug Something isn't working label Jan 16, 2024
@CommanderStorm
Copy link
Collaborator

image

image

@CommanderStorm
Copy link
Collaborator

Cannot really reproduce this one. I think some content for the body may be necessary given that you said to provide JSON encoding. (?)

@CommanderStorm CommanderStorm added help cannot-reproduce area:monitor Everything related to monitors and removed bug Something isn't working labels Jan 17, 2024
@vinznsk
Copy link
Author

vinznsk commented Jan 17, 2024

403 error is because of Sucuri Firewall (there are a several websites use Sucuri, but not all of them)

There were 3 websites we saw this issue today and now all of them work fine

image

I'll give more info as soon as it happens again. Thanks for checking this out.

@CommanderStorm CommanderStorm added the question Further information is requested label Jan 18, 2024
Copy link

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions github-actions bot added the Stale label Mar 18, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:monitor Everything related to monitors cannot-reproduce help question Further information is requested Stale
Projects
None yet
Development

No branches or pull requests

2 participants