Video replay error

Hi, I encounter this error, when I played a video ( size >1G, stored in S3 object storage )

warn[2023/10/3 23:52:59] Warning in tracker.

  "err": {
    "stack": "Error: Unknown infoHash db66ee343cd6608c4aabc1ee35a8991df96367c9 requested by ip 172.69.214.XXX\n    at Server.<anonymous> (/var/www/peertube/dist/server/controllers/tracker.js:56:20)\n    at (<anonymous>)\n    at fulfilled (/var/www/peertube/node_modules/tslib/tslib.js:164:62)\n    at runMicrotasks (<anonymous>)\n    at processTicksAndRejections (node:internal/process/task_queues:96:5)",
    "message": "Unknown infoHash db66ee343cd6608c4aabc1ee35a8991df96367c9 requested by ip 172.69.214.XXX"

I have set the upload video size to 50MB. This video size more than 1G, but it still successfully uploaded(I see that file with 1G size in the S3), but it cannot be replyed. Other video can replay without any problem. :sweat_smile:

Can you paste the video URL?

Here it is:

Thank you. :bouquet:

Thanks, from what I see your s3 proxy doesn’t seem to support the byte range request from your web browser. Ensure it correctly forwards Range HTTP header to your S3 provider

Thanks for your reply.

Just to make sure I understand you correctly.

For byte range request, I think you mean to use « fetch byte-range from an object »

Using the Range HTTP header in a GET Object request, you can fetch a byte-range from an object, transferring only the specified portion. …

Typical sizes for byte-range requests are 8 MB or 16 MB. If objects are PUT using a multipart upload, it’s a good practice to GET them in the same part sizes (or at least aligned to part boundaries) for best performance. GET requests can directly address individual parts; for example, GET ?partNumber=N.

from amazon aws

However, I checked my object storage provider does not use a multipart upload. It upload the whole files in to ONE single file.

Or for s3 proxy, do you mean my cloudflare CDN need some configuration?

or do I need to set up something like this post on my server? I saw you also mention, " It seems the range header is not sent to object storage because it returns the entire file every time"

I followed what mentioned in that post thread and used this:

curl '' -X OPTIONS -H 'Access-Control-Request-Method: GET' -H 'Access-Control-Request-Headers: range,user-agent' -H 'Origin:’

it returns with


I don’t know what shall I do next.

I also found this on wasabi, « How to restrict object access based on HTTP referer header? » In which it says


Please note:

-The web browser must pass along the HTTP header request for this policy to function properly

Do you mean that I should configure cloudflare CDN(my s3 proxy) to correct forwards Range HTTP head to wasabi?

So I should use something like "Cloudflare worker Cloudflare worker to fetch byte request range on initial request "?
I don’t know what shall I do next. :sweat_smile: :face_with_peeking_eye:

Sorry, I can read every word, but I really don’t know what to do. Would you please say more about what shall I do? Thanks.