ERR_SPDY_PROTOCOL_ERROR is a Google Chrome browser error which you can face for many reasons. Here I’m going to give you the exact cause of the issue and how to solve the ERR_SPDY_PROTOCOL_ERROR in Chrome Browser. Sometimes clearing the cache on browser or windows may fix the problem.
Fix Chrome’s ERR_SPDY_PROTOCOL_ERROR
The below solutions will fix the problem on Google Chrome permanently. If a single method doesn’t work, be sure to apply all the methods as mentioned below.
Clear Chrome’s DNS
You can particularly clear Chrome’s DNS without clearing the Windows from CMD. Copy the below URL and paste it into Chrome’s address bar and hit the enter button:
Now click the Clear host cache button, and it may fix the problem.
Flush Socket Pools
If the above method doesn’t work for you, flush the socket pools by following the below method.
To clean Flush Socket Pools, all you need to do is copy the below URL and paste it into your browser’s address bar and it the enter button:
Once you are on the Socket pools page, click on Flush socket pools button and you are all done.
Clear Chrome’s Cookies
To clear Chrome’s cookies copy the below address and paste it into your browser’s address bar and hit the enter button:
Now select only the Cookies and other sites and plugin data and hit the Clea browsing data button.
Clear Chrome’s Cache
You can clear the Chrome’s cache just the way you cleared the cookies of the browser. In this case, all you need to do is select the Cache images and files except Cookies.
If you are using Avast Antivirus
Avast Antivirus can also block you from accessing websites, and if you are using Avast, you much check the following settings and make changes.
- At first, open Avast in your desktop
- Click on Settings
- Click on Active Protection
- Now click on Customize for Web Shield Protection
- Now add each website separately to the URLs to exclude section and save it.
That’s how you can fix the ERR_SPDY_PROTOCOL_ERROR in Google Chrome. If you continue facing the issue feel free to leave a comment below and I’ll try to find an alternative way to fix the issue for you. You can also try adding Google DNS to your network connection and check whether it fixes the issue or now, Google DNS are 220.127.116.11 and 18.104.22.168.