The current workaround is to change the SSL Cipher Suite On Tue, Aug 1, 2017 at 5:37 PM shahzaib mushtaq <shahzaib...@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.skylinehost...@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...@gmail.com> >> wrote: >> >> Hi, >> >> This error is mostly coming on google chrome. :( >> >> Shahzaib >> >> On Tue, Aug 1, 2017 at 8:51 PM, Etienne Robillard <tkad...@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 <fran...@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 fran...@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
