Featured AI Products
Compute
Build, deploy, and scale cloud compute resources
Containers and Images
Safely store and manage containers and backups
Managed Databases
Fully managed resources running popular database engines
Management and Dev Tools
Control infrastructure and gather insights
Networking
Secure and control traffic to apps
Security
Help protect your account and resources with these security features
Storage
Store and access any amount of data reliably in the cloud
Browse all products
AI/ML
CMS
Data and IoT
Developer Tools
Gaming and Media
Hosting
Security and Networking
Startups and SMBs
Web and App Platforms
See all solutions
Community
Documentation
Developer Tools
Get Involved
Utilities and Help
Become a Partner
Marketplace
Pricing

- Community
- DigitalOcean
- Community
- DigitalOcean

Chrome console error "net::ERR_HTTP2_PROTOCOL_ERROR 200". Some site's content doesn't available.

Posted on April 30, 2020

Hello! I am getting error on opening my site. Here are the examples:

GET https://houseville.villas/fonts/Montserrat-Regular.woff2
net::ERR_HTTP2_PROTOCOL_ERROR 200

GET https://houseville.villas/styles/welcome-tour.css
net::ERR_ABORTED 404

The errors only relate to site resources like css and js. The error appeared on May-29 and somehow solved without any actions from my side. It just appeared again.

Thanks for you answer!

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby

May 2, 2020

Hi there @secretdeals,

There are a few things which could be causing this issue:

Make sure there is enough space on the Droplet, you can do that by running the df -h command
After some research, it looks like that there was a bug report and it is being fixed at the moment:

https://chromium-review.googlesource.com/c/chromium/src/+/2001234

I’ve not been able to recreate the problem myself but some people report that making the following changes to their Nginx server blocks fixed the problem:

gzip on;
add_header 'Cache-Control' 'no-store, no-cache, must-revalidate, proxy-revalidate, max-age=0';
expires off;

Make sure to run an Nginx config test before restarting the service:

nginx -t

If you get syntax is ok, then go ahead and restart the service.

Let me know how it goes! Regards, Bobby

The developer cloud

Scale up as you grow — whether you're running one virtual machine or ten thousand.

View all products

Start building today

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.