It worked great for me. Here is the reference link if you think i made this up myself. -
This tutorial is for setting up everything from scratch… The idea to use EE is to avoid doing all of this. I used EE’s famous 2 line installation on all my websites - And everyone runs smooth but the one I made yesterday. IF you can help me with that I would really be thankfull…
Tried this as well - Nginx does not restart after this. I copy pasted this exact cipher after ssl_ciphers and before ; but after saving nginx does not restart.
then u have done something else. share your nginx config file
What’s your sudo nginx -t says?
or
sudo cat /var/log/nginx/error.log says?
1- Nowadays, all nginx configs needed IPv4 and IPv6 settings. If you have listen 80; into a line, then you need listen [::]:80; also. Keep it simple. Unfortunately, none redirect or domain .conf file brings it.
2- Since nginx 1.10 stable branches, we have http2 support by default. So, you do not need to remove http2 from listen line.
3- After item 2 above, check 443 part of config file at server { ... statements about 443 port and more ... }, improve your ciphers and give compatibility or not with old browsers.
https://mozilla.github.io/server-side-tls/ssl-config-generator/
https://raymii.org/s/tutorials/Strong_SSL_Security_On_nginx.html
1 Like
I think so …
-t says line of ssl_cipher has some issues (basically i had copied the above mentioned ciphers to my ssl.conf and post that nginx would not start)…
please remove the one on ssl.conf and place the ssl_cipher only on nginx.conf
Same error caused to me.
And I replace ssl_cipher with this one
ssl_ciphers 'ECDHE-RSA-AES128-GCM-SHA256:AES256+EECDH:AES256+EDH';
and problem resolved.
3 Likes
Well, Identified the issue deeply and it occurs frequently in Internet Browsers due to some uncommon reasons. I have listed down all the possible solutions and 99% your issue is going to resolve from one of the solution. Try them one by one and do reply which solution solved your issue.
Solutions Page: How to Solve Google Chrome’s Error “ERR_SPDY_PROTOCOL_ERROR"
Try clearing the cache and restart the chrome. I always do this and it works every time. take a look at some more solutions: How To Fix Chrome’s ERR_SPDY_PROTOCOL_ERROR
One of the most common problems that we face while using Google Chrome is the error " ERR_SPDY_PROTOCOL_ERROR ". You may encounter this issue while browsing certain pages on the browser.Refer the artical : ERR_SPDY_PROTOCOL_ERROR
There are many ways to fix this error, You can any one and can fix very easily, Mostly it can fix by
- Updating Google Chrome Browser
- Flush the Socket Solution
- Clear Cookies
- Restart Browser If still problem not solve then try manually for more fixes.
Perhaps try to change your current SSL Cipher with these:
https://mozilla.github.io/server-side-tls/ssl-config-generator/
I had one of my sites suddenly go down with a SPDY_PROTOCOL_ERROR, all my other sites were operational so I knew 100% it was nothing to do with any certificate problem.
I eventually traced it to a permissions problem with the location for the nginx fastcgi cache. A simple chown -R www-data:www-data on the /var/cache/nginx folder resolved it for me immediately. Hopefully this may help someone in future.
Hi, Mahendra meghwal Your suggestion really working for me. I find that mostly it is happen due to cookies and also Antivirus. I found also a good site where you can find right fixes. Thanks
This is also happen due to Anti Virus, If you are using Avast Safe sure it will due to this. You can try it via disable.
I am facing this error many times. i jusy found some simple solution to resloved this error here. few normal steps write about here
100% working try this fix