Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Proxy HTTPS ERR_HTTP2_PROTOCOL_ERROR #3691

Closed
Mtn16 opened this issue Jul 5, 2024 · 9 comments
Closed

Proxy HTTPS ERR_HTTP2_PROTOCOL_ERROR #3691

Mtn16 opened this issue Jul 5, 2024 · 9 comments
Labels
Bug Issues that contain unintended behavior

Comments

@Mtn16
Copy link

Mtn16 commented Jul 5, 2024

When HTTPS is activated from the proxy (KeyStore_path: proxy), the main page does not load and the following error is displayed in the browser console: Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR.
The login page works normally without any problems.

Exceptions & Other Logs

(there are no files in the /plugins/Plan/logs directory.)

Plugin versions

Latest version of Plan (5.6. build 2883)

Image

@Mtn16 Mtn16 added the Bug Issues that contain unintended behavior label Jul 5, 2024
@AuroraLS3
Copy link
Collaborator

What is your reverse proxy config like and what is Plan alternative IP set as?

@Mtn16
Copy link
Author

Mtn16 commented Jul 5, 2024

I do not have access to reverse proxy configuration, I can only connect domain to port.
Alternative IP is set to domain.

@AuroraLS3
Copy link
Collaborator

In proxy mode Plan uses http 1.1 so if the reverse proxy tries to communicate using http 2 with Plan it will fail

@Mtn16
Copy link
Author

Mtn16 commented Jul 6, 2024

Oh, okay. Am I able to switch it? (I mean in Plan)

@AuroraLS3
Copy link
Collaborator

Using a self signed cert instead of proxy mode will have Plan use http/2

@sarahyzova
Copy link

Hi there
I'm developer from the hosting where @Mtn16's server is hosted
Proxy uses http 1.1 for the communication with Plan and it seems to always return valid response.
JavaScript files shows without a problem when opened inside it's own tab or when loaded via fetch inside console. Error shows only when app is trying to import dynamic module. Other parts of the app (like fetching data) works without issue.
Also for some reason it starts to work correctly when Firefox dev tools are opened.

@AuroraLS3
Copy link
Collaborator

Does the Firefox dev tools have disable cache checkbox checked on the Network tab? Maybe it's a caching issue - if the proxy adds cache headers that can cause problems (it has at least in the past)

@sarahyzova
Copy link

We finally found the issue. It was caused by our firewall which classified this traffic as HTTP Flood attack. The problem was fixed and this ticket can be closed.

Really cool plugin BTW

@AuroraLS3
Copy link
Collaborator

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Issues that contain unintended behavior
Projects
None yet
Development

No branches or pull requests

3 participants