NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR while trying to connect using cloudflare DNS.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
index-B19rbAfn.css:1 Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR index-nLqQo6ej.js:1 Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR
I have errors like that in chrome console with all of hosts and all of settings. Page usually load only html without css and other features.
I'm using ssl cert through cloudflare that were setup properly because my site proxies properly when i use additional nginx container in setup but other services like nextcloud, portainer and others have the same errors .
Maybe the main issue is that nginx-proxy-manager setup located in Russia and it connects to our stupid limitations from ISP
I'll be very glad to hear any ideas to fix it.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Chrome console errors for index-B19rbAfn.css and index-nLqQo6ej.js, then compare the Cloudflare SSL/DNS path with the Nginx Proxy Manager and additional nginx container setup described in the report. Done means proxied services load CSS, JavaScript, and other features without HTTP/2 protocol errors across the reported hosts and settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, infrastructure, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100