Webinoly is just the perfect tool for NGINX experts. Give it a try!
0 votes
680 views
by Rookie
After upgrading to 16.1, it is not possible to download easy digital downloads files. In the logs error 2022/01/16 04:20:52 [error] 40900#40900: *27 upstream prematurely closed FastCGI request while reading upstream,....

Before the update everything worked fine.

I have never met with such an error before. Google also does not give out anything on it.

Who knows what and where to fix?
by Expert

Did you try: sudo webinoly -server-reset=php

by Rookie
Yes, I did it in the first place. It didn't help. Performed the same sudo webinoly -server-reset. There is also no result. I don't understand what's broken.

The update was performed from 15.1 immediately to 16.1 (without installing 16.0)
by Expert
You can try raising the "php-max-time" variable in Webinoly Configuration file. Before this update this variable was set to "300", and now is "60".by default.
by Rookie
Unfortunately, it didn't help either. Sales from the site have risen.(((

Is it possible to roll back the system to v15.1? Everything worked fine there. Perhaps there is a conflict somewhere. I will look for the problem on the test server
by Expert

Downgrade is possible but not recommended because it can break more things.

  • Check: sudo log -php
  • Check: sudo log -error
  • Paste here the output of: sudo webinoly -info Please, remove any sensitive data, like emails and passwords.
by Rookie
$ sudo log -php

[sudo] password for user:

[16-Jan-2022 13:11:00] NOTICE: Terminating ...

[16-Jan-2022 13:11:00] NOTICE: exiting, bye-bye!

[16-Jan-2022 13:11:00] NOTICE: fpm is running, pid 7216

[16-Jan-2022 13:11:00] NOTICE: ready to handle connections

[16-Jan-2022 13:11:00] NOTICE: systemd monitor interval set to 10000ms

[16-Jan-2022 21:28:59] NOTICE: Terminating ...

[16-Jan-2022 21:28:59] NOTICE: exiting, bye-bye!

[16-Jan-2022 21:29:30] NOTICE: fpm is running, pid 739

[16-Jan-2022 21:29:31] NOTICE: ready to handle connections

[16-Jan-2022 21:29:31] NOTICE: systemd monitor interval set to 10000ms

***************************************************************************************

==> /var/log/nginx/mysite.com.error.log <==

2022/01/16 21:30:02 [error] 839#839: *1 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=103%3A46%3A1%3A0&ttl=1642454996&file=1&token=8daf4885a6dc72b16bfcbcf301e91ea5ea5edc802450746c9b5e98242343021e HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

2022/01/16 21:30:02 [error] 839#839: *1 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=103%3A46%3A1%3A0&ttl=1642454996&file=1&token=8daf4885a6dc72b16bfcbcf301e91ea5ea5edc802450746c9b5e98242343021e HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

2022/01/16 21:30:03 [error] 839#839: *1 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=103%3A46%3A1%3A0&ttl=1642454996&file=1&token=8daf4885a6dc72b16bfcbcf301e91ea5ea5edc802450746c9b5e98242343021e HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

2022/01/16 22:07:27 [error] 839#839: *1036 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=103%3A46%3A1%3A0&ttl=1642454862&file=1&token=120529b48ee75ea25e4b79d92fe71d46871739a48c981a06878daa480c89e1ba HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

2022/01/16 22:07:27 [error] 839#839: *1036 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=87%3A46%3A1%3A0&ttl=1642425122&file=1&token=e9191e3fa3095286e6853a198bac2cf6be495c6aa4f1610a8c4b1733cc3c0b20 HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

2022/01/16 22:07:28 [error] 839#839: *1036 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=78%3A46%3A1%3A0&ttl=1642395609&file=1&token=f03c3974c1f79f2110c7d76f1c07a19cd7a34c9447fa1b0cb839dd9a0f7c2f2f HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

2022/01/16 22:07:29 [error] 839#839: *1036 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=48%3A46%3A1%3A0&ttl=1642394272&file=1&token=d0f9380092e11e574a34372c76e2cceec00132ae9f92f7756dd35abc8727c1ca HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

2022/01/16 22:07:30 [error] 839#839: *1036 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=48%3A46%3A1%3A0&ttl=1642394272&file=1&token=d0f9380092e11e574a34372c76e2cceec00132ae9f92f7756dd35abc8727c1ca HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

2022/01/16 22:07:30 [error] 839#839: *1036 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=95%3A46%3A1%3A0&ttl=1642454780&file=1&token=1b120cdbbb344fab35a9cfd092b4aeb3ae2699d59c787a3ccf845613ba71151b HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

