• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

proxy_read_timeout directive is duplicate and $VAR template objects.

brainforge

Basic Pleskian
I put values for the following into domain Additional Nginx Directives
client_max_body_size
proxy_read_timeout

I get error messages like these:
Invalid nginx configuration: nginx: [emerg] "proxy_read_timeout" directive is duplicate in ... nginx: configuration file /etc/nginx/nginx.conf test failed

I can stop that duplicate error by creating a custom conf template with those directive lines removed:
/usr/local/psa/admin/conf/templates/custom/domain/nginxDomainVirtualHost.php

But is there a better way?
The values come from variables in the template file.
Where are these variables read from?
Changing / Catching them at source and not deleting the lines in the template would most likely be better.

$VAR->domain->physicalHosting->proxySettings['nginxClientMaxBodySize']
$VAR->domain->physicalHosting->scriptTimeout

Ditto all the other $VAR - is there a document of the $VAR properties and where they come from?
 
client_max_body_size directive is duplicate and $VAR template objects.

Similarly for client_max_body_size it assigns a value of 128M to it when it builds:
/var/www/vhosts/system/mydomain.uk/conf/vhost_nginx.conf
Where is this 128M coming from?


Putting a value of 256M into 'Additional nginx directives' for the domain get a duplicate directive error.
Removing the client_max_body_size line from the custom template solves the problem.

Could get away with doing that on what could in effect be a single site server.
But no good in wider situations, there must be a more generic solution I have overlooked!

Could it be this setting in php.ini? - upload_max_filesize = 128M
But changing upload_max_filesize in domain PHP settings of Plesk does not seem to affect client_max_body_size!
 
Back
Top