Chrome network error · -356 · HTTP
ERR_QUIC_PROTOCOL_ERROR
Chromium's description
There is a QUIC protocol error.
Chrome shows it as net::ERR_QUIC_PROTOCOL_ERROR, error -356. puppeteer and Playwright report the same name when a page fails to load in Chromium.
Common causes
- A firewall, router or antivirus blocks or mangles UDP on port 443.
- A VPN or proxy that does not support QUIC.
- A browser extension or experimental Chrome flag.
- A temporary problem on the site’s CDN.
How to fix ERR_QUIC_PROTOCOL_ERROR
- Reload; Chrome often falls back to HTTP/2 over TCP.
- Turn off the VPN or proxy and the antivirus web shield.
- Disable extensions to find one that interferes.
- As a last resort, turn QUIC off at
chrome://flags/#enable-quic.
ERR_QUIC_PROTOCOL_ERROR in the screenshot API
The renderer has QUIC switched off: it talks HTTP/1.1 and HTTP/2 over TCP only, so a screenshot or PDF of the page does not fail with this error.
Only the page's own load can fail a render. An image, script or frame of the page that fails with a network error does not: the page is captured as the browser shows it without that resource.
Check whether a website loads
Frequently asked questions
What does ERR_QUIC_PROTOCOL_ERROR mean?
How do I fix ERR_QUIC_PROTOCOL_ERROR?
Is a screenshot that fails with ERR_QUIC_PROTOCOL_ERROR billed?
Other common errors
Screenshot API
Take screenshots from your code
screenshotbase renders any website in a real browser and returns the image: full page or viewport, any device size, retina, from 100+ countries, with cookie banners and ads hidden.
/v1/take documentation Screenshot API All documentation
300 free screenshots every month. No credit card required.
GET https://api.screenshotbase.com/v1/take?url=https://example.com&full_page=true
# Response: the image (PNG, JPG, WebP or GIF)
curl -G "https://api.screenshotbase.com/v1/take" \
--data-urlencode "url=https://example.com" \
-d viewport_width=1280 -d viewport_height=800 \
-d format=png \
-H "apikey: YOUR-API-KEY" \
-o screenshot.png