How To Fix the ERR_HTTP2_PROTOCOL_ERROR
How To Fix the ERR_HTTP2_PROTOCOL_ERROR
Get back to your normal browsing experience in no time with this handy guide 🛠
👉 Subscribe: https://www.youtube.com/c/Kinsta?sub_…
Using the HTTP/2 Network Protocol, you can reach websites faster than ever before. However, you may stumble across an err_http2_protocol_error. This can prevent you from accessing certain web pages.
Fortunately, there are many solutions for the HTTP/2 protocol error. Whether you fix the problem within your browser or operating system, you can easily remove this troublesome message. Then, you can continue with your normal online browsing.
In this video, we’ll introduce you to the err_http2_protocol_error and its causes. Then, we’ll show you how to fix this problem on both a browser and a personal device.
ℹ️ About Kinsta
Kinsta provides Application, Database, and Managed WordPress Hosting. Powered by Google Cloud Platform’s premium tier network and compute-optimized C2 virtual machines, Kinsta delivers enterprise-level security, a free CDN global edge network with 200+ PoPs, and 24/7/365 support.
🚀 Don’t let unnecessarily complicated and underperforming hosts delay your projects. Explore our plans and resource-based pricing to find the perfect fit to run your applications, databases, or WordPress sites ► https://kinsta.com/plans/
💡Learn more about Kinsta’s hosting solutions:
👉Application Hosting: https://kinsta.com/application-hosting/
👉Database Hosting: https://kinsta.com/database-hosting/
👉Managed WordPress Hosting: https://kinsta.com/wordpress-hosting/
👤Follow us:
► https://kinsta.com/blog/
► https://kinsta.com/newsletter/
► https://twitter.com/kinsta
► https://instagram.com/kinstahosting
► https://facebook.com/kinstahosting
🕘Timestamps
0:00 Intro
1:18 Update Your Browser
2:06 Clear Your Browser Data
3:09 Open a Private or Incognito Browser Window
3:59 Disable or Uninstall Browser Extensions
4:39 Turn Off the Browser’s QUIC Protocol
5:31 Restore the Browser’s Default Settings
6:43 Reinstall Google Chrome
7:57 How To Fix the err_http2_protocol_error In a Device
8:07 Reset Your Device’s Date and Time
9:00 Update Your Operating System
9:49 Flush the DNS
10:39 Check Antivirus Software
📚 Resources
🛠 How To Fix the ERR_HTTP2_PROTOCOL_ERROR
► https://kinsta.com/knowledgebase/err_…
#browsererror
Content
0 -> Hey there, I'm Mike, and today I'm going to
1.86 -> show you how to fix the HTTP/2 protocol error.
5.664 -> (upbeat music)
11.911 -> Using the HTTP/2 network protocol
14.04 -> you can reach websites faster than ever before.
16.95 -> However, you may stumble
18.18 -> across an error HTTP/2 protocol error.
21.54 -> This can prevent you from accessing certain webpages.
24.45 -> With the help of this video
25.59 -> you can easily remove this troublesome message
27.87 -> and continue with your normal online browsing.
30.57 -> But before we get started, I wanna let you know
32.55 -> that there'll be links to more resources
34.32 -> in the video's description below and remember
36.84 -> subscribe and ring that bell to get notifications
39.06 -> for future helpful content.
40.47 -> Now let's fix this protocol error in a browser.
46.92 -> Once you receive this error
48.15 -> you can start troubleshooting to find the source
49.95 -> of the issue
50.85 -> although we'll fully discuss some method you can use.
53.19 -> There are some simple fixes that you can start with.
55.47 -> First, try refreshing the webpage heading F five
58.38 -> on your keyboard.
59.213 -> While send a request with an if modified since header.
62.52 -> If the site was temporarily down
64.23 -> this may solve the problem.
65.28 -> Alternatively
66.174 -> you can visit the site using a different browser.
68.55 -> You may also want to close some tabs
70.32 -> if there are too many open.
71.79 -> If the error persists, continue with the following methods.
75.06 -> If you're making searches with that outdated browser
77.4 -> this can easily lead to an HTTP/2 protocol error.
80.88 -> This is because your browser's data packets are incompatible
83.79 -> with the site you're trying to load.
85.53 -> To fix this problem
86.55 -> you can update your browser using Google Chrome.
88.92 -> You can simply click on the three dot icon
91.2 -> in the upper right hand corner
92.49 -> and select update Google Chrome.
95.16 -> If you don't see this button
96.33 -> your browser is likely already up to date, to check.
99.36 -> If this is the case, go to help then about Google Chrome.
102.69 -> This will prompt Google Chrome to check for a new update.
105.72 -> If there is one, it will automatically install it.
108.45 -> To finish updating, you need to relaunch the browser.
111.06 -> If you're using the Google Chrome mobile app
113.1 -> you can simply open the app store or play store
115.56 -> depending on your device type.
117.24 -> Then check for any app updates and install them.
120.48 -> Whenever you experience issues during the rendering process
123.18 -> it's a good idea to clear your browser data
125.55 -> by clearing your cache, cookies and history.
127.95 -> You can enable visited websites to authenticate your device
130.86 -> and fulfill the request.
132.54 -> Depending on your browser
133.68 -> there are a few different ways to clear the cache.
135.78 -> For Google Chrome.
136.71 -> You can select more tools then clear browsing data.
139.89 -> Using the pop-up window
141.18 -> you can specify the information you want to clear.
143.73 -> You'll want to be sure to select cached images and files
146.438 -> but you can also get rid
147.96 -> of your browsing history, cookies and other data.
150.81 -> If you're using Safari, it will be a similar process.
153.81 -> To do this, go to Safari and then Clear History.
156.69 -> Then you can choose to clear your cache, cookies
159.15 -> and site data from a specific time range.
161.88 -> When you're done, click on clear history.
164.19 -> To clear your browser data on Mozilla Firefox.
166.89 -> You need to find the hamburger icon
168.66 -> in the upper right hand corner.
170.04 -> Next, select history.
171.51 -> In the new tab, click on clear recent history.
174.21 -> Like other browsers
175.2 -> you can choose only to clear certain data.
177.45 -> However it's important to remember to select
179.73 -> the cache option.
180.96 -> Now that you've cleared your browser cache
182.61 -> try to visit the website where the error occurred.
185.04 -> If you still see the error message
186.63 -> you'll need to try some alternative solutions.
188.73 -> Whenever you visit a new website
190.2 -> your browser will save information
191.94 -> about that site in a cache.
193.89 -> Once you visit the page again
195.24 -> your browser will pull that cache data rather
197.64 -> than requesting the server all over again.
199.89 -> Often this can make the site load faster on repeat visits.
203.19 -> For this reason
204.023 -> you may want to avoid clearing your browser cache
206.31 -> when trying to bypass the HTTP/2 protocol error.
209.72 -> In this case, you can launch the browser
211.74 -> in private or incognito mode.
214.11 -> This can be an effective one-time solution to
216.27 -> avoid permanently deleting the cache
218.4 -> or disabling third party extensions.
220.41 -> To do this in Google Chrome
221.85 -> extend the menu and click on new incognito window.
224.88 -> This will open a private browser using the incognito mode.
228.21 -> Try to visit the website again and may enable you to do this
231.24 -> without having to use more complicated solutions.
233.73 -> However, keep in mind this is primarily a short-term fix.
237.42 -> As we mentioned earlier
238.35 -> third party extensions could potentially interfere
240.84 -> with how your browser and webpage interact.
243.36 -> After you see the error message
244.65 -> you can consider disabling these extensions to see
247.08 -> if the error disappears.
249.03 -> To do this
249.863 -> in Google Chrome visit more tools and then extensions.
252.84 -> This will take you
253.673 -> to a webpage that lists your Google Chrome extensions.
256.23 -> First, use the switches
257.58 -> on the bottom right corner to turn off each extension.
260.34 -> Now that your extensions are disabled
262.14 -> try to go to the webpage that caused the error.
264.45 -> If the webpage loads, you know
266.04 -> that one of your extensions caused the problem.
268.47 -> Now you can go back
269.303 -> to the extension page and enable them one by one.
272.07 -> After you turn on an extension, see if the error returns.
275.25 -> When you find the problematic extension
277.23 -> consider removing it entirely.
278.94 -> Quick UDP internet Connections is an encrypted transport
282.24 -> network protocol that was developed by Google.
284.64 -> Essentially, its goal was to increase the speed, security
287.85 -> and efficiency of HTTP traffic.
290.07 -> Currently, only 8% of websites use QUIC.
293.1 -> Therefore, when sites aren't configured to process this kind
295.95 -> of traffic, it can cause incompatibility
298.11 -> between the client and the server.
300.24 -> As a result, this can display an HTTP/2 protocol error.
304.02 -> To solve this problem, you can turn
305.7 -> off the QUIC protocol in your browser within Chrome.
308.185 -> You'll simply need to enter the following URL
310.83 -> into your search bar.
311.85 -> Now you'll see a highlighted result labeled
313.92 -> Experimental QUIC protocol for this setting
317.01 -> change it to disabled.
318.63 -> Once you make this change
319.8 -> you'll need to relaunch your browser.
321.75 -> This will disable QUIC allowing you to
323.52 -> view the incompatible website.
325.11 -> As you use Google Chrome, you may not notice small
327.72 -> glitches that can change its default settings over time.
330.87 -> This can lead to more errors
332.43 -> like the HTTP/2 protocol error.
335.1 -> Fortunately, you can get your browser back
337.38 -> to normal by reverting its settings to the default options.
340.59 -> To get started
341.52 -> open the Google Chrome settings page on the left.
344.46 -> Find the reset settings tab.
346.38 -> Then select the restore settings
348.36 -> to their original default options.
350.19 -> Finally, you'll just need to confirm
351.93 -> that you want to erase your current Chrome settings.
354.24 -> If you do click on reset settings, it's important to keep
357.6 -> in mind that this will erase your current search
359.55 -> engine history, startup page
361.53 -> pin tabs, extensions, bookmarks, and more.
365.04 -> It will essentially revert your browser to a clean slate.
367.83 -> However, it can remove any conflicting software
370.35 -> or settings that are causing the HTTP/2 protocol error.
373.95 -> You can also consider resetting the experimental settings
376.56 -> in your browser.
377.94 -> These are not fully tested functional features
380.13 -> so they could prevent your browser
381.42 -> from communicating properly with a website.
383.85 -> To find your advanced experimental settings
385.98 -> search for the following address.
387.75 -> In the upper right hand corner, select the reset all option.
391.47 -> If certain features that were accidentally enabled
393.72 -> this will revert them to the default settings.
395.82 -> Then these changes will be applied whenever
398.1 -> you relaunch Chrome.
400.257 -> After executing all these methods
401.25 -> you may still see the Troublesome HTTP/2 protocol error.
404.85 -> If so, there could be an error within the Google Chrome app.
408.75 -> Even if you restore the default settings
410.76 -> you may want to consider reinstalling the entire browser.
414 -> First, you'll need to delete the browser from your device.
417.12 -> To do this with a Mac OS operating system
419.52 -> open the applications folder
421.02 -> and move the Google Chrome app to the trash.
423.78 -> You'll also want to delete any Chrome software
425.91 -> updates, to find them.
427.5 -> Search for your library folder
429.06 -> and then the Google folder on your device in your results
432.06 -> delete the Google software update folder.
434.49 -> If you're a Windows user
435.78 -> you'll use different steps to delete Chrome.
437.97 -> To start, click on the Windows start button
440.22 -> and search for the control panel.
442.32 -> Open it.
443.153 -> Then find the programs option.
444.93 -> Click on uninstall a program under programs.
447.57 -> Now you'll need to find Google Chrome and right click on it.
450.96 -> Lastly, hit uninstall for both Mac and Windows users.
455.04 -> You can reinstall Chrome in the same way.
457.26 -> You'll simply need to download the file included
459.39 -> on the Google Chrome website.
460.98 -> Although this method could potentially
462.63 -> solve the HTTP/2 protocol error
465.33 -> it's best only to use it as a last resort.
468.06 -> Deleting Chrome will also remove any of its data
470.82 -> so be sure to try a few simpler solutions beforehand.
476.91 -> Now let's discuss how to make your device compatible
480.09 -> with the HTTP/2 protocol.
482.07 -> Although it may not seem like a big deal
483.9 -> it's important to have the correct date
485.7 -> and time displayed on your device.
487.86 -> If this information isn't accurate
489.66 -> the incorrectly timestamped data packets could be refused.
493.05 -> This can lead to an error HTTP/2 protocol error
496.2 -> with a Windows operating system.
498.03 -> You can right click on the clock
499.47 -> in the bottom right hand corner of your desktop.
501.72 -> Then select adjust date and time.
503.82 -> If your computer isn't automatically
505.213 -> displaying the right time, you'll need to
507.54 -> disable the set time automatically setting beneath this.
511.14 -> Be sure to set the correct time zone.
513.18 -> Next, select the change button to set the date
516 -> and time manually, in the pop-up window.
518.28 -> Enter the correct date and time, for Mac users.
520.83 -> Click on the Apple menu.
522.42 -> Then select system preferences here.
524.94 -> Find the date and time option in the bottom left corner.
528 -> Click on the lock to make changes.
530.16 -> Now you can deselect the set date
531.99 -> and time automatically option
533.58 -> and choose the correct values.
535.47 -> After you make these changes, try relaunching the webpage.
538.65 -> If you haven't updated your device in a while
540.87 -> this can cause a multitude of performance issues.
543.75 -> To ensure you can avoid any conflicts
545.76 -> between your operating system and visited websites
548.16 -> you'll need to check
549 -> for recent upgrades using a Mac OS device.
551.82 -> You can start by performing a backup.
553.77 -> Then go to system preferences, then to software update.
557.85 -> In this window, you'll see any newly available updates.
561.27 -> If you're ready to install them, click on update.
563.7 -> Now with a Windows computer, you can navigate to start then
567.36 -> to settings, and then Windows update.
570 -> If you haven't already, install the latest update.
572.88 -> Once your device is up to date
574.56 -> it should be compatible with most websites
576.51 -> that you want to visit, to see if this is the case.
579.12 -> Check whether the protocol error is fixed.
581.58 -> If not, continue with the following methods,
584.28 -> on the internet, the DNS functions as an index
586.95 -> for all available websites and their unique IP addresses.
590.4 -> When you visit a website, your operating system
592.59 -> or browser will save this information in a database.
596.1 -> This can lead to faster loading times on revisited websites.
599.16 -> If you're seeing the HTTP/2 protocol error
601.86 -> you can try flushing your DNS cache.
604.32 -> Put simply.
605.153 -> This will erase the IP addresses and other DNS data
608.07 -> from your computer, to flush a Mac DNS cache
611.19 -> open the command line interface called terminal
613.83 -> and this window enter the following command.
616.65 -> This should successfully clear the DNS removing
619.41 -> the HTTP/2 protocol error.
621.81 -> However, keep in mind
623.16 -> that you'll need to use slightly different processes
625.29 -> for older versions of Mac OS.
627.42 -> If you have Windows 10, 8, 7 or XP.
630.87 -> you can start by opening command prompt.
632.91 -> In the command line.
634.08 -> Put this command.
635.61 -> You should see a confirmation message.
637.08 -> Once the DNS has been flushed, to keep your computer safe
640.23 -> while you're browsing
641.4 -> you likely have an antivirus program installed.
644.28 -> Although this software offers many security benefits
647.22 -> it can occasionally flag certain applications as malicious.
650.67 -> When this happens, it may unnecessarily limit your access
653.64 -> to a website if none of the previous methods worked.
656.43 -> You can check your antivirus software to see
658.59 -> if it's functioning properly.
660.06 -> First, open your notifications
662.07 -> which can display new security issues.
664.26 -> Most antivirus software will also have a quarantine list.
667.44 -> This will contain all of the detected security threats
670.47 -> on your computer, and either of these areas evaluate
673.53 -> whether any unwanted applications are being flagged.
676.38 -> If so
677.213 -> you may need to temporarily disable your antivirus software.
681.99 -> Kinsta's WordPress hosting can speed
683.7 -> up your website by up to 200%, and you'll get 24/7 support.
687.54 -> From our expert WordPress engineers
689.67 -> we offer two months free with any annual plan
692.52 -> a 30 day money back guarantee
694.29 -> and unlimited free basic migrations from any host.
697.8 -> Head over to Kinsta.com/plans to get started.
701.52 -> Thank you so much for watching.
703.14 -> If you found this video helpful
704.7 -> please don't forget to like, subscribe
707.1 -> and hit that notification bell
708.48 -> for more tutorials, explainers
710.43 -> and helpful content like this.
713.15 -> (upbeat music)
Source: https://www.youtube.com/watch?v=Fm-_jxRiOw0