[Bug] Error "414 URI Too Long" trying to reach 2nd page of a channel's video listings

[cinetube]

Description

When trying to browse the 2nd page (or later) of a YouTube channel’s video listings in my self-hosted Invidious instance, the server returns:

414 Request-URI Too Long

The first page of videos loads fine, but clicking “Next” or trying to navigate directly to ?page=2 fails.

---

Environment

• Platform: Raspberry Pi 4 (ARM64, DietPi)
• Invidious version: quay.io/invidious/invidious:latest-arm64
• Reverse proxy: nginx (also tested with Caddy, same behavior)
• Database: Postgres 14-alpine
• Docker Compose setup: standard example from the docs

I also tried:

INVIDIOUS_MAX_REQUEST_LINE_SIZE: 65536

but it doesn’t seem to have any effect on this build.

---

Steps to Reproduce

1. Host Invidious via Docker (quay.io/invidious/invidious:latest-arm64)
2. Open any channel with many videos
3. Scroll to the bottom and click “Next” or go to ?page=2
4. Observe the 414 error

---

Expected Behavior

The second page (and subsequent pages) of channel videos should load normally without an HTTP 414 error.

---

Actual Behavior

A “414 URI Too Long” error appears, both through the reverse proxy and when connecting directly to port 3000.

---

Additional Notes

• Other users (e.g. invidious.nerdvpn.de) running more recent custom builds are not affected, suggesting this is fixed in newer commits or in PR [#5394](feat: Add configurable max_request_line_size to handle 414 errors #5394).
• The INVIDIOUS_MAX_REQUEST_LINE_SIZE environment variable is likely not implemented in the current latest-arm64 image.

Please confirm whether the fix from PR #5394 has been merged into the ARM build pipeline, or if a new image release is required.
Thanks for your work on Invidious!

[unixfox]

Hello, closing as the PR #5394 is still opened.