• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Error while Uploading files over 500MB

staatsfeind3326

New Pleskian
Hello Forum,

I am switching to a new server because need more webspace. Things which have been worked on old server are not working anymore.

Old Server:
Plesk Version 17.5.3
‪Ubuntu 14.04.6 LTS‬
Nginx Apache FastCGI
PHP 5.3.29

New Server:
Plesk Version 17.8.11
‪Ubuntu 16.04.6 LTS‬
Nginx Apache FastCGI
PHP 5.3.29

I have overtaken all the settings from old server but if I upload more than 500MB then I will get this error:

20716#0: *1 upstream prematurely closed connection while reading response header from upstream

Sometimes additional:
21804#0: *227 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream

I have searched whole google and made the changes which were declared as solution but no changes for me.
I have also made this changes for Apache and Nginx:

Additional HTTP and HTTPS:
<IfModule mod_fcgid.c>
FcgidMaxRequestLen 1073741824
FcgidMaxRequestsPerProcess 100
FcgidProcessLifeTime 7200
</IfModule>
MaxRequestLen 1073741824


In /etc/nginx/conf.d/aa_client_max_body.conf I have setup
client_max_body_size 1024m;

In /etc/nginx/conf.d/timeout.conf I have setup
proxy_connect_timeout 1800;
proxy_send_timeout 1800;
proxy_read_timeout 1800;
send_timeout 1800;


Dont know what to do anymore. I can upload 500MB but not 501MB???

Thank you all for your help
 
I have already tried this:

In Apache & Nginx Settings I have inserted this:
Code:
<IfModule mod_fcgid.c>
    FcgidMaxRequestLen 1073741824
    FcgidMaxRequestsPerProcess 0
    FcgidProcessLifeTime 7200
</IfModule>
MaxRequestLen 1073741824


Additional PHP Settings in Plesk:
Code:
proxy_read_timeout 9600;

In /etc/apache2/mods-available/fcgid.conf
Code:
FcgidIdleTimeout 40
  FcgidProcessLifeTime 30
  FcgidMaxProcesses 250
  FcgidMaxProcessesPerClass 8
  FcgidMinProcessesPerClass 0
  FcgidConnectTimeout 30
  FcgidIOTimeout 1800
  FcgidBusyTimeout 1800
  FcgidInitialEnv RAILS_ENV production
  FcgidIdleScanInterval 10
  FcgidMaxRequestLen 1073741824


In /etc/nginx/conf.d/ created aa_client_max_body.conf
client_max_body_size 1024m;

created timeout.conf
Code:
proxy_connect_timeout 1800;
proxy_send_timeout 1800;
proxy_read_timeout 1800;
send_timeout 1800;
this is my /etc/nginx/nginx.conf
Code:
#user  nginx;
worker_processes  auto;

#error_log  /var/log/nginx/error.log;
#error_log  /var/log/nginx/error.log  notice;
#error_log  /var/log/nginx/error.log  info;

#pid        /var/run/nginx.pid;

include /etc/nginx/modules.conf.d/*.conf;

events {
    worker_connections  1024;
}


http {
    include       mime.types;
    default_type  application/octet-stream;

    #log_format  main  '$remote_addr - $remote_user [$time_local] "$request" '
    #                  '$status $body_bytes_sent "$http_referer" '
    #                  '"$http_user_agent" "$http_x_forwarded_for"';

    #access_log  /var/log/nginx/access.log  main;
    proxy_ssl_server_name on;
    proxy_request_buffering off;
    proxy_buffering off;
    proxy_buffer_size 64k;
    proxy_buffers 16 32k;
    proxy_busy_buffers_size 64k;
    proxy_redirect off;


    sendfile        on;
    #tcp_nopush     on;

    keepalive_timeout  0;
    #keepalive_timeout  65;
    #tcp_nodelay        on;

    #gzip  on;
    #gzip_disable "MSIE [1-6]\.(?!.*SV1)";

 
    fastcgi_buffers 8 64k;
    fastcgi_buffer_size 128k;

 
    server_tokens off;

    include /etc/nginx/conf.d/*.conf;
}

# override global parameters e.g. worker_rlimit_nofile
include /etc/nginx/*global_params;

Any Plesk Moderator here? There must be a solution for that.
 
It seems that I have a problem with the fcgid configs. If I switch to FPM application served by apache or nginx I am able to upload 1GB files without any errors. If I switch to fcgid then I get again these errors.

20716#0: *1 upstream prematurely closed connection while reading response header from upstream
Sometimes additional:
21804#0: *227 peer closed connection in SSL handshake (104: Connection reset by peer) while SSL handshaking to upstream
 
Back
Top