[Question] "The media could not be loaded, either because the server or network failed or because the format is not supported." - inv_sig_helper missing

[DUOLabs333]

Solution here: #4947 (comment)

---

Describe the bug
For almost all videos (shorts and a few other videos seem to be immune), I started getting this error: "The media could not be loaded, either because the server or network failed or because the format is not supported." This started about 2 days ago.

Steps to Reproduce

1. Go to https:///watch?v=tPTvG0Se7L8
2. See error

Logs

Screenshots

Additional context

• Browser (if applicable): Chrome 120
• OS (if applicable): macOS 11

I tried adding the po_token and visitor_data from https://github.com/iv-org/youtube-trusted-session-generator, but it didn't help.

Switching to master-arm64 also didn't help.

[DUOLabs333]

Oh, I think it does work, but cached videos (even those that were opened unsuccessfully) are not sent to the helper.

Yeah, truncation was needed (I remembered the command --- psql -d invidious -c 'TRUNCATE TABLE videos')

Are you managing your containers in Portainer?

No, I use my own scripts.

[unixfox]

Also fixed the problem for me (also for previously failed videos); also did not know that this was needed. It's in the install docs already, but I didn't know it changed/had an update.

Some sort of notification for new install requirements would be cool!

Thanks for the info/fix :)

Invidious has releases now! With a changelog of what changed: https://github.com/iv-org/invidious/releases/tag/v2.20240825

So there were technically an announcement back in the end of august.

---

So you need to add inv_sig_helper and potoken now. By following the updated documentation: https://docs.invidious.io/installation/

---

potoken and inv_sig_helper are not an hard requirement since some IP address may still work on the old method.

If you haven't followed there were actually a constant fight against youtube from June to September: #4734.

Invidious lost for the moment and the IP addresses of most datacenter are blocked.

[sainttttt]

Oh, I think it does work, but cached videos (even those that were opened unsuccessfully) are not sent to the helper.

Yeah, truncation was needed (I remembered the command --- psql -d invidious -c 'TRUNCATE TABLE videos')

Are you managing your containers in Portainer?

No, I use my own scripts.

In case anyone is using docker and this can help, I used this command to truncate the videos table in docker which allowed me to view previously failed videos:

 docker exec invidious-invidious-db-1 psql -U kemal -d invidious -c 'TRUNCATE TABLE videos'

[eleaner]

Adding to the thread - went through the process of running the session generator via docker run quay.io/invidious/youtube-trusted-session-generator, got the two keys

• po_token
• visitor_data identities

plugged them into docker-compose.yml and added those two new keys, along with sig helper and adding signature_server: inv_sig_helper:12999 as well.

inv_sig_helper: image: quay.io/invidious/inv-sig-helper:latest command: ["--tcp", "0.0.0.0:12999"] environment: - RUST_LOG=info restart: unless-stopped cap_drop: - ALL read_only: true security_opt: - no-new-privileges:true

observations:

1. If no account is logged into the instance, every video plays.
2. if you're logged into an existing account with subs/playlists, no video plays.
3. if you create a brand new account, with no subs or playlists, every video plays.
4. if you export invidious settings from import/export under settings, and import into the new account you just created, no video plays.

items # 3. and 4. have thrown me off in a loop. Not sure what is causing that. Any clues on what could be the reason?

Thank you all for your incredible hard work!! we shall prevail!! :)

did anyone ever answer that?

[Lucky-Lobo]

Funny, something must have changed, it all worked perfectly fine until last night. I started getting 403 when watching on DASH - switching to HD720 it's all 206.
Tried to add po_token and visitor_data but, also the truncation several times but no such luck.

Is anyone else having these issues?

EDIT:
Okay, what I just found out:

I have DASH setting for 2160p

When clicking these "shots"-Videos they are working, even in 2160p
But no other, 'regular' video unless i go by HD720 default.

Is this Google, differenciating these sources or types of content?

If anyone need samples i found, just tell me.

Thanks!

[need4swede]

Also having issues

[pflavio]

Same for me, only 720p works (DASH doens't work at all regardless of quality setting).

[danvolchek]

Seeing the same behavior now - even after the addition of the sig helper resolved the first issue. I think this is a new one/needs a new issue.

[Lucky-Lobo]

Seeing the same behavior now - even after the addition of the sig helper resolved the first issue. I think this is a new one/needs a new issue.

I do have the sig-helper running, sill the issue, so I'm not quite sure if the problem is there.

[markturner]

Can this be reopened? It’s clearly still an issue (I’m getting the same results as others, signed out, all videos play; signed in, only lower quality plays).

[unixfox]

No. The original issue is #4734