You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently we upgraded a machine that we use to redirect traffic to some of our sites. Among other things, we upgraded to Nginx version 1.20.1.
Following this upgrade, we noticed that the backoffice of our AquilaCMS did not display very well. This phenomenon was rather random and only occurred on Chrome. Indeed, when accessing the AquilaCMS backoffice several requests are sent at the same time, sometimes all the requests come back without errors, but sometimes some have an error which can be either net::ERR_FAILED or net::ERR_HTTP2_SERVER_REFUSED_STREAM.
The issue was that in version 1.19.7, Nginx changed several variables relating to http2 requests and caused some of the default values to change, including the number of http2 requests allowed per connection. As stated in the changelogs of this version :
Change: connections handling in HTTP/2 has been changed to better
match HTTP/1.x; the "http2_recv_timeout", "http2_idle_timeout", and
"http2_max_requests" directives have been removed, the
"keepalive_timeout" and "keepalive_requests" directives should be
used instead.
The solution was to change the value of the keepalive_requests variable from 100 to 1000, to make sure that all the requests we send can be done at the same time.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Recently we upgraded a machine that we use to redirect traffic to some of our sites. Among other things, we upgraded to Nginx version 1.20.1.
Following this upgrade, we noticed that the backoffice of our AquilaCMS did not display very well. This phenomenon was rather random and only occurred on Chrome. Indeed, when accessing the AquilaCMS backoffice several requests are sent at the same time, sometimes all the requests come back without errors, but sometimes some have an error which can be either net::ERR_FAILED or net::ERR_HTTP2_SERVER_REFUSED_STREAM.
The issue was that in version 1.19.7, Nginx changed several variables relating to http2 requests and caused some of the default values to change, including the number of http2 requests allowed per connection. As stated in the changelogs of this version :
The solution was to change the value of the
keepalive_requests
variable from 100 to 1000, to make sure that all the requests we send can be done at the same time.Beta Was this translation helpful? Give feedback.
All reactions