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

    • JRaccoon@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      7 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.