How to solve the problem with downloading Android Chrome files from Nginx acting as a proxy?

Question

Android

Redmine is installed, some files are stored in it, some files are periodically downloaded from it. On all browsers except Chrome under android and its own chrome rocking chair - everything is fine.
The chrome rocker shows a running strip, and then flies out on a timeout.
Initially, redmine was running under thin, and before that, nginx stood as a balancer.
Then I tried to run it just under webrick - the glitch disappeared, but the production version was unusable.
I tried passenger by building (passenger-install-nginx-module) a separate nginx with a built-in module. Hung up on other port. There is no glitch, but the option is not suitable, since I would like to use nginx from the repository as the main one.
Configured basically nginx proxy_pass on nginx with passenger:

server {
       listen 443 ssl;
       server_name my.server.name;

       access_log          /var/log/nginx/redmine.access.log;
       error_log           /var/log/nginx/redmine.error.log;

       ssl on;
       ssl_certificate  /etc/ssl/certs/my.server.name.crt;
       ssl_certificate_key  /etc/ssl/certs/my.server.name.key;

       ssl_session_cache    shared:SSL:10m;
       ssl_session_timeout  10m;

       client_max_body_size 1000M;

       location / {
            proxy_set_header X-Forwarded-Host $host;
            proxy_set_header X-Forwarded-Server $host;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_pass http://127.0.0.1:9800;
        }
}

The glitch is there again.
I remove ssl - there is no glitch.
From which I conclude that the whole point is in the work of proxy_pass under ssl. It is in this form that it is used in the first and penultimate versions.
Any ideas how to fix this?

Answer 1

Try to look at the transmitted traffic by the fiddler. If the glitch remains - that it is possible to compare the going packets. If it disappears, then at least look for anomalies in the server responses.

Answer 2

The problem was solved by installing a purchased SSL certificate instead of a self-signed one. I can not say, but I did the first and second with the same parameters. However, Chrome did not like something. I did not get into the traffic analysis deeply.