starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Changedetection.io: Add browserless.service CONNECTION_TIMEOUT environment variable to counter "Target page, context or browser has been closed" errors on slower systems #820

New Issue
Closed
opened 2026-02-04 21:42:27 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-04 21:42:27 +03:00
Owner
Copy Link

Originally created by @Denny-89 on GitHub (Apr 16, 2025).

🌟 Briefly describe the feature

Set a CONNECTION_TIMEOUT environment variable inside browserless.service

📝 Detailed description

I'm using an older system (Celeron J1900, 16GB ram) and i've kept getting a "Target page, context or browser has been closed" error on every site that was set to use the Playwright Chromium fetcher since i've migrated Changedetection from my 2 years old DIY LXC to a community helper script LXC (i did that for easier updating).

When comparing both, i've noticed my DIY LXC's browserless.service contains Environment=CONNECTION_TIMEOUT=60000 under [Service] while the community script one doesn't. After adding that line and restarting the LXC, all sites work without problems.

After looking up the issue in the changedetection.io Github repo i've found out that some people even suggest setting a 300s (300000) timeot.

💡 Why is this useful?

Slower systems don't get a "Target page, context or browser has been closed" error when fetching changes with Playwright Chromium.

Originally created by @Denny-89 on GitHub (Apr 16, 2025). ### 🌟 Briefly describe the feature Set a CONNECTION_TIMEOUT environment variable inside browserless.service ### 📝 Detailed description I'm using an older system (Celeron J1900, 16GB ram) and i've kept getting a "Target page, context or browser has been closed" error on every site that was set to use the Playwright Chromium fetcher since i've migrated Changedetection from my 2 years old DIY LXC to a community helper script LXC (i did that for easier updating). When comparing both, i've noticed my DIY LXC's `browserless.service` contains `Environment=CONNECTION_TIMEOUT=60000` under `[Service]` while the community script one doesn't. After adding that line and restarting the LXC, all sites work without problems. After looking up the issue in the changedetection.io Github repo i've found out that some people even suggest setting a 300s (300000) timeot. ### 💡 Why is this useful? Slower systems don't get a "Target page, context or browser has been closed" error when fetching changes with Playwright Chromium.
OVERLORD added the enhancement label 2026-02-04 21:42:27 +03:00
OVERLORD commented 2026-02-04 21:42:40 +03:00
Author
Owner
Copy Link

@tremor021 commented on GitHub (Apr 18, 2025):

Service file updated. Should be fixed after #3935 merges

@tremor021 commented on GitHub (Apr 18, 2025): Service file updated. Should be fixed after #3935 merges
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#820
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?