Is this something sh admins are aware of? "Many Lemmy instances are misconfigured, which can break progressive video streaming and even basic image loading in strange ways."

Comments

• TheDude@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

  Thanks for bringing this to my attention.

  I found that there were some changes to the nginx.conf file which can be seen here

  it does look like its fixed in the 19.10 version of lemmy. I’ll do another deep dive later tonight to see if we can just update the nginx configuration without upgrading to 19.10 and if its the case will schedule another small maintenance window this week to get it pushed out.

  Thank you

  source

  • funkforager@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

    Thanks for all the great work, El Duderino!

    source
  • Madbrad200@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

    Cheers

    source
• deranger@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

  There’s video streaming on Lemmy?

  source
• TheDude@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

  I’ve went ahead and updated and applied the update to our configuration files. This issue should be sorted now.

  Thanks!

  source
• match@pawb.social ⁨1⁩ ⁨week⁩ ago

  I always wondered what was wrong with shitjustworks

  source

  • Madbrad200@sh.itjust.works ⁨1⁩ ⁨week⁩ ago

    pawb.social seems to have the same error. The site seems to suggest that it may only be an issue if its returning a 200 response, but only admins can check this:

    Expected: A 206 response response with two bytes payload.

    Incorrect: A 200 response, meaning the server is ignoring partial requests, breaking video streaming. This usually indicates improper reverse proxy settings. You may need to enable the Nginx slice module—as seen here in lemmy-ansible. Check the ngx_http_slice_module docs for more details.

    source

    • match@pawb.social ⁨1⁩ ⁨week⁩ ago

      neat! i guess we’re not posting much in the way of furry video at the moment

      @crashdoom@pawb.social fyi

      source