Describe the bug
Since a few days, when navigating from my self-hosted Invidious instances Feed -> Popular to a creators Channel by clicking on the name of the creator, which usually brings me to his channel, I get the error message
"Could not extract JSON. Youtube API returned error 400 with message: "Request contains an invalid argument"".
I see the message posted above and the channel contents are not shown.
Logs
These are the logs of the container from when I click on the creators name until the error message pops up in the browser:
invidious | 2024-11-10 09:31:56 UTC [error] YoutubeAPI: Got error 400 when requesting /youtubei/v1/browse
invidious | 2024-11-10 09:31:56 UTC [error] YoutubeAPI: Request contains an invalid argument.
invidious | 2024-11-10 09:31:56 UTC [info] YoutubeAPI: POST data was: {"context" => {"client" => {"hl" => "en", "gl" => "US", "clientName" => "WEB", "clientVersion" => "2.20240814.00.00", "clientScreen" => "WATCH_FULL_SCREEN", "osName" => "Windows", "osVersion" => "10.0", "platform" => "DESKTOP", "visitorData" => "<redacted>"}}, "continuation" => "<redacted>"}
invidious | Exception: Could not extract JSON. Youtube API returned error 400 with message:<br>"Request contains an invalid argument." (InfoException)
invidious | from /usr/share/crystal/src/io/buffered.cr:265:5 in '_post_json'
invidious | from src/invidious/channels/videos.cr:107:12 in 'get_videos:continuation:sort_by'
invidious | from src/invidious/channels/videos.cr:87:12 in 'videos'
invidious | from lib/kemal/src/kemal/route.cr:13:9 in '->'
invidious | from src/invidious/helpers/handlers.cr:30:37 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
invidious | from lib/kemal/src/kemal/filter_handler.cr:21:7 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
invidious | from src/invidious/helpers/handlers.cr:94:12 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call_next'
invidious | from src/ext/kemal_static_file_handler.cr:106:14 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call'
invidious | from /usr/share/crystal/src/http/server/handler.cr:30:7 in 'call'
invidious | from /usr/share/crystal/src/http/server/request_processor.cr:51:11 in 'handle_client'
invidious | from /usr/share/crystal/src/fiber.cr:141:11 in 'run'
invidious | from ???
invidious |
invidious | 2024-11-10 09:31:56 UTC [warn] i18n: Missing translation key "Could not extract JSON. Youtube API returned error 400 with message:<br>"Request contains an invalid argument.""
invidious | 2024-11-10 09:31:56 UTC [info] 500 GET /channel/UCFyP17HoU-vpxhIpGXnXx2g 499.33ms
invidious | 2024-11-10 09:31:56 UTC [info] 200 GET /api/v1/auth/subscriptions 4.48ms
Screenshots
Additional context
Browser: Vivaldi and Edge
OS Windows 11:
Invidious runs in Docker, Image quay.io/invidious/invidious:latest which currently has ID sha256:48147da1f64d3e25dcde4ce26a06bd435401bbbe0d298c722cf7aa425bbab599, created at 2024-08-26T21:00:29.689723426Z and includes Invidious version 2024.08.26-4782a67 @ (HEAD detached at v2.20240825.2)
I can not tell for sure, but if memory serves me right, this just started to pop up out of the blue. I do not think a invidious update was involved and I suspect that on youtubes side something maybe changed in the APIs?
unixfox
commented
2 weeks ago
Describe the bug Since a few days, when navigating from my self-hosted Invidious instances Feed -> Popular to a creators Channel by clicking on the name of the creator, which usually brings me to his channel, I get the error message "Could not extract JSON. Youtube API returned error 400 with message: "Request contains an invalid argument"".
Steps to Reproduce
Logs These are the logs of the container from when I click on the creators name until the error message pops up in the browser:
Screenshots
Additional context