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

raspberry pi 4 problems with docker and nginx:1.21.4 vs nginx:1.21.3 using as a reverse proxy #610

Closed
zenhighzer opened this issue Dec 10, 2021 · 2 comments

Comments

@zenhighzer
Copy link

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:

#VIRTUALHOSTS

     server {
        #listen 80;
        listen 443;
        listen [::]:443;

        ssl on;
        ssl_certificate /etc/nginx/wildcard_cert.crt;
        ssl_certificate_key /etc/nginx/wildcard_cert.pem;

        server_name www.mydomain.test;

        index index.htm index.html /index.htm;

        location / {
        proxy_pass http://www.mydomain.test:8888/;
        }
}


server {
    #listen 80;
    listen 443;
    #listen [::]:443;

    ssl on;
    ssl_certificate /etc/nginx/wildcard_cert.crt;
    ssl_certificate_key /etc/nginx/wildcard_cert.pem;
    server_name gitlab.mydomain.test;


    index index.htm index.html /index.htm;

    location / {
       proxy_pass http://gitlab.mydomain.test:8877;
       proxy_redirect https://gitlab.mydomain.test:8877 https://gitlab.mydomain.test;
    }

}

Thanks and Best Regards
zenhighzer

@thresheek
Copy link
Collaborator

hi @zenhighzer !

The change between 1.21.3 and 1.21.4 is move to a newer Debian version, 11.

Overall it looks similar to #601 - can you please check if updating libseccomp and docker fixes the issue for you, similar to #601 (comment) ?

Thanks!

@thresheek
Copy link
Collaborator

Closing due to feedback timeout.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants