Welcome! Log In Create A New Profile

Advanced

ERR_SPDY_PROTOCOL_ERROR Nginx !!

Posted by shahzaib mushtaq 
shahzaib mushtaq
ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 01, 2017 10:50AM
Hi,

It was working well back in days but there's sudden error which is
preventing our users to play videos in browser. The error is :

GET
https://domain.com/files/videos/2017/08/01/15015680292fcdf-360.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
net::ERR_SPDY_PROTOCOL_ERROR


We're unable to find any errors in nginx logs.

Here is the Nginx Version :

[root@cw008 /tunefiles/files]# nginx -V
nginx version: nginx/1.10.1
built with OpenSSL 1.0.2j 26 Sep 2016
TLS SNI support enabled
configure arguments: --prefix=/usr/local/etc/nginx --with-cc-opt='-I
/usr/local/include' --with-ld-opt='-L /usr/local/lib'
--conf-path=/usr/local/etc/nginx/nginx.conf
--sbin-path=/usr/local/sbin/nginx --pid-path=/var/run/nginx.pid
--error-log-path=/var/log/nginx/error.log --user=www --group=www
--modules-path=/usr/local/libexec/nginx --with-file-aio --with-ipv6
--http-client-body-temp-path=/var/tmp/nginx/client_body_temp
--http-fastcgi-temp-path=/var/tmp/nginx/fastcgi_temp
--http-proxy-temp-path=/var/tmp/nginx/proxy_temp
--http-scgi-temp-path=/var/tmp/nginx/scgi_temp
--http-uwsgi-temp-path=/var/tmp/nginx/uwsgi_temp
--http-log-path=/var/log/nginx/access.log --with-http_addition_module
--with-http_auth_request_module --with-http_dav_module
--with-http_flv_module --with-http_gzip_static_module
--with-http_gunzip_module --with-http_mp4_module
--with-http_random_index_module --with-http_realip_module
--with-http_secure_link_module --with-http_slice_module
--with-http_stub_status_module --with-http_sub_module --with-pcre
--with-http_v2_module --with-stream=dynamic --with-stream_ssl_module
--with-threads --with-mail=dynamic --without-mail_imap_module
--without-mail_pop3_module --without-mail_smtp_module
--with-mail_ssl_module --with-http_ssl_module

======================================================

Please guide me on how should i diagnose this error ?

Thanks.
Shahzaib
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Francis Daly
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 01, 2017 02:50PM
On Tue, Aug 01, 2017 at 01:47:36PM +0500, shahzaib mushtaq wrote:

Hi there,

> It was working well back in days but there's sudden error which is
> preventing our users to play videos in browser. The error is :
>
> GET
> https://domain.com/files/videos/2017/08/01/15015680292fcdf-360.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
> net::ERR_SPDY_PROTOCOL_ERROR
>
>
> We're unable to find any errors in nginx logs.

If the error message came from something not-nginx, possibly web-searching
for it in the context of that other thing will give a hint as to the
reason?

Which browser shows the error message, and did that browser change
anything recently?

Good luck with it,

f
--
Francis Daly francis@daoine.org
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 01, 2017 04:00PM
Hi,

Thanks for the answer, the browser is google chrome. Googling not helping
much we've tried various solutions but all in vain. :-(

http://prntscr.com/g2zqo9

Also the OS is FreeBSD.

Regards.
Shahzaib

On Tue, Aug 1, 2017 at 5:39 PM, Francis Daly <francis@daoine.org> wrote:

> On Tue, Aug 01, 2017 at 01:47:36PM +0500, shahzaib mushtaq wrote:
>
> Hi there,
>
> > It was working well back in days but there's sudden error which is
> > preventing our users to play videos in browser. The error is :
> >
> > GET
> > https://domain.com/files/videos/2017/08/01/15015680292fcdf-360.mp4?h=
> vOilKo_cOUft5fViRqIcMg&ttl=1501588832
> > net::ERR_SPDY_PROTOCOL_ERROR
> >
> >
> > We're unable to find any errors in nginx logs.
>
> If the error message came from something not-nginx, possibly web-searching
> for it in the context of that other thing will give a hint as to the
> reason?
>
> Which browser shows the error message, and did that browser change
> anything recently?
>
> 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
Etienne Robillard
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 01, 2017 06:00PM
Hi,

i think mozilla don't even support SPDY protocol anymore. The
replacement is HTTP2.

Best regards,

E


Le 2017-08-01 à 09:50, shahzaib mushtaq a écrit :
> Hi,
>
> Thanks for the answer, the browser is google chrome. Googling not
> helping much we've tried various solutions but all in vain. :-(
>
> http://prntscr.com/g2zqo9
>
> Also the OS is FreeBSD.
>
> Regards.
> Shahzaib
>
> On Tue, Aug 1, 2017 at 5:39 PM, Francis Daly <francis@daoine.org
> <mailto:francis@daoine.org>> wrote:
>
> On Tue, Aug 01, 2017 at 01:47:36PM +0500, shahzaib mushtaq wrote:
>
> Hi there,
>
> > It was working well back in days but there's sudden error which is
> > preventing our users to play videos in browser. The error is :
> >
> > GET
> >
> https://domain.com/files/videos/2017/08/01/15015680292fcdf-360.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
> https://domain.com/files/videos/2017/08/01/15015680292fcdf-360.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
> > net::ERR_SPDY_PROTOCOL_ERROR
> >
> >
> > We're unable to find any errors in nginx logs.
>
> If the error message came from something not-nginx, possibly
> web-searching
> for it in the context of that other thing will give a hint as to the
> reason?
>
> Which browser shows the error message, and did that browser change
> anything recently?
>
> Good luck with it,
>
> f
> --
> Francis Daly francis@daoine.org <mailto:francis@daoine.org>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org <mailto:nginx@nginx.org>
> http://mailman.nginx.org/mailman/listinfo/nginx
> http://mailman.nginx.org/mailman/listinfo/nginx
>
>
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

--
Etienne Robillard
tkadm30@yandex.com
http://www.isotopesoftware.ca/

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 01, 2017 10:40PM
Hi,

