Hi,

The latest update:

We tested videos on Debian and everything worked smooth, the issue looks to
be on FreeBSD. No idea what is it related to though.

Any guidance will be very much appreciated. :(

Shahzaib

On Wed, Aug 2, 2017 at 1:17 PM, shahzaib mushtaq <shahzaib.cb@gmail.com>
wrote:

> Hi Franic,
>
> Thanks for response well i've tried lot more things, updated FreeBsd,
> updated openssl but issue is still there. Do you think is there any
> possibility it is linked with Nginx ? Here is my Nginx SSL config :
>
> https://pastebin.com/gaVWfWJv
>
> >>There is more than one version of google chrome. Some web reports
> suggest
> that SPDY support was going to be removed in version 51.
>
> Chrome version is 64 latest which has removed spdy and supports HTTP2 i
> guess.
>
> >>On that basis, if you are looking for how to diagnose the problem,
> I'd start by looking at the clients and seeing what changed on their side.
>
> We are also getting spdy error, we create an html page and put 6 direct
> video links on the page like following :
>
> https://pastebin.com/dzpwg26C
>
> After that we open this link in Incognito chrome and in Inspect element
> under Console those SPDY protocol errors start to occur. Here see the
> screenshot : http://prntscr.com/g3bqcg
>
> Regards.
> Shahzaib
>
>
> On Wed, Aug 2, 2017 at 12:13 PM, Francis Daly <francis@daoine.org> wrote:
>
>> On Tue, Aug 01, 2017 at 06:50:39PM +0500, shahzaib mushtaq wrote:
>>
>> Hi there,
>>
>> > Thanks for the answer, the browser is google chrome. Googling not
>> helping
>> > much we've tried various solutions but all in vain. :-(
>>
>> That's not much to go on.
>>
>> There is more than one version of google chrome. Some web reports suggest
>> that SPDY support was going to be removed in version 51.
>>
>> Some web reports suggest client-side changes that can avoid that error
>> message, including one particular malware-protection system leading to
>> it appearing.
>>
>> You don't say which "various solutions" you have tried, so there's no
>> point me linking to the same web pages that you can find -- perhaps
>> you've already seen them and done what they suggest.
>>
>>
>> What you seem to be reporting is that things were working fine with your
>> nginx and some clients; and then without changing nginx, some clients
>> started failing.
>>
>> On that basis, if you are looking for how to diagnose the problem,
>> I'd start by looking at the clients and seeing what changed on their side.
>>
>> There may well be a problem with your nginx setup; or there may well
>> be something that you can change on your nginx side to unbreak whatever
>> client changes happened; but from what you have written so far, I see
>> no evidence of that.
>>
>> Good luck with it,
>>
>> f
>> --
>> Francis Daly francis@daoine.org
>> _______________________________________________
>> nginx mailing list
>> nginx@nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx