<div dir="ltr">Hi,<div><br></div><div>The latest update:<br><br>We tested videos on Debian and everything worked smooth, the issue looks to be on FreeBSD. No idea what is it related to though. <br><br>Any guidance will be very much appreciated. :(<br><br>Shahzaib</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 2, 2017 at 1:17 PM, shahzaib mushtaq <span dir="ltr"><<a href="mailto:shahzaib.cb@gmail.com" target="_blank">shahzaib.cb@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Franic,<div><br></div><div>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 :</div><div><br></div><div><a href="https://pastebin.com/gaVWfWJv" target="_blank">https://pastebin.com/gaVWfWJv</a><br></div><span class=""><div><br></div><div>>><span style="font-size:12.8px">There is more than one version of google chrome. Some web reports suggest</span></div><span style="font-size:12.8px">that SPDY support was going to be removed in version 51.<br><br></span></span><div><span style="font-size:12.8px">Chrome version is 64 latest which has removed spdy and supports HTTP2 i guess.</span><span class=""><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">>></span><span style="font-size:12.8px">On that basis, if you are looking for how to diagnose the problem,</span></div><span style="font-size:12.8px">I'd start by looking at the clients and seeing what changed on their side.</span><br><br></span><span style="font-size:12.8px">We are also getting spdy error, we create an html page and put 6 direct video links on the page like following :</span><br><br><span style="font-size:12.8px"><a href="https://pastebin.com/dzpwg26C" target="_blank">https://pastebin.com/dzpwg26C</a></span><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">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 : <a href="http://prntscr.com/g3bqcg" target="_blank">http://prntscr.com/g3bqcg</a></span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Regards.<span class="HOEnZb"><font color="#888888"><br>Shahzaib<br></font></span></span><br></div></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Aug 2, 2017 at 12:13 PM, Francis Daly <span dir="ltr"><<a href="mailto:francis@daoine.org" target="_blank">francis@daoine.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Tue, Aug 01, 2017 at 06:50:39PM +0500, shahzaib mushtaq wrote:<br>
<br>
Hi there,<br>
<br>
</span><span>> Thanks for the answer, the browser is google chrome. Googling not helping<br>
> much we've tried various solutions but all in vain. :-(<br>
<br>
</span>That's not much to go on.<br>
<br>
There is more than one version of google chrome. Some web reports suggest<br>
that SPDY support was going to be removed in version 51.<br>
<br>
Some web reports suggest client-side changes that can avoid that error<br>
message, including one particular malware-protection system leading to<br>
it appearing.<br>
<br>
You don't say which "various solutions" you have tried, so there's no<br>
point me linking to the same web pages that you can find -- perhaps<br>
you've already seen them and done what they suggest.<br>
<br>
<br>
What you seem to be reporting is that things were working fine with your<br>
nginx and some clients; and then without changing nginx, some clients<br>
started failing.<br>
<br>
On that basis, if you are looking for how to diagnose the problem,<br>
I'd start by looking at the clients and seeing what changed on their side.<br>
<br>
There may well be a problem with your nginx setup; or there may well<br>
be something that you can change on your nginx side to unbreak whatever<br>
client changes happened; but from what you have written so far, I see<br>
no evidence of that.<br>
<div class="m_-1122550982566468328HOEnZb"><div class="m_-1122550982566468328h5"><br>
Good luck with it,<br>
<br>
f<br>
--<br>
Francis Daly <a href="mailto:francis@daoine.org" target="_blank">francis@daoine.org</a><br>
______________________________<wbr>_________________<br>
nginx mailing list<br>
<a href="mailto:nginx@nginx.org" target="_blank">nginx@nginx.org</a><br>
<a href="http://mailman.nginx.org/mailman/listinfo/nginx" rel="noreferrer" target="_blank">http://mailman.nginx.org/mailm<wbr>an/listinfo/nginx</a><br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>