Sites look banned when they are not: the app browser's own challenge backs them off, and a stuck solver challenge reads as an outage #98
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
cmoriarty/sports-breaker#98
Loading…
Reference in a new issue
No description provided.
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?
Checked 2026-11-07 (8 h of container logs, 3.5 days of
/api/events, a live probe at 00:50 UTC) whether viewing problems come from sites or CDNs throttling or banning the app. They don't. There is no ban page anywhere in the solver log. The red rows on the Admin Sites table are the app's own doing, and two bugs make them look like bans.What happens
1. The app's own browser's challenge backs good sites off.
_read_player_pageopens a player page in the app's browser first. On the Cloudflare-gated sites (dudestream1.com, streameast.ga, tvsportslive.fr, mygoodstream.pw, iohit.st) Cloudflare challenges that browser every time, andread_stream_from_pagerecords the challenge (with its 403) against the host.after_challengehand-off from PR #82): dudestream1.com 11 of 12, streameast.ga 11 of 11, tvsportslive.fr 20 of 23. All 54 backoffs that day were followed within 3 s by a solver read of the same host.2. A challenge the solver can't clear reads as a solver outage.
SOLVE_TIMEOUT_SECONDS(90 s) equals themaxTimeoutthe app sends the solver (90 000 ms). The solver sends its 500 ("Error solving the challenge. Timeout after 90.0 seconds") at 90.1 s. httpx has given up about 50 ms earlier, so_fetch_clearanceraisesSolverUnreachable.What it costs
The idea
Ladder.fail, 10 min) already keeps it from being re-read. A challenge the solver can't clear still counts.past_backofflets the solver step through.maxTimeout, for example 100 s against 90 s, so the solver's own error arrives. A session that fails to clear a challenge is then discarded, the next read starts a fresh browser, and the challenge counts against the host and shows on the Sites table.Not throttling, for the record
Related: #78 (the embedsports.me frame those gated pages hold, which gave "no stream found" 17 times on 2026-11-07), PR #82, #91.
Deployed 2026-11-08 06:11Z in PR #111 (merge
a133e29, container 71367c5163eb); OpenSpec change archived inb4d5b94. Left open until a live night shows it: a gated player page (dudestream1, streameast, tvsportslive) read by the solver without backing its host off, a frame on the same host read past a backoff, and a hub challenge the solver can't clear counted against the host (the Sites strip turns amber) instead of logged as "not answering". Hosts that challenged the app's browser in the last 6 h are now read by the solver directly (a shield beside the host on the Sites list).Closed at the owner's word (2026-11-08): the fix is merged to develop in PR #111 (merge
a133e29) and deployed. A new issue will be opened if a problem shows up.