keepalive_timeout issue

[mommaroodles]

Any idea why there would be a constant issue with keepalive_timeout? I have been battling with this for days and absolutely nothing I have tried is working.

I just keep on getting the same error spamming my logfiles

client 192.168.1.101 closed keepalive connection How does one fix this? And it would be great if this mysql could be updated to v8.0.13 - I tried to edit the manifest.jps file and imported from local file and it failed

[sych74]

[info] 5964#0: *14 client 192.168.1.201 closed keepalive connection

It’s an info message report says that client closed keepalive connection, nothing more. This is a normal behaviour and not an error. If you don't want see such messages - just tune your error_log logging level to something less verbose. For example, “notice” or “error”.

Currently, the wordpress is optimized to use mysql version prior 8.0. We have added mysql 8.х support and it will be published in the next update package soon.

[mommaroodles]

Something is preventing me from importing the demo content of a WordPress theme which can be done from within the WP dashboard. If I manually build the exact same topology I can import the demo content, If I use the 1 click deploy WP Cluster the importing of the demo content fails.

[sych74]

The body size and timeout parameters for nginx configuration were increased. You can deploy a new cluster from marketplace or via import and recheck your issue. If the issue will be reproduced again, please provide the information about steps to reproduce.

regards,

[mommaroodles]

Hi I'm going to try this out now again.

What I've also added to the wp-upload.ini file is max_input_vars directive - you might want to consider adding that too.