This error is mostly coming on google chrome. :(

Shahzaib

On Tue, Aug 1, 2017 at 8:51 PM, Etienne Robillard <tkadm30@yandex.com>
wrote:

> Hi,
>
> i think mozilla don't even support SPDY protocol anymore. The replacement
> is HTTP2.
> Best regards,
>
> E
>
> Le 2017-08-01 à 09:50, shahzaib mushtaq a écrit :
>
> Hi,
>
> Thanks for the answer, the browser is google chrome. Googling not helping
> much we've tried various solutions but all in vain. :-(
>
> http://prntscr.com/g2zqo9
>
> Also the OS is FreeBSD.
>
> Regards.
> Shahzaib
>
> On Tue, Aug 1, 2017 at 5:39 PM, Francis Daly <francis@daoine.org> wrote:
>
>> On Tue, Aug 01, 2017 at 01:47:36PM +0500, shahzaib mushtaq wrote:
>>
>> Hi there,
>>
>> > It was working well back in days but there's sudden error which is
>> > preventing our users to play videos in browser. The error is :
>> >
>> > GET
>> > https://domain.com/files/videos/2017/08/01/15015680292fcdf-
>> 360.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
>> > net::ERR_SPDY_PROTOCOL_ERROR
>> >
>> >
>> > We're unable to find any errors in nginx logs.
>>
>> If the error message came from something not-nginx, possibly web-searching
>> for it in the context of that other thing will give a hint as to the
>> reason?
>>
>> Which browser shows the error message, and did that browser change
>> anything recently?
>>
>> 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 listnginx@nginx.orghttp://mailman.nginx.org/mailman/listinfo/nginx
>
>
> --
> Etienne Robillardtkadm30@yandex.comhttp://www.isotopesoftware.ca/
>
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
spectre inc
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 01, 2017 10:40PM
Are you useing ssl?

On Tue, Aug 1, 2017 at 4:31 PM shahzaib mushtaq <shahzaib.cb@gmail.com>
wrote:

> Hi,
>
> This error is mostly coming on google chrome. :(
>
>
> Shahzaib
>
> On Tue, Aug 1, 2017 at 8:51 PM, Etienne Robillard <tkadm30@yandex.com>
> wrote:
>
>> Hi,
>>
>> i think mozilla don't even support SPDY protocol anymore. The replacement
>> is HTTP2.
>> Best regards,
>>
>> E
>>
>> Le 2017-08-01 à 09:50, shahzaib mushtaq a écrit :
>>
>> Hi,
>>
>> Thanks for the answer, the browser is google chrome. Googling not helping
>> much we've tried various solutions but all in vain. :-(
>>
>> http://prntscr.com/g2zqo9
>>
>> Also the OS is FreeBSD.
>>
>> Regards.
>> Shahzaib
>>
>> On Tue, Aug 1, 2017 at 5:39 PM, Francis Daly <francis@daoine.org> wrote:
>>
>>> On Tue, Aug 01, 2017 at 01:47:36PM +0500, shahzaib mushtaq wrote:
>>>
>>> Hi there,
>>>
>>> > It was working well back in days but there's sudden error which is
>>> > preventing our users to play videos in browser. The error is :
>>> >
>>> > GET
>>> >
>>> https://domain.com/files/videos/2017/08/01/15015680292fcdf-360.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
>>> > net::ERR_SPDY_PROTOCOL_ERROR
>>> >
>>> >
>>> > We're unable to find any errors in nginx logs.
>>>
>>> If the error message came from something not-nginx, possibly
>>> web-searching
>>> for it in the context of that other thing will give a hint as to the
>>> reason?
>>>
>>> Which browser shows the error message, and did that browser change
>>> anything recently?
>>>
>>> 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 listnginx@nginx.orghttp://mailman.nginx.org/mailman/listinfo/nginx
>>
>>
>> --
>> Etienne Robillardtkadm30@yandex.comhttp://www.isotopesoftware.ca/
>>
>>
> _______________________________________________
> 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
spectre inc
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 01, 2017 11:30PM
I had the same problem when seeing a site with https is that's the case then it has to do with the ssl and there is work around let me know and I'll tell you what to fix

Sent from my iPhone

> On Aug 1, 2017, at 2:30 PM, shahzaib mushtaq <shahzaib.cb@gmail.com> wrote:
>
> Hi,
>
> This error is mostly coming on google chrome. :(
>
> Shahzaib
>
>> On Tue, Aug 1, 2017 at 8:51 PM, Etienne Robillard <tkadm30@yandex.com> wrote:
>> Hi,
>>
>> i think mozilla don't even support SPDY protocol anymore. The replacement is HTTP2.
>> Best regards,
>> E
>>
>>> Le 2017-08-01 à 09:50, shahzaib mushtaq a écrit :
>>> Hi,
>>>
>>> Thanks for the answer, the browser is google chrome. Googling not helping much we've tried various solutions but all in vain. :-(
>>>
>>> http://prntscr.com/g2zqo9
>>>
>>> Also the OS is FreeBSD.
>>>
>>> Regards.
>>> Shahzaib
>>>
>>>> On Tue, Aug 1, 2017 at 5:39 PM, Francis Daly <francis@daoine.org> wrote:
>>>> On Tue, Aug 01, 2017 at 01:47:36PM +0500, shahzaib mushtaq wrote:
>>>>
>>>> Hi there,
>>>>
>>>> > It was working well back in days but there's sudden error which is
>>>> > preventing our users to play videos in browser. The error is :
>>>> >
>>>> > GET
>>>> > https://domain.com/files/videos/2017/08/01/15015680292fcdf-360.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
>>>> > net::ERR_SPDY_PROTOCOL_ERROR
>>>> >
>>>> >
>>>> > We're unable to find any errors in nginx logs.
>>>>
>>>> If the error message came from something not-nginx, possibly web-searching
>>>> for it in the context of that other thing will give a hint as to the
>>>> reason?
>>>>
>>>> Which browser shows the error message, and did that browser change
>>>> anything recently?
>>>>
>>>> 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
>>
>> --
>> Etienne Robillard
>> tkadm30@yandex.com
>> http://www.isotopesoftware.ca/
>
> _______________________________________________
> 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
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 01, 2017 11:40PM
Hi,

What fix do you suggest ?

Shahzaib

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Aug 2, 2017 at 2:15 AM, spectre inc <sales.skylinehosting@gmail.com>
wrote:

> I had the same problem when seeing a site with https is that's the case
> then it has to do with the ssl and there is work around let me know and
> I'll tell you what to fix
>
> Sent from my iPhone
>
> On Aug 1, 2017, at 2:30 PM, shahzaib mushtaq <shahzaib.cb@gmail.com>
> wrote:
>
> Hi,
>
> This error is mostly coming on google chrome. :(
>
> Shahzaib
>
> On Tue, Aug 1, 2017 at 8:51 PM, Etienne Robillard <tkadm30@yandex.com>
> wrote:
>
>> Hi,
>>
>> i think mozilla don't even support SPDY protocol anymore. The replacement
>> is HTTP2.
>> Best regards,
>>
>> E
>>
>> Le 2017-08-01 à 09:50, shahzaib mushtaq a écrit :
>>
>> Hi,
>>
>> Thanks for the answer, the browser is google chrome. Googling not helping
>> much we've tried various solutions but all in vain. :-(
>>
>> http://prntscr.com/g2zqo9
>>
>> Also the OS is FreeBSD.
>>
>> Regards.
>> Shahzaib
>>
>> On Tue, Aug 1, 2017 at 5:39 PM, Francis Daly <francis@daoine.org> wrote:
>>
>>> On Tue, Aug 01, 2017 at 01:47:36PM +0500, shahzaib mushtaq wrote:
>>>
>>> Hi there,
>>>
>>> > It was working well back in days but there's sudden error which is
>>> > preventing our users to play videos in browser. The error is :
>>> >
>>> > GET
>>> > https://domain.com/files/videos/2017/08/01/15015680292fcdf-3
>>> 60.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
>>> > net::ERR_SPDY_PROTOCOL_ERROR
>>> >
>>> >
>>> > We're unable to find any errors in nginx logs.
>>>
>>> If the error message came from something not-nginx, possibly
>>> web-searching
>>> for it in the context of that other thing will give a hint as to the
>>> reason?
>>>
>>> Which browser shows the error message, and did that browser change
>>> anything recently?
>>>
>>> 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 listnginx@nginx.orghttp://mailman.nginx.org/mailman/listinfo/nginx
>>
>>
>> --
>> Etienne Robillardtkadm30@yandex.comhttp://www.isotopesoftware.ca/
>>
>>
> _______________________________________________
> 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
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
spectre inc
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 01, 2017 11:50PM
The current workaround is to change the SSL Cipher Suite
On Tue, Aug 1, 2017 at 5:37 PM shahzaib mushtaq <shahzaib.cb@gmail.com>
wrote:

> Hi,
>
> What fix do you suggest ?
>
> Shahzaib
>
>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free.
> www.avast.com
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> <#m_5273588369263236465_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Wed, Aug 2, 2017 at 2:15 AM, spectre inc <
> sales.skylinehosting@gmail.com> wrote:
>
>> I had the same problem when seeing a site with https is that's the case
>> then it has to do with the ssl and there is work around let me know and
>> I'll tell you what to fix
>>
>> Sent from my iPhone
>>
>> On Aug 1, 2017, at 2:30 PM, shahzaib mushtaq <shahzaib.cb@gmail.com>
>> wrote:
>>
>> Hi,
>>
>> This error is mostly coming on google chrome. :(
>>
>> Shahzaib
>>
>> On Tue, Aug 1, 2017 at 8:51 PM, Etienne Robillard <tkadm30@yandex.com>
>> wrote:
>>
>>> Hi,
>>>
>>> i think mozilla don't even support SPDY protocol anymore. The
>>> replacement is HTTP2.
>>> Best regards,
>>>
>>> E
>>>
>>> Le 2017-08-01 à 09:50, shahzaib mushtaq a écrit :
>>>
>>> Hi,
>>>
>>> Thanks for the answer, the browser is google chrome. Googling not
>>> helping much we've tried various solutions but all in vain. :-(
>>>
>>> http://prntscr.com/g2zqo9
>>>
>>> Also the OS is FreeBSD.
>>>
>>> Regards.
>>> Shahzaib
>>>
>>> On Tue, Aug 1, 2017 at 5:39 PM, Francis Daly <francis@daoine.org> wrote:
>>>
>>>> On Tue, Aug 01, 2017 at 01:47:36PM +0500, shahzaib mushtaq wrote:
>>>>
>>>> Hi there,
>>>>
>>>> > It was working well back in days but there's sudden error which is
>>>> > preventing our users to play videos in browser. The error is :
>>>> >
>>>> > GET
>>>> >
>>>> https://domain.com/files/videos/2017/08/01/15015680292fcdf-360.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
>>>> > net::ERR_SPDY_PROTOCOL_ERROR
>>>> >
>>>> >
>>>> > We're unable to find any errors in nginx logs.
>>>>
>>>> If the error message came from something not-nginx, possibly
>>>> web-searching
>>>> for it in the context of that other thing will give a hint as to the
>>>> reason?
>>>>
>>>> Which browser shows the error message, and did that browser change
>>>> anything recently?
>>>>
>>>> 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 listnginx@nginx.orghttp://mailman.nginx.org/mailman/listinfo/nginx
>>>
>>>
>>> --
>>> Etienne Robillardtkadm30@yandex.comhttp://www.isotopesoftware.ca/
>>>
>>>
>> _______________________________________________
>> 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
>>
>
> _______________________________________________
> 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
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 12:10AM
Hi,

Following ciphers i am using :

server {
listen 443 http2;
ssl on;
ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
ssl_ciphers
'ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4';
ssl_prefer_server_ciphers on;

===========

What do you think should i change it to ?

Thanks
Shahzaib

On Wed, Aug 2, 2017 at 2:40 AM, spectre inc <sales.skylinehosting@gmail.com>
wrote:

> The current workaround is to change the SSL Cipher Suite
>
> On Tue, Aug 1, 2017 at 5:37 PM shahzaib mushtaq <shahzaib.cb@gmail.com>
> wrote:
>
>> Hi,
>>
>> What fix do you suggest ?
>>
>> Shahzaib
>>
>>
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free.
>> www.avast.com
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
>> <#m_-6754267639672595285_m_5273588369263236465_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> On Wed, Aug 2, 2017 at 2:15 AM, spectre inc <sales.skylinehosting@gmail.
>> com> wrote:
>>
>>> I had the same problem when seeing a site with https is that's the case
>>> then it has to do with the ssl and there is work around let me know and
>>> I'll tell you what to fix
>>>
>>> Sent from my iPhone
>>>
>>> On Aug 1, 2017, at 2:30 PM, shahzaib mushtaq <shahzaib.cb@gmail.com>
>>> wrote:
>>>
>>> Hi,
>>>
>>> This error is mostly coming on google chrome. :(
>>>
>>> Shahzaib
>>>
>>> On Tue, Aug 1, 2017 at 8:51 PM, Etienne Robillard <tkadm30@yandex.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> i think mozilla don't even support SPDY protocol anymore. The
>>>> replacement is HTTP2.
>>>> Best regards,
>>>>
>>>> E
>>>>
>>>> Le 2017-08-01 à 09:50, shahzaib mushtaq a écrit :
>>>>
>>>> Hi,
>>>>
>>>> Thanks for the answer, the browser is google chrome. Googling not
>>>> helping much we've tried various solutions but all in vain. :-(
>>>>
>>>> http://prntscr.com/g2zqo9
>>>>
>>>> Also the OS is FreeBSD.
>>>>
>>>> Regards.
>>>> Shahzaib
>>>>
>>>> On Tue, Aug 1, 2017 at 5:39 PM, Francis Daly <francis@daoine.org>
>>>> wrote:
>>>>
>>>>> On Tue, Aug 01, 2017 at 01:47:36PM +0500, shahzaib mushtaq wrote:
>>>>>
>>>>> Hi there,
>>>>>
>>>>> > It was working well back in days but there's sudden error which is
>>>>> > preventing our users to play videos in browser. The error is :
>>>>> >
>>>>> > GET
>>>>> > https://domain.com/files/videos/2017/08/01/
>>>>> 15015680292fcdf-360.mp4?h=vOilKo_cOUft5fViRqIcMg&ttl=1501588832
>>>>> > net::ERR_SPDY_PROTOCOL_ERROR
>>>>> >
>>>>> >
>>>>> > We're unable to find any errors in nginx logs.
>>>>>
>>>>> If the error message came from something not-nginx, possibly
>>>>> web-searching
>>>>> for it in the context of that other thing will give a hint as to the
>>>>> reason?
>>>>>
>>>>> Which browser shows the error message, and did that browser change
>>>>> anything recently?
>>>>>
>>>>> 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 listnginx@nginx.orghttp://mailman.nginx.org/mailman/listinfo/nginx
>>>>
>>>>
>>>> --
>>>> Etienne Robillardtkadm30@yandex.comhttp://www.isotopesoftware.ca/
>>>>
>>>>
>>> _______________________________________________
>>> 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
>>>
>>
>> _______________________________________________
>> 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
>
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Rainer Duffner
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 12:10AM
> Am 01.08.2017 um 23:51 schrieb shahzaib mushtaq <shahzaib.cb@gmail.com>:
>
> What do you think should i change it to ?



What does SSL-Labs say to it?

Or htbridge?



Rainer_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Matthias Fechner
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 08:10AM
Am 01.08.2017 um 23:51 schrieb shahzaib mushtaq:
> Following ciphers i am using :
>
> server {
> listen 443 http2;
> ssl on;
> ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
> ssl_ciphers
> 'ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4';
> ssl_prefer_server_ciphers on;
>
> ===========
>
> What do you think should i change it to ?

have you tried to using this generator:
https://mozilla.github.io/server-side-tls/ssl-config-generator/

A very helpful tool.

Gruß
Matthias

--

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Francis Daly
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 09:20AM
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
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 10:20AM
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
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 12:00PM
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
Alt
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 04:00PM
Hello!

This issue often happens when a cipher is missing in your cipher list and
Chrome tries to use another cipher forbidden in the HTTP/2 spec. Using SSL
Labs would normally display such error (in the "Handshake Simulation" part
of thei results).

And yes, Chrome sucks for displaying an error related to SPDY, even when you
don't have any SPDY and are using HTTP/2.

Posted at Nginx Forum: https://forum.nginx.org/read.php?2,275776,275816#msg-275816

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 05:10PM
Hi,

What could be the exact cipher missing in this case ? Here is the cipher
list i am using , also there's nothing i found of error in ssl labs instead
for two ciphers which it said as WEAK while ssllabs gave A grade.

ssl_ciphers
'ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!CAMELLIA:!DES:!MD5:!PSK:!RC4';




On Wed, Aug 2, 2017 at 6:53 PM, Alt <nginx-forum@forum.nginx.org> wrote:

> Hello!
>
> This issue often happens when a cipher is missing in your cipher list and
> Chrome tries to use another cipher forbidden in the HTTP/2 spec. Using SSL
> Labs would normally display such error (in the "Handshake Simulation" part
> of thei results).
>
> And yes, Chrome sucks for displaying an error related to SPDY, even when
> you
> don't have any SPDY and are using HTTP/2.
>
> Posted at Nginx Forum: https://forum.nginx.org/read.
> php?2,275776,275816#msg-275816
>
> _______________________________________________
> 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
Lukas Tribus
AW: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 05:20PM
Hello!


> This issue often happens when a cipher is missing in your cipher list and
> Chrome tries to use another cipher forbidden in the HTTP/2 spec.

Wrong. In that case, Chrome would return:
ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY

which is different than ERR_SPDY_PROTOCOL_ERROR.


Also note that all those error codes are valid for HTTP2 as well, its just
that their name hasn't been updated in Chrome yet.


I'd suggest to upgrade to a supported nginx release without any
third-party modules first of all, also try without mp4 streaming
code paths.

Try to reproduce it in an isolated environment, then you can
debug on the client site and on the nginx side.



Lukas


_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 06:50PM
The only fix that worked is disabling the HTTP2 on Nginx for chrome. No
idea what the actual problem is.

On Wed, Aug 2, 2017 at 8:11 PM, Lukas Tribus <luky-37@hotmail.com> wrote:

> Hello!
>
>
> > This issue often happens when a cipher is missing in your cipher list and
> > Chrome tries to use another cipher forbidden in the HTTP/2 spec.
>
> Wrong. In that case, Chrome would return:
> ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY
>
> which is different than ERR_SPDY_PROTOCOL_ERROR.
>
>
> Also note that all those error codes are valid for HTTP2 as well, its just
> that their name hasn't been updated in Chrome yet.
>
>
> I'd suggest to upgrade to a supported nginx release without any
> third-party modules first of all, also try without mp4 streaming
> code paths.
>
> Try to reproduce it in an isolated environment, then you can
> debug on the client site and on the nginx side.
>
>
>
> Lukas
>
>
> _______________________________________________
> 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
Valentin V. Bartenev
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 08:10PM
On Wednesday 02 August 2017 21:43:19 shahzaib mushtaq wrote:
> The only fix that worked is disabling the HTTP2 on Nginx for chrome. No
> idea what the actual problem is.
>
[..]

There are a lot of problems has been fixed since 1.10.
As already suggested, you should update nginx to a supported version.

wbr, Valentin V. Bartenev

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 02, 2017 08:10PM
I've already update Nginx to 12.X but issue is the same :

nginx version: nginx/1.12.1
built with OpenSSL 1.0.2l 25 May 2017
TLS SNI support enabled
configure arguments: --prefix=/usr/local/etc/nginx --with-cc-opt='-I
/usr/local/include' --with-ld-opt='-L /usr/local/lib'
--conf-path=/usr/local/etc/nginx/nginx.conf
--sbin-path=/usr/local/sbin/nginx --pid-path=/var/run/nginx.pid
--error-log-path=/var/log/nginx/error.log --user=www --group=www
--modules-path=/usr/local/libexec/nginx --with-file-aio
--with-cc-opt='-DNGX_HAVE_INET6=0 -I /usr/local/include'
--http-client-body-temp-path=/var/tmp/nginx/client_body_temp
--http-fastcgi-temp-path=/var/tmp/nginx/fastcgi_temp
--http-proxy-temp-path=/var/tmp/nginx/proxy_temp
--http-scgi-temp-path=/var/tmp/nginx/scgi_temp
--http-uwsgi-temp-path=/var/tmp/nginx/uwsgi_temp
--http-log-path=/var/log/nginx/access.log --with-http_addition_module
--without-http-cache --with-http_flv_module
--with-http_geoip_module=dynamic --with-http_gzip_static_module
--with-http_mp4_module --with-http_realip_module
--with-http_secure_link_module --with-pcre --with-http_v2_module
--with-threads --with-http_ssl_module

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Wed, Aug 2, 2017 at 11:03 PM, Valentin V. Bartenev <vbart@nginx.com>
wrote:

> On Wednesday 02 August 2017 21:43:19 shahzaib mushtaq wrote:
> > The only fix that worked is disabling the HTTP2 on Nginx for chrome. No
> > idea what the actual problem is.
> >
> [..]
>
> There are a lot of problems has been fixed since 1.10.
> As already suggested, you should update nginx to a supported version.
>
> wbr, Valentin V. Bartenev
>
> _______________________________________________
> 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
Alt
Re: AW: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 03, 2017 01:20AM
Lukas, you're of course right!
My mistake, I see so many times the "ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY"
error that I forgot there was another one which is completely different.

Shahzaib, I'm very sorry, I can't help you :-(
As said by Lukas, have you tried others files than the mp4 we see in your
capture? Like images or just plain text.
And also have you tried compiling nginx without "--with-http_mp4_module"?

Best Regards

Posted at Nginx Forum: https://forum.nginx.org/read.php?2,275776,275828#msg-275828

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Francis Daly
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 03, 2017 09:30AM
On Wed, Aug 02, 2017 at 01:17:06PM +0500, shahzaib mushtaq wrote:

Hi there,

> 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 ?

You have one client that reports an error message.

What are the specific circumstances under which that version of that
client can report that error message? That information may give a hint
as to where the problem is.

Is the problem repeatable? As in: if you do a fresh install with no
historical information of the client browser (a new "profile" or under
a new user account), do you see the same behaviour?

In a later mail, you suggest that you have two test nginx instances,
and one client reports the error against one instance and not against
the other.

"nginx -V" on each could be used to identify any differences in the
compile-time settings. "nginx -T" on each could be used to identify any
difference in the run-time configuration.

> 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.

As far as I know, there are about half a dozen "latest" versions of
Google Chrome, and none of them are version 64 currently.

If you ask for help in a Google Chrome mailing list, you may want to
provide the specific version number there to allow them to identify what
exactly you are running.

Good luck with it,

f
--
Francis Daly francis@daoine.org
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 03, 2017 06:20PM
Hi,

>>As far as I know, there are about half a dozen "latest" versions of
Google Chrome, and none of them are version 64 currently.

Your're right sorry, the version latest is 60.


>>You have one client that reports an error message.What are the specific
circumstances under which that version of that
client can report that error message? That information may give a hint
as to where the problem is.

Well, i can generate this issue without a problem all i've to do is create
a test.html page, put 5 x static video links (our server http2 mp4 video
links) and play them simultaneously. For the first request they'll start
playing with *200* status in inspect element under *Network *tab but for
further chunk requests from chrome, it'll stuck in *pending *and under *Console
*tab spdy error will start to occur. Once i've disabled HTTP2 that issue is
gone but 'pending' status issue still was there which i think is linked
with my below issue :

----------------------------------------------------------------------------

Now we think there's issue with one SSL certificate which we renewed
recently. Our server has actually two different domain SSL certificates
configured on same ip;

*.mydomain.com
*.yourdomain.com (*Renewed*)

We've configured both these certificates vhosts in
/usr/local/etc/nginx/vhosts/ directory. After installing certificate we
tested it with sslshopper and both were installed properly (CN,
Intermediate Chain etc were properly listed for each).

Now here is the twist comes. Recently we've renewed the SSL
certificate for **.yourdomain.com
http://yourdomain.com* from *Godaddy *and after that sslshopper shows
correct CN and intermediate chain for new certificate (*.yourdomain.com) but
openssl is showing the CN of *.yourdomain.com as of *.mydomain.com.

I repeat SSLshopper and SSLLabs shows proper CN (common name) but if i use
openssl command to verify it :

[root@cw012 /usr/ports/security/ca_root_nss]# openssl s_client -connect
s4.yourdomain.com:443 |head -30depth=2 C = US, O = GeoTrust Inc., OU = (c)
2008 GeoTrust Inc. - For authorized use only, CN = GeoTrust Primary
Certification Authority - G3verify return:1s_clidepth=1 C = US, O =
GeoTrust Inc., CN = RapidSSL SHA256 CA - G2verify return:1head depth=0
CN = **.mydomain.com
http://mydomain.com*

Here you can see that CN is *.mydomain.com instead of *.yourdomain.com.

==============================================

Now for testing i had disabled vhost for yourdomain.com and used only
single mydomain.com after which requests for serving files improved
drastically before that, if we would had hit a page, it'll first go to
'pending' status in chrome inspect element and after few time it'll show
200 status but now it goes directly to 200 status.

I'm really confused on what's happening right now but if someone has faced
this experience before please let me know, on first i thought there could
be nginx config issue but the problem is SSLshopper and ssllabs are showing
proper CName so now i think maybe its related to chrome


Thanks for your help.
Shahzaib

https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Thu, Aug 3, 2017 at 12:27 PM, Francis Daly <francis@daoine.org> wrote:

> On Wed, Aug 02, 2017 at 01:17:06PM +0500, shahzaib mushtaq wrote:
>
> Hi there,
>
> > 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 ?
>
> You have one client that reports an error message.
>
> What are the specific circumstances under which that version of that
> client can report that error message? That information may give a hint
> as to where the problem is.
>
> Is the problem repeatable? As in: if you do a fresh install with no
> historical information of the client browser (a new "profile" or under
> a new user account), do you see the same behaviour?
>
> In a later mail, you suggest that you have two test nginx instances,
> and one client reports the error against one instance and not against
> the other.
>
> "nginx -V" on each could be used to identify any differences in the
> compile-time settings. "nginx -T" on each could be used to identify any
> difference in the run-time configuration.
>
> > 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.
>
> As far as I know, there are about half a dozen "latest" versions of
> Google Chrome, and none of them are version 64 currently.
>
> If you ask for help in a Google Chrome mailing list, you may want to
> provide the specific version number there to allow them to identify what
> exactly you are running.
>
> 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
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 03, 2017 11:10PM
Update:

Now i removed vhost for mydomain.com and yourdomain.com is now showing
correct Common name. So there's some kind of overlapping in vhosts.


https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon
Virus-free.
www.avast.com
https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Thu, Aug 3, 2017 at 9:13 PM, shahzaib mushtaq <shahzaib.cb@gmail.com>
wrote:

> Hi,
>
> >>As far as I know, there are about half a dozen "latest" versions of
> Google Chrome, and none of them are version 64 currently.
>
> Your're right sorry, the version latest is 60.
>
>
> >>You have one client that reports an error message.What are the specific
> circumstances under which that version of that
> client can report that error message? That information may give a hint
> as to where the problem is.
>
> Well, i can generate this issue without a problem all i've to do is create
> a test.html page, put 5 x static video links (our server http2 mp4 video
> links) and play them simultaneously. For the first request they'll start
> playing with *200* status in inspect element under *Network *tab but for
> further chunk requests from chrome, it'll stuck in *pending *and under *Console
> *tab spdy error will start to occur. Once i've disabled HTTP2 that issue
> is gone but 'pending' status issue still was there which i think is linked
> with my below issue :
>
> ------------------------------------------------------------
> ----------------
>
> Now we think there's issue with one SSL certificate which we renewed
> recently. Our server has actually two different domain SSL certificates
> configured on same ip;
>
> *.mydomain.com
> *.yourdomain.com (*Renewed*)
>
> We've configured both these certificates vhosts in
> /usr/local/etc/nginx/vhosts/ directory. After installing certificate we
> tested it with sslshopper and both were installed properly (CN,
> Intermediate Chain etc were properly listed for each).
>
> Now here is the twist comes. Recently we've renewed the SSL certificate
> for **.yourdomain.com http://yourdomain.com* from *Godaddy *and after
> that sslshopper shows correct CN and intermediate chain for new certificate
> (*.yourdomain.com) but openssl is showing the CN of *.yourdomain.com as
> of *.mydomain.com.
>
> I repeat SSLshopper and SSLLabs shows proper CN (common name) but if i use
> openssl command to verify it :
>
> [root@cw012 /usr/ports/security/ca_root_nss]# openssl s_client -connect
> s4.yourdomain.com:443 |head -30depth=2 C = US, O = GeoTrust Inc., OU =
> (c) 2008 GeoTrust Inc. - For authorized use only, CN = GeoTrust Primary
> Certification Authority - G3verify return:1s_clidepth=1 C = US, O =
> GeoTrust Inc., CN = RapidSSL SHA256 CA - G2verify return:1head depth=0 CN = **.mydomain.com
> http://mydomain.com*
>
> Here you can see that CN is *.mydomain.com instead of *.yourdomain.com.
>
> ==============================================
>
> Now for testing i had disabled vhost for yourdomain.com and used only
> single mydomain.com after which requests for serving files improved
> drastically before that, if we would had hit a page, it'll first go to
> 'pending' status in chrome inspect element and after few time it'll show
> 200 status but now it goes directly to 200 status.
>
> I'm really confused on what's happening right now but if someone has faced
> this experience before please let me know, on first i thought there could
> be nginx config issue but the problem is SSLshopper and ssllabs are showing
> proper CName so now i think maybe its related to chrome
>
>
> Thanks for your help.
> Shahzaib
>
>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free.
> www.avast.com
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> <#m_1565204697939808308_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Thu, Aug 3, 2017 at 12:27 PM, Francis Daly <francis@daoine.org> wrote:
>
>> On Wed, Aug 02, 2017 at 01:17:06PM +0500, shahzaib mushtaq wrote:
>>
>> Hi there,
>>
>> > 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 ?
>>
>> You have one client that reports an error message.
>>
>> What are the specific circumstances under which that version of that
>> client can report that error message? That information may give a hint
>> as to where the problem is.
>>
>> Is the problem repeatable? As in: if you do a fresh install with no
>> historical information of the client browser (a new "profile" or under
>> a new user account), do you see the same behaviour?
>>
>> In a later mail, you suggest that you have two test nginx instances,
>> and one client reports the error against one instance and not against
>> the other.
>>
>> "nginx -V" on each could be used to identify any differences in the
>> compile-time settings. "nginx -T" on each could be used to identify any
>> difference in the run-time configuration.
>>
>> > 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.
>>
>> As far as I know, there are about half a dozen "latest" versions of
>> Google Chrome, and none of them are version 64 currently.
>>
>> If you ask for help in a Google Chrome mailing list, you may want to
>> provide the specific version number there to allow them to identify what
>> exactly you are running.
>>
>> 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
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 03, 2017 11:20PM
I've noticed that its related to the orders of virtual host files. For
example if vhost of mydomain.com comes first than yourdomain.com then SSL
CN (common name) for both domains will be *.mydomain.com.

And if vhost of yourdomain.com comes before than mydomain.com then common
name for both domains is yourdomain.com .



On Fri, Aug 4, 2017 at 2:01 AM, shahzaib mushtaq <shahzaib.cb@gmail.com>
wrote:

> Update:
>
> Now i removed vhost for mydomain.com and yourdomain.com is now showing
> correct Common name. So there's some kind of overlapping in vhosts.
>
>
>
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free.
> www.avast.com
> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
> <#m_-2776267015937845177_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>
> On Thu, Aug 3, 2017 at 9:13 PM, shahzaib mushtaq <shahzaib.cb@gmail.com>
> wrote:
>
>> Hi,
>>
>> >>As far as I know, there are about half a dozen "latest" versions of
>> Google Chrome, and none of them are version 64 currently.
>>
>> Your're right sorry, the version latest is 60.
>>
>>
>> >>You have one client that reports an error message.What are the
>> specific circumstances under which that version of that
>> client can report that error message? That information may give a hint
>> as to where the problem is.
>>
>> Well, i can generate this issue without a problem all i've to do is
>> create a test.html page, put 5 x static video links (our server http2 mp4
>> video links) and play them simultaneously. For the first request they'll
>> start playing with *200* status in inspect element under *Network *tab
>> but for further chunk requests from chrome, it'll stuck in *pending *and
>> under *Console *tab spdy error will start to occur. Once i've disabled
>> HTTP2 that issue is gone but 'pending' status issue still was there which i
>> think is linked with my below issue :
>>
>> ------------------------------------------------------------
>> ----------------
>>
>> Now we think there's issue with one SSL certificate which we renewed
>> recently. Our server has actually two different domain SSL certificates
>> configured on same ip;
>>
>> *.mydomain.com
>> *.yourdomain.com (*Renewed*)
>>
>> We've configured both these certificates vhosts in
>> /usr/local/etc/nginx/vhosts/ directory. After installing certificate we
>> tested it with sslshopper and both were installed properly (CN,
>> Intermediate Chain etc were properly listed for each).
>>
>> Now here is the twist comes. Recently we've renewed the SSL certificate
>> for **.yourdomain.com http://yourdomain.com* from *Godaddy *and after
>> that sslshopper shows correct CN and intermediate chain for new certificate
>> (*.yourdomain.com) but openssl is showing the CN of *.yourdomain.com as
>> of *.mydomain.com.
>>
>> I repeat SSLshopper and SSLLabs shows proper CN (common name) but if i
>> use openssl command to verify it :
>>
>> [root@cw012 /usr/ports/security/ca_root_nss]# openssl s_client -connect
>> s4.yourdomain.com:443 |head -30depth=2 C = US, O = GeoTrust Inc., OU =
>> (c) 2008 GeoTrust Inc. - For authorized use only, CN = GeoTrust Primary
>> Certification Authority - G3verify return:1s_clidepth=1 C = US, O =
>> GeoTrust Inc., CN = RapidSSL SHA256 CA - G2verify return:1head depth=0 CN = **.mydomain.com
>> http://mydomain.com*
>>
>> Here you can see that CN is *.mydomain.com instead of *.yourdomain.com.
>>
>> ==============================================
>>
>> Now for testing i had disabled vhost for yourdomain.com and used only
>> single mydomain.com after which requests for serving files improved
>> drastically before that, if we would had hit a page, it'll first go to
>> 'pending' status in chrome inspect element and after few time it'll show
>> 200 status but now it goes directly to 200 status.
>>
>> I'm really confused on what's happening right now but if someone has
>> faced this experience before please let me know, on first i thought there
>> could be nginx config issue but the problem is SSLshopper and ssllabs are
>> showing proper CName so now i think maybe its related to chrome
>>
>>
>> Thanks for your help.
>> Shahzaib
>>
>>
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free.
>> www.avast.com
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
>> <#m_-2776267015937845177_m_1565204697939808308_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> On Thu, Aug 3, 2017 at 12:27 PM, Francis Daly <francis@daoine.org> wrote:
>>
>>> On Wed, Aug 02, 2017 at 01:17:06PM +0500, shahzaib mushtaq wrote:
>>>
>>> Hi there,
>>>
>>> > 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 ?
>>>
>>> You have one client that reports an error message.
>>>
>>> What are the specific circumstances under which that version of that
>>> client can report that error message? That information may give a hint
>>> as to where the problem is.
>>>
>>> Is the problem repeatable? As in: if you do a fresh install with no
>>> historical information of the client browser (a new "profile" or under
>>> a new user account), do you see the same behaviour?
>>>
>>> In a later mail, you suggest that you have two test nginx instances,
>>> and one client reports the error against one instance and not against
>>> the other.
>>>
>>> "nginx -V" on each could be used to identify any differences in the
>>> compile-time settings. "nginx -T" on each could be used to identify any
>>> difference in the run-time configuration.
>>>
>>> > 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.
>>>
>>> As far as I know, there are about half a dozen "latest" versions of
>>> Google Chrome, and none of them are version 64 currently.
>>>
>>> If you ask for help in a Google Chrome mailing list, you may want to
>>> provide the specific version number there to allow them to identify what
>>> exactly you are running.
>>>
>>> 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
shahzaib mushtaq
Re: ERR_SPDY_PROTOCOL_ERROR Nginx !!
August 04, 2017 01:20PM
Hi,

Guys is there anything i am missing with SSL for multiple vhosts due to
which the vhost Order is overlapping the other one ?

Shahzaib

On Fri, Aug 4, 2017 at 2:12 AM, shahzaib mushtaq <shahzaib.cb@gmail.com>
wrote:

> I've noticed that its related to the orders of virtual host files. For
> example if vhost of mydomain.com comes first than yourdomain.com then SSL
> CN (common name) for both domains will be *.mydomain.com.
>
> And if vhost of yourdomain.com comes before than mydomain.com then common
> name for both domains is yourdomain.com .
>
>
>
> On Fri, Aug 4, 2017 at 2:01 AM, shahzaib mushtaq <shahzaib.cb@gmail.com>
> wrote:
>
>> Update:
>>
>> Now i removed vhost for mydomain.com and yourdomain.com is now showing
>> correct Common name. So there's some kind of overlapping in vhosts.
>>
>>
>>
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free.
>> www.avast.com
>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
>> <#m_6887420271712490320_m_-2776267015937845177_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>
>> On Thu, Aug 3, 2017 at 9:13 PM, shahzaib mushtaq <shahzaib.cb@gmail.com>
>> wrote:
>>
>>> Hi,
>>>
>>> >>As far as I know, there are about half a dozen "latest" versions of
>>> Google Chrome, and none of them are version 64 currently.
>>>
>>> Your're right sorry, the version latest is 60.
>>>
>>>
>>> >>You have one client that reports an error message.What are the
>>> specific circumstances under which that version of that
>>> client can report that error message? That information may give a hint
>>> as to where the problem is.
>>>
>>> Well, i can generate this issue without a problem all i've to do is
>>> create a test.html page, put 5 x static video links (our server http2 mp4
>>> video links) and play them simultaneously. For the first request they'll
>>> start playing with *200* status in inspect element under *Network *tab
>>> but for further chunk requests from chrome, it'll stuck in *pending *and
>>> under *Console *tab spdy error will start to occur. Once i've disabled
>>> HTTP2 that issue is gone but 'pending' status issue still was there which i
>>> think is linked with my below issue :
>>>
>>> ------------------------------------------------------------
>>> ----------------
>>>
>>> Now we think there's issue with one SSL certificate which we renewed
>>> recently. Our server has actually two different domain SSL certificates
>>> configured on same ip;
>>>
>>> *.mydomain.com
>>> *.yourdomain.com (*Renewed*)
>>>
>>> We've configured both these certificates vhosts in
>>> /usr/local/etc/nginx/vhosts/ directory. After installing certificate we
>>> tested it with sslshopper and both were installed properly (CN,
>>> Intermediate Chain etc were properly listed for each).
>>>
>>> Now here is the twist comes. Recently we've renewed the SSL certificate
>>> for **.yourdomain.com http://yourdomain.com* from *Godaddy *and after
>>> that sslshopper shows correct CN and intermediate chain for new certificate
>>> (*.yourdomain.com) but openssl is showing the CN of *.yourdomain.com as
>>> of *.mydomain.com.
>>>
>>> I repeat SSLshopper and SSLLabs shows proper CN (common name) but if i
>>> use openssl command to verify it :
>>>
>>> [root@cw012 /usr/ports/security/ca_root_nss]# openssl s_client
>>> -connect s4.yourdomain.com:443 |head -30depth=2 C = US, O = GeoTrust
>>> Inc., OU = (c) 2008 GeoTrust Inc. - For authorized use only, CN = GeoTrust
>>> Primary Certification Authority - G3verify return:1s_clidepth=1 C = US, O =
>>> GeoTrust Inc., CN = RapidSSL SHA256 CA - G2verify return:1head depth=0 CN = **.mydomain.com
>>> http://mydomain.com*
>>>
>>> Here you can see that CN is *.mydomain.com instead of *.yourdomain.com.
>>>
>>> ==============================================
>>>
>>> Now for testing i had disabled vhost for yourdomain.com and used only
>>> single mydomain.com after which requests for serving files improved
>>> drastically before that, if we would had hit a page, it'll first go to
>>> 'pending' status in chrome inspect element and after few time it'll show
>>> 200 status but now it goes directly to 200 status.
>>>
>>> I'm really confused on what's happening right now but if someone has
>>> faced this experience before please let me know, on first i thought there
>>> could be nginx config issue but the problem is SSLshopper and ssllabs are
>>> showing proper CName so now i think maybe its related to chrome
>>>
>>>
>>> Thanks for your help.
>>> Shahzaib
>>>
>>>
>>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon Virus-free.
>>> www.avast.com
>>> https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link
>>> <#m_6887420271712490320_m_-2776267015937845177_m_1565204697939808308_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
>>>
>>> On Thu, Aug 3, 2017 at 12:27 PM, Francis Daly <francis@daoine.org>
>>> wrote:
>>>
>>>> On Wed, Aug 02, 2017 at 01:17:06PM +0500, shahzaib mushtaq wrote:
>>>>
>>>> Hi there,
>>>>
>>>> > 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 ?
>>>>
>>>> You have one client that reports an error message.
>>>>
>>>> What are the specific circumstances under which that version of that
>>>> client can report that error message? That information may give a hint
>>>> as to where the problem is.
>>>>
>>>> Is the problem repeatable? As in: if you do a fresh install with no
>>>> historical information of the client browser (a new "profile" or under
>>>> a new user account), do you see the same behaviour?
>>>>
>>>> In a later mail, you suggest that you have two test nginx instances,
>>>> and one client reports the error against one instance and not against
>>>> the other.
>>>>
>>>> "nginx -V" on each could be used to identify any differences in the
>>>> compile-time settings. "nginx -T" on each could be used to identify any
>>>> difference in the run-time configuration.
>>>>
>>>> > 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.
>>>>
>>>> As far as I know, there are about half a dozen "latest" versions of
>>>> Google Chrome, and none of them are version 64 currently.
>>>>
>>>> If you ask for help in a Google Chrome mailing list, you may want to
>>>> provide the specific version number there to allow them to identify what
>>>> exactly you are running.
>>>>
>>>> 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
Sorry, only registered users may post in this forum.

Click here to login