Hi David,
This is usually a problem on the client (of which you'll have no control) or the Origin. (web server)
The HTTP/2 settings can be adjust within the website under the delivery settings. (left hand nav)
There are 3 options:

The first will disable HTTP/2 support completely.
The second option will enable support from client to Imperva, but then use HTTP/1.0 or HTTP/1.1 to communicate with the Origin. (webserver) If you select this option and the errors persist then you know the problem is with the clients. If the errors go away, then you know the problem is with the Origin.
The third option will enable HTTP/2 support from the client to Imperva, and Imperva to the Origin.
------------------------------
Jaired Anderson
Imperva
------------------------------
Original Message:
Sent: 06-14-2023 18:47
From: David Sloane
Subject: "err_http2_protocol_error" with some users accessing site through Imperva WAF
Hello,
Some of my colleagues and customers report "err_http2_protocol_error" in Google Chrome when connecting to a site that's proxied by Imperva Cloud WAF.
I couldn't find any reference to this error in docs.imperva.com.
I've seen discussions about this kind of issue in other forums, which generally say "update your software".
Any tips or troubleshooting guides would be appreciated.
#CloudWAF(formerlyIncapsula)
------------------------------
David Sloane
VP Production IT
Bonterra LLC
------------------------------