..:: tchncs ::..

1543 readers

1 users here now

Your friendly https://tchncs.de/ community! Discuss whats happening in the tchncs world and/or just use it as a community forum.

German and english allowed.

If you are looking for a way to support tchncs, please check out https://tchncs.de/donate

founded 2 years ago

MODERATORS

milan@discuss.tchncs.de

Does my Lemmy instance support video streaming? tchncs shows ❌ Error: Failed to fetch (aeharding.github.io)

submitted 9 months ago by squirrel@discuss.tchncs.de to c/tchncs@discuss.tchncs.de

5 comments fedilink hide all child comments

Many Lemmy instances are misconfigured, which can break progressive video streaming and even basic image loading in strange ways. The latest default lemmy-ansible config handles this correctly, but many instances use custom proxy setups that cause issues. This tool will check that:

✅ The instance supports HTTP range requests for proper video streaming
✅ CORS headers are properly set for API and pictrs media

The instance result shows:

discuss.tchncs.de ❌ Error: Failed to fetch

top 5 comments

sorted by: hot top controversial new old

[–] squirrel@discuss.tchncs.de 3 points 9 months ago

Could be related to https://discuss.tchncs.de/post/32822957

[–] milan@discuss.tchncs.de 3 points 8 months ago (2 children)

Note: will act on this asap, did not forget

[–] JRaccoon@discuss.tchncs.de 1 points 2 days ago* (last edited 2 days ago)

Any updates on this? I mean, it's not a critical issue by any means, but to my understanding (without knowing the specifics of your hosting setup) it could be an easy fix.

[–] squirrel@discuss.tchncs.de 1 points 8 months ago

Thank you Milan!

[–] JRaccoon@discuss.tchncs.de 2 points 8 months ago

Seems to be a CORS issue. A GET request to https://discuss.tchncs.de/pictrs/image/2254acd7-9ce1-4b07-b334-15631f2847e2.png is correctly responded to with a single Allow-Origin header:

Access-Control-Allow-Origin: *

However, the problem occurs when a browser makes that request. It adds an Origin header (For example, Origin: https://aeharding.github.io/ in this case), and then the server responds with two Allow-Origin headers, which is invalid:

access-control-allow-origin: https://aeharding.github.io/
Access-Control-Allow-Origin: *

(Note the different capitalization.)

Ignoring that, it also seems that the server does not support the Range header. Requesting the same image with the header:

Range: bytes=0-1

returns the full image instead of the requested partial content. This effectively means that while video/audio files hosted on this instance will play, features like fast forwarding won’t work properly. This is something @milan@discuss.tchncs.de will probably want to take a look at some point.