Having issues with the dreaded ERR_SPDY_PROTOCOL_ERROR error in Google Chrome? The ERR_SPDY_PROTOCOL_ERROR error has become an unfortunate error on WordPress sites using nginx or Cloudflare.
While browsing a WordPress website, you get a ERR_SPDY_PROTOCOL_ERROR. You are no longer able to browse the website only to encounter an ERR_SPDY_PROTOCOL_ERROR. You try another browser, and the issue is isolated to Google Chrome.
This issue is problematic for both WordPress site owners and visitors alike. The SPDY Protocol was developed by Google to reduce page loading time. However, it was discontinued due to HTTP 2 vulnerability.
While Google supposedly has resolved this issue by updating Google Chrome, this issue is not completely resolved and the issue may still linger even after having updated your Google Chrome browser.
Here are some solutions to temporarily (in some cases permanently) eradicate this nuisance.
First solution is to try updating your Google Chrome browser. To do so, go to settings > About Google Chrome. The browser should update itself.
If the issue persists, try flushing Socket. To do so, enter the following in your Google Chrome address bar:
You will find a button called Flush socket pools. Click on it to flush the socket. After doing that, restart your browser and try opening the same website.
If this does not work. Clear your browser cache. To do this, go to settings > More tools > Clear browsing data > Clear cookies and browsing data.
If you are using 3rd party Internet security program, try disabling HTTPS scanning in your antivirus or firewall.
If the solution continues to persist, you can also try flushing DNS cache (in command line ipconfig /flushdns) or reset Google Chrome settings (type Chrome://flags in the address bar and hit Enter. Look for the Enable Reset Profile Settings flag and click on the Enable link.)
If all else faces, use and alternate browser and contact the admin of the site to make sure they are off Google Page Speed or to contact their host to help resolve the issue (if you want to take it that far).