Bug on Browser Engine: browser.newContext: Target page, context or browser has been closed.

[calebcall]

⚠️ 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

Description

I get this error with the browser engine checks:

browser.newContext: Target page, context or browser has been closed. 

The Checks using the Browser Engine work great for an initial period of time and then all of the checks using the browser engine start to fail at the same time and never recover.

👟 Reproduction steps

Configure Browser Engine monitor

👀 Expected behavior

To continue to work

😓 Actual Behavior

return the error :

browser.newContext: Target page, context or browser has been closed

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

Debian 12.4

🌐 Browser

Brave v1.61.116

🐋 Docker Version

K8s 1.27.7

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[CommanderStorm]

• What exactly is returning this log message? the browser console or the node/docker log?
• To be able to reproduce this: what website are you monitoring? Is this reproducible?

[calebcall]

I'm seeing this error in Kuma. The services are internal services (Jellyseerr, Radarr, Sonarr, Sabnzbd, and Scrypted)

This shot shows they all went down in the same check period.

Prior to that, they had all been up for about 6.5 hours when they all failed in the same way.

[CommanderStorm]

Thanks ^^
We might have a race condition in the playwright code as in https://stackoverflow.com/questions/61933492/playwright-error-target-closed-after-navigation

Given that this does not seem very widespread/reprducible I am not going to prioritse reproducing/debugging this (I am currently quite under the water Uni-wise).
If somebody else wants to give this a shot, here is our contribution guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

[chakflying]

Added a simple fix in #4417 but I'm not sure if this is the root cause, you can help by testing it if you're interested.

https://github.com/louislam/uptime-kuma/wiki/Test-Pull-Requests

[CommanderStorm]

@calebcall
I think this issue was fixed by #4417
Given that we cannot reproduce the issue, testing said PR would be greatly appreaciated ^^

I am going to assume that said PR works and does not contain bugs => closing as resolved