I have one site that was not displaying grids of info in the manager. Javascript console was displaying lots of “ERR_HTTP2_PROTOCOL_ERROR” errors. Has anyone else had problems like this with MODX 3? I would expect the newer version to work fine with HTTP2 and 3. Here’s the message from the web host tech support:
"The server was using newer HTTP/2 and HTTP/3 protocols, and some of the background requests used by the MODX Manager were being interrupted. This caused the page tree and dashboard sections to briefly appear and then fail to load.
We adjusted this domain to use the more stable HTTP/1.1 protocol instead."
I use HTTP/3 on all my sites without issues. Sounds like BS to me.
That’s kind of what I thought. I think there must be something wrong with their server setup to get this kind of error.
We’re experiencing exactly the same issue since yesterday on multiple MODX 3 websites hosted on the same LiteSpeed server.
The manager loads, but the resource tree and grids fail with ERR_HTTP2_PROTOCOL_ERROR errors in Chrome.
We’ve already ruled out MODX itself and currently have an open support ticket with our hosting provider.
Curious to hear if anyone has found the actual cause or a proper fix.
During our investigation, we noticed that the latest LiteSpeed releases (LSWS 6.3.6 / Web ADC 3.3.3) introduced several changes to the HTTP/2/HTTP/3 implementation, including stricter header validation, stream flood protection and additional protocol hardening.
Since our issue started very recently and all affected websites are hosted on the same LiteSpeed server, we’re wondering if a recent LiteSpeed update could be related. The timing seems worth investigating.
Our hosting provider confirmed the issue was related to a recent LiteSpeed update. They temporarily rolled back LiteSpeed on the affected servers, and immediately afterwards all affected MODX 3 Manager issues were resolved.