Actions in the body code #3571

Closed
opened 2026-02-28 03:34:00 -05:00 by deekerman · 4 comments
Owner

Originally created by @JPpascoal on GitHub (Aug 28, 2024).

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

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

I have a website that I'm monitoring with Uptime Kuma, and on one of the pages, I need to create a "floor." To do this, I have to click on two buttons first, but the problem is that everything happens on the same page. When I click on these buttons, one of them triggers a pop-up and not a different URL. In Kuma, I have a POST request to check if this "floor" has been created, but it always returns "request failed." If anyone can help, I'd appreciate it.

📝 Error Message(s) or Log

No response

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Windows 11

🌐 Browser

Google Chrome

🖥️ Deployment Environment

  • Runtime:
  • Database:
  • Filesystem used to store the database on:
  • number of monitors:
Originally created by @JPpascoal on GitHub (Aug 28, 2024). ### ⚠️ Please verify that this question has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I have a website that I'm monitoring with Uptime Kuma, and on one of the pages, I need to create a "floor." To do this, I have to click on two buttons first, but the problem is that everything happens on the same page. When I click on these buttons, one of them triggers a pop-up and not a different URL. In Kuma, I have a POST request to check if this "floor" has been created, but it always returns "request failed." If anyone can help, I'd appreciate it. ### 📝 Error Message(s) or Log _No response_ ### 🐻 Uptime-Kuma Version 1.23.13 ### 💻 Operating System and Arch Windows 11 ### 🌐 Browser Google Chrome ### 🖥️ Deployment Environment - Runtime: - Database: - Filesystem used to store the database on: - number of monitors:
Author
Owner

@CommanderStorm commented on GitHub (Aug 28, 2024):

You likely are not monitoring, but testing => consider using cypress, playwrigt or similar to build your testing script.
You can then string this together via the Push-minitors and a chron job.

Alternatively, look at https://changedetection.io

@CommanderStorm commented on GitHub (Aug 28, 2024): You likely are not monitoring, but testing => consider using cypress, playwrigt or similar to build your testing script. You can then string this together via the `Push`-minitors and a chron job. Alternatively, look at https://changedetection.io
Author
Owner

@JPpascoal commented on GitHub (Aug 29, 2024):

I am trying to monitor it, but i can't because its a pop up in the page, and not an URL, is there something i can do?

@JPpascoal commented on GitHub (Aug 29, 2024): I am trying to monitor it, but i can't because its a pop up in the page, and not an URL, is there something i can do?
Author
Owner

@CommanderStorm commented on GitHub (Aug 29, 2024):

Yes, you could to what I suggested?
Am I missing something?
Examples how to use the push monitor are avaliable here: https://github.com/louislam/uptime-kuma/tree/master/extra/push-examples

consider using cypress, playwrigt or similar to build your testing script.
You can then string this together via the Push-minitors and a chron job.

Alternatively, look at https://changedetection.io

@CommanderStorm commented on GitHub (Aug 29, 2024): Yes, you could to what I suggested? Am I missing something? Examples how to use the push monitor are avaliable here: https://github.com/louislam/uptime-kuma/tree/master/extra/push-examples > consider using cypress, playwrigt or similar to build your testing script. You can then string this together via the `Push`-minitors and a chron job. > > Alternatively, look at https://changedetection.io
Author
Owner

@github-actions[bot] commented on GitHub (Oct 28, 2024):

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[bot] commented on GitHub (Oct 28, 2024): 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.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3571
No description provided.