2022/01/16 22:07:31 [error] 839#839: *1036 upstream prematurely closed FastCGI request while reading upstream, client: 192.168.0.1, server: mysite.com, request: "GET /index.php?eddfile=103%3A46%3A1%3A0&ttl=1642454996&file=1&token=8daf4885a6dc72b16bfcbcf301e91ea5ea5edc802450746c9b5e98242343021e HTTP/2.0", upstream: "fastcgi://127.0.0.1:9000", host: "mysite.com", referrer: "https://mysite.com/oformlenie-zakaza/podtverzhdenie-zakaza/"

***************************************************************************************

[Operating System]

OS Info: Linux version 5.4.0-94-generic (buildd@lcy02-amd64-053) (gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)) #106-Ubuntu SMP Thu Jan 6 23:58:14 UTC 2022

Description:    Ubuntu 20.04.3 LTS

Codename:       focal

RAM: 8Gb

SWAP: 4Gb

CPU Model: Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz

Architecture: GenuineIntel (x86_64)

Cores: 4

Threads per core: 2

Hostname: server

File descriptors (OS): 9223372036854775807

File descriptors (root): 243870

File descriptors (nginx/per process): 243870

[Disk Usage]

Filesystem     Type  Size  Used Avail Use% Mounted on

/dev/sda2      ext4  229G   20G  198G  10% /

[NGINX]

Branch: stable

Version: 1.20.2

worker_processes: auto

worker_connections: 20000

worker_rlimit_nofile: 243870

client_max_body_size: 100m

[NGINX Cache Settings]

FastCGI 200: 30d

FastCGI 3xx/4xx: 1m

FastCGI inactive: 7d

FastCGI max-size: 1829m

open_file_cache_valid: 30s

open_file_cache max: 1000

open_file_cache inactive: 10s

[PHP]

Info: PHP 7.4.27 (cli) (built: Dec 20 2021 21:28:15) ( NTS )

memory_limit:  192M

post_max_size:  101M

upload_max_filesize:  100M

max_file_uploads:  20

max_execution_time:  60

Process Manager:  static

pm.max_children:  12

pm.start_servers:  4

pm.min_spare_servers:  4

pm.max_spare_servers:  8

[MYSQL]

Info: mysql  Ver 15.1 Distrib 10.6.5-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

phpMyAdmin: 5.1.1

[Webinoly]

Default site: blackhole

Tools site: default

Tools port: 22222

Timezone: Europe/Moscow

SMTP Host:  smtp.yandex.ru:587

SMTP Mainsite: mysite.com

[Internal]

timezone:Europe/Moscow

nginx-ppa:stable

mail:mymail@mail.ru

global-access-log-off:true

php-ver:7.4

php-max-time:300

mysql-ver:10.6

tools-port:13321

app-version:1.16.1

pre-packs:true

nginx:true

swap-owner:system

linux-optim:true

server-version:1.7

nginx-optim:true

php:true

php-optim:true

mysql-client:true

mysql-root:1234567890=

mysql-admin:1234567890=

mysql:true

login-www-data:true

default-site:blackhole

smtp:true

status-api:wys

mysql-optim:true

mysql-tool-pma:true

nginx-tool-ssl:true

nginx-tool-bkp:true

php-tool-postfix:true

php-tool-redis:true

php-tool-memcached:true
by Expert

You forgot to reset your PHP server after "php-max-time:300" to changes take effect.

Please, run: sudo webinoly -server-reset=php

After that you should see the "max_execution_time" updated in PHP section of the INFO command. Confirm and see if it solve your issue!

by Rookie
No, I haven't forgotten. I even rebooted

the server in the -info block, it can be seen that

[Internal]

timezone:Europe/Moscow

nginx-ppa:stable

mail:mymail@mail.ru

global-access-log-off:true

php-ver:7.4

php-max-time:300

But I did the reset again. alas, it does not work. There is no file download.

created a test product on a test site. with zero payment. It doesn't download either.

See for yourself. https://vidurland.ru/downloads/tst/
by Expert
Please, read again my last comment!

I cannot help you if you don't even understand what I'm trying to explain.
by Rookie
I understood everything and I follow all your recommendations. I copied the wrong block. there is such a line in the PHP block

[PHP]

Info: PHP 7.4.27 (cli) (built: Dec 20 2021 21:28:15) ( NTS )

memory_limit:  192M

post_max_size:  101M

upload_max_filesize:  100M

max_file_uploads:  20

max_execution_time:  300

but the downloads didn't work.

I will think and look for the problem. Have a good night!

Please log in or register to answer this question.

Welcome to the Community site for Webinoly.

Our Optimized LEMP Web Server is a powerful set of commands for doing just about anything you could wish.

With Webinoly you can set up your NGINX web server in just one step.

* * * * * * *

To report a bug, please create a new issue on GitHub or ask a question here with the bug tag.
Webinoly Support Paypal Donations

PayPal · GitHub Sponsors · Bitcoin

It is very important that any visitor to the site read the disclaimer, terms of use and privacy and legal statement before start browsing.

...