Giters

iv-org / invidious

Invidious is an alternative front-end to YouTube

Home Page:https://invidious.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[Bug] The video returned by YouTube isn't the requested one. (AndroidScreenEmbed client) (VideoNotAvailableException)

qwersj19 opened this issue · comments

commented

Describe the bug

Steps to Reproduce

Logs

Screenshots

Additional context

commented

Same. Here is the backtrace:

The video returned by YouTube isn't the requested one. (Android client) (VideoNotAvailableException)
  from src/invidious/videos/parser.cr:158:9 in 'try_fetch_streaming_data'
  from src/invidious/videos/parser.cr:111:5 in 'extract_video_info:video_id'
  from src/invidious/videos.cr:391:3 in 'fetch_video'
  from src/invidious/videos.cr:379:13 in 'get_video'
  from src/invidious/videos.cr:361:1 in 'get_video:region'
  from src/invidious/routes/watch.cr:55:15 in 'handle'
  from src/invidious/routing.cr:159:19 in '->'
  from lib/kemal/src/kemal/route.cr:12:26 in '->'
  from src/invidious/helpers/handlers.cr:30:37 in 'process_request'
  from lib/kemal/src/kemal/route_handler.cr:17:7 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from lib/kemal/src/kemal/websocket_handler.cr:13:14 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from lib/kemal/src/kemal/filter_handler.cr:21:7 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from src/invidious/helpers/handlers.cr:157:5 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from src/invidious/helpers/handlers.cr:94:12 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from src/invidious/helpers/handlers.cr:146:5 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from src/invidious/helpers/handlers.cr:70:5 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from src/ext/kemal_static_file_handler.cr:162:16 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from lib/kemal/src/kemal/exception_handler.cr:8:7 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from src/invidious/helpers/logger.cr:17:35 in 'call'
  from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
  from lib/kemal/src/kemal/init_handler.cr:12:7 in 'call'
  from /usr/share/crystal/src/http/server/request_processor.cr:51:11 in 'process'
  from /usr/share/crystal/src/http/server.cr:517:5 in 'handle_client'
  from /usr/share/crystal/src/http/server.cr:470:13 in '->'
  from /usr/share/crystal/src/fiber.cr:146:11 in 'run'
  from /usr/share/crystal/src/fiber.cr:98:34 in '->'
  from ???
commented

see #4584
try updating

commented

see #4584 try updating

I updated by pulling the Github repo and pulling new docker images. I ran docker-compose down && docker-compose up -d. I still get the error.

commented

updating solved it for me

commented

updating solved it for me

How did you update it?

commented

updating solved it for me

How did you update it?

https://docs.invidious.io/installation/#updating-a-docker-install

docker-compose pull && docker-compose up -d

commented

updating solved it for me

How did you update it?

https://docs.invidious.io/installation/#updating-a-docker-install

docker-compose pull && docker-compose up -d

That's exactly what I did.

Admin: "It works on my machine."
Docker: "Then we'll ship your machine."
Me: "Your machine doesn't work on my machine."

For some reason Docker is still using the older version 2024.04.10-b673695a @ master. I've run the image prune command though.

I removed the invidious image manually with docker rmi and am going to rebuild. I don't know why it didn't do this to begin with. The docker-compose.yml file I'm using doesn't pull the images from a registry; it builds the images from a Dockerfile in the repository under docker/Dockerfile.

UPDATE: I confirm that rebuilding the image works. My instance is now using the latest version 2024.04.27-eda7444c. It seems that adding docker-compose up --build -d in the update instructions would be a good idea.

commented

@hyperreal64

updating solved it for me

How did you update it?

https://docs.invidious.io/installation/#updating-a-docker-install

docker-compose pull && docker-compose up -d

That's exactly what I did.

Admin: "It works on my machine."
Docker: "Then we'll ship your machine."
Me: "Your machine doesn't work on my machine."

For some reason Docker is still using the older version 2024.04.10-b673695a @ master. I've run the image prune command though.

I removed the invidious image manually with docker rmi and am going to rebuild. I don't know why it didn't do this to begin with. The docker-compose.yml file I'm using doesn't pull the images from a registry; it builds the images from a Dockerfile in the repository under docker/Dockerfile.

UPDATE: I confirm that rebuilding the image works. My instance is now using the latest version 2024.04.27-eda7444c. It seems that adding docker-compose up --build -d in the update instructions would be a good idea.

"User doesn't follow the official doc: https://docs.invidious.io/installation/#docker"

User : Why this doesn't work?

You are using the docker-compose for development, obviously you will run into issues.

commented

"User doesn't follow the official doc: https://docs.invidious.io/installation/#docker"

User : Why this doesn't work?

You are using the docker-compose for development, obviously you will run into issues.

Huh, you're right, I didn't read the official doc where it provides a docker-compose.yml file that uses an official image from quay.io. I just cloned the repository and edited the compose file. That was my fault. My apologies.