You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the current behavior
We are embedding several (>15) videos into a single page on an external website, and peertube responds with HTTP 409: TOO MANY REQUESTS for several requests.
Steps to reproduce:
Create a dummy HTML page
Embed any 20 videos from the same instance
Open the page
Describe the expected behavior
A larger number of embedded videos (thumbnails and video player) should be properly loaded without triggering error 429. Maybe we could try to reduce the number of calls (e.g., I see captions being loaded before playing the video)?
Additional information
I've tried removing all limit_rate and similar modules from /etc/nginx/sites-available/peertube, but the behaviour persists. I also tried to add ngx_http_limit_req_module, ngx_http_limit_conn_module and follow this guide, but I couldn't manage to solve the issue (either by increasing the limit, either by just removing any limit protection).
Question: is there any other component that could raise 429 error code other than NGINX?
Describe the current behavior
We are embedding several (>15) videos into a single page on an external website, and peertube responds with
HTTP 409: TOO MANY REQUESTS
for several requests.Steps to reproduce:
Describe the expected behavior
A larger number of embedded videos (thumbnails and video player) should be properly loaded without triggering error 429. Maybe we could try to reduce the number of calls (e.g., I see captions being loaded before playing the video)?
Additional information
I've tried removing all
limit_rate
and similar modules from/etc/nginx/sites-available/peertube
, but the behaviour persists. I also tried to add ngx_http_limit_req_module, ngx_http_limit_conn_module and follow this guide, but I couldn't manage to solve the issue (either by increasing the limit, either by just removing any limit protection).Question: is there any other component that could raise 429 error code other than NGINX?
Thank you
The text was updated successfully, but these errors were encountered: