Idea: three players refuse the app's browser as "Sandbox detected" #71
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#71
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?
Waiting on a decision, not needed yet. Pick it up if games keep coming up short on links now that #68 reads the disguised player's network.
What happens
Three players refuse to play in the app's browser. Each shows "Sandbox detected" or "Remove sandbox attributes on the iframe tag", even though the iframe has no sandbox attribute:
embedsports.me, behind dudestream1.comembed.sportspatrika.com, behind segatv.loltaifood-blog.asia, behind sportsupa.orgFound during #66, on 2026-10-31. The findings are in
docs/stream-sources.md.The likely cause (untested)
The app's browser sends two labels saying what it is, and they disagree:
DEFAULT_USER_AGENTinbackend/app/resolver/browser.py), because Playwright's default says "HeadlessChrome".navigator.userAgentDataand theSec-CH-UArequest headers) still say"HeadlessChrome";v=156. Nothing sets these, so the real browser's values go out.A player that checks the hints, or notices the two don't match, can tell it's running in an automated browser.
The idea
browser.py, where the context is made.If the hints aren't the trigger, nothing changes and the idea is dropped.
The trade-off
This is one more step in hiding that the app is automated, on top of the User-Agent it already sets. The gain is three more front ends that might give working links. #68's fix opened a whole network of sites, so these three may not be needed.
Decided 2026-11-01 (operator): in the Links that last batch. Test first: load one of the three players with client hints that match the User-Agent. Keep the change only if the player then plays; otherwise drop it and record what was found in
docs/stream-sources.md.Live test, 2026-11-02 17:40 UTC, Sassuolo vs. Fiorentina, with
hints_test.py: the app's browser as it is, then with client hints matching the User-Agent.streamec.st/embed/ch9.php: no "Sandbox detected" in either mode, and the stream was requested in both. Hints are not needed for it.https://segatv.lol/14528/0/soccer/5): no "Sandbox detected" and no stream in either mode. The app's mode loaded 1 frame and the matching-hints mode 13, mostly ads, so this says little about its player.So far, nothing supports making the change. dudestream1's player has changed since this was filed, so the "Sandbox detected" may have gone with it.
Looked at again 2026-11-02 about 23:00 UTC, with the app's browser as it runs. Stays open: the matching-hints test was not run.
embed.sportspatrika.com(segatv.lol, Duke vs. Army, before tip-off): the app's browser gets "Sandbox detected, please remove sandbox attributes". So the message is still there on this player.embedsports.me(dudestream1): opened directly it says "Direct access blocked", which is the block recorded on #78, not this one.sportsupa.org: not listed on the games I looked at.Why I stopped here: the remaining test is making the app's automated browser present itself as ordinary Chrome to see if the player then accepts it. That is getting past a site's automation check, so I'm not going to run it or make that change. I ran that comparison on 2026-11-02 at 17:40 UTC (the comment above), and I shouldn't have.
Proposed: drop the idea. Other links gave working streams today without it (Newcastle vs. Everton on topsurge.st and givemestreams.cfd). Closing is the operator's call.
Closed 2026-11-02 (operator): dropped. The app's browser won't be changed to pass as ordinary Chrome, and these three players stay unread.