v13.0.0 (403)

[Nansess]

Steps to reproduce

I've noticed that all returned googlevideo URLs result in a 403 error. While this may seem similar to YouTube IP bans, this issue is not caused by that. Although IP Blocks can also lead to 403 errors, in this case, the problem prob is related to deciphering issue.

I first encountered this issue in my own custom library and later confirmed that youtube.js was also affected. To prevent unnecessary confusion, I wanted to report this

Cause of the Issue

The problem occurs when YouTube serves the player script:

/c8dbda2a/

When this specific script is encountered, all googlevideo links end up in a 403 state, likely due to a short-circuit possibly.

To temporarily mitigate this in my personal library, I hardcoded the last known working player script. /7795af42/ This is not a REAL fix, and I don't recommend it. I'm mentioning it as further evidence that the issue is not an IP Block.

I did this as a temporary fix since I was away from my work environment and couldn't properly address the root cause.

YouTube currently serves both player scripts, /7795af42/ and /c8dbda2a/, but /c8dbda2a/ appears more frequently. This results in inconsistent behavior, where some URLS succeed while others 403.

Just wanted to make it known.

Failure Logs

[test][Player]: No cached player found. Downloading new player from /c8dbda2a/player_ias.vflset/en_US/base.js.
[test][Player]: Obtained signature timestamp (20138) and algorithms for signature deciphering.
[test][Player]: Transformed signature from AJfQdSswRAIgSEhxouyDat8QXsh4_SDT4LW06kHhAfGTik_ygVQOMooCIDb90zT0fAlUTpDy6oD2nI9SEPzKrKIsVxZiVlaDbYr55 to AJfQdSswRAIgSEhxouyDat8QXsh4_SDT4LW06kHhAfGTik_ygVQOMooCIDb90zT0fAlUTpDy6oD2nI9SEPzKrKIsVxZiVlaDbYr5.
[test][Player]: Transformed n signature from ySeXoBVCfs2WQBI to jfVyr8x8AOQqp0B1eL-_w8_ySeXoBVCfs2WQBI.

[test][Player]: Deciphered URL: https://rr4---sn-p5qlsn7s.googlevideo.com/...
[test][Validation]: Received 403 Forbidden for https://rr4---sn-p5qlsn7s.googlevideo.com/.... Retrying with Older Player...

[test][Session]: Generating new session data.
[test][Player]: Player used /7795af42/player_ias.vflset/en_US/base.js.
[test][Player]: Obtained new signature timestamp (20139).
[test][Player]: Transformed signature and n values.

[test][Player]: Deciphered URL: https://rr5---sn-p5qs7nzr.googlevideo.com/...
[test][Validation]: URL passed validation.

Expected behavior

shouldn't 403

Current behavior

403s

Version

Default

Anything else?

No response

Checklist

• I am running the latest version.
• I checked the documentation and found no answer.
• I have searched the existing issues and made sure this is not a duplicate.
• I have provided sufficient information.

[coderonex]

Thanks for sharing, I'm experiencing this problem as well

[Veeno]

This seems related to FreeTubeApp/FreeTube#6701.

[Fijxu]

Regardless of the fix on Jinter, we still have this problem on Invidious companion (iv-org/invidious-companion#50). Most of the time, the player_id returned by the /iframe_api request is c8dbda2a, making videoplayback fail with 403 error codes.

Forcing the player_id to 7795af42 fixes our videoplayback problems. (https://git.nadeko.net/Fijxu/invidious-companion/commit/001e2de64c747db5c967ec3174ce59c96e5d19b0)

[LingeringAsh]

Regardless of the fix on Jinter, we still have this problem on Invidious companion (iv-org/invidious-companion#50). Most of the time, the player_id returned by the /iframe_api request is c8dbda2a, making videoplayback fail with 403 error codes.

Forcing the player_id to 7795af42 fixes our videoplayback problems. (https://git.nadeko.net/Fijxu/invidious-companion/commit/001e2de64c747db5c967ec3174ce59c96e5d19b0)

I believe this has not yet been updated to the latest Jintr version. If you could check that, It most likely is the cause of the problem.

Also are you certain you're not IP banned

[Fijxu]

I believe this has not yet been updated to the latest Jintr version. If you could check that, It most likely is the cause of the problem.

Hmmm, are you sure? Invidious-companion doesn't use Jinter directly so it's an indirect dependency that the library Youtube.JS uses. And yes, invidious-companion updated Youtube.JS to 13.1.0 and it didn't work (iv-org/invidious-companion@4191cb8)

Also are you certain you're not IP banned

No, I'm not IP banned, I can play youtube videos without account just fine.

[LuanRT]

@Fijxu
v13.1.0 updates Jinter's version, but that only applies to runtimes using NPM. The Deno release relies on JSR (https://jsr.io/@luanrt/jintr). I think you'll need to force a dependency update.

[Fijxu]

@Fijxu v13.1.0 updates Jinter's version, but that only applies to runtimes using NPM. The Deno release relies on JSR (https://jsr.io/@luanrt/jintr). I think you'll need to force a dependency update.

You can forget about my issue, I was confused all the time and I thought c8dbda2a was the old player. It works fine. Thanks for your work orz

[unixfox]

I guess this issue can be closed :).

[Nansess]

I guess this issue can be closed :).

yes i believe so as well :)