Skip to content

Conversation

@pictos
Copy link
Contributor

@pictos pictos commented Oct 23, 2025

While look into www I found that issue is related to google now require a POToken, or something like that, and while I didn't find a way to generate/grab/use this token I found a PR that provides a workaround for that issue. Looks like there's one client that doesn't need that token (yet).

The downside, that I found in my tests, is that the number of results for Muxed (video + audio) are reduced, but you know is better than nothing.

Related to #853

@Tyrrrz
Copy link
Owner

Tyrrrz commented Oct 24, 2025

Hi, thanks for the PR.

The downside, that I found in my tests, is that the number of results for Muxed (video + audio) are reduced, but you know is better than nothing.

Weren't we already not getting any muxed streams anyway, for a while?

@Tyrrrz Tyrrrz changed the title change the client Change the client Oct 24, 2025
@Tyrrrz Tyrrrz changed the title Change the client Change the client to avoid the 403 error Oct 24, 2025
@pictos pictos force-pushed the pj/workaround-for-403 branch from 767dccf to 72754c6 Compare October 24, 2025 20:09
@pictos pictos requested a review from Tyrrrz October 25, 2025 02:40
@Tyrrrz Tyrrrz merged commit 552c4db into Tyrrrz:master Oct 25, 2025
@Tyrrrz
Copy link
Owner

Tyrrrz commented Oct 25, 2025

Thanks a lot @pictos!

@pictos pictos deleted the pj/workaround-for-403 branch October 25, 2025 17:45
@YumYumFisch
Copy link

Awesome! Thank you very much for fixing the 403 Forbidden Error 🥳

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants