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
Hi there,
today after "upgrading" my container from nginx:1.21.3 to nginx:1.21.4 I experienced some strange behavior
My browser throws errors like:
504 Gateway Time-out
PR_END_OF_FILE_ERROR
In the nginx-logs there are errors like:
1931/02/16 03:06:35 [error] 24#24: *660 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.100.202, server: gitlab.mydomain.test, request: "GET / HTTP/2.0", upstream: "http://192.168.100.55:8877/", host: "gitlab.mydomain.test"
But if I use nginx:1.21.3 with the same configuration everything is absolutely fine, no errors
I build an own image with Dockerfile and the only difference is "FROM nginx:1.21.3" and "FROM nginx:1.21.4"
And for testing I just change the docker run command like docker run [bind some mounts and ports] nginx:1.21.3 vs docker run [bind some mounts and ports] nginx:1.21.4
Are there any breaking changes, do I make something wrong or what could be the problem? Thank you for your help :)
In general I use a really "basic" configuration like:
Hi there,
today after "upgrading" my container from nginx:1.21.3 to nginx:1.21.4 I experienced some strange behavior
My browser throws errors like:
In the nginx-logs there are errors like:
1931/02/16 03:06:35 [error] 24#24: *660 upstream timed out (110: Connection timed out) while reading response header from upstream, client: 192.168.100.202, server: gitlab.mydomain.test, request: "GET / HTTP/2.0", upstream: "http://192.168.100.55:8877/", host: "gitlab.mydomain.test"
But if I use nginx:1.21.3 with the same configuration everything is absolutely fine, no errors
Are there any breaking changes, do I make something wrong or what could be the problem? Thank you for your help :)
In general I use a really "basic" configuration like:
Thanks and Best Regards
zenhighzer
The text was updated successfully, but these errors were encountered: