Category: Plesk

Plesk 11 – vhost.conf File For Nginx

April 21, 2014

We’re all familier with using a vhost.conf file on Plesk to provide custom Apache directives to an individual virtual host. Originally the file was located at:

/var/www/vhosts/domain.com/conf/vhost.conf

1	/var/www/vhosts/domain.com/conf/vhost.conf

Recent versions of Plesk have moved the file to:

/var/www/vhosts/system/domain.com/conf/vhost.conf

1	/var/www/vhosts/system/domain.com/conf/vhost.conf

And of course there is an SSL version of the file at:

/var/www/vhosts/system/domain.com/conf/vhost_ssl.conf

1	/var/www/vhosts/system/domain.com/conf/vhost_ssl.conf

The good news is there’s also now a file for Nginx at:

/var/www/vhosts/system/domain.com/conf/vhost_nginx.conf

1	/var/www/vhosts/system/domain.com/conf/vhost_nginx.conf

By default these files don’t exist and are not included in the configuration. So you’ll need to create the file and then run:

/usr/local/psa/admin/sbin/httpdmng --reconfigure-all

1	/usr/local/psa/admin/sbin/httpdmng --reconfigure-all

/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain domain.com

1	/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain domain.com

Increase Nginx Upload Limit On Server With Plesk Panel

April 15, 2014

From the Plesk Panel you can set the PHP upload_max_filesize at Website & Domains -> PHP Setting. But if you’re using Nginx then you may also need to configure Nginx to allow larger uploads. We saw errors like this in the /var/log/nginx/error_log:

2014/04/15 15:33:19 [error] 18042#0: *21376 client intended to send too large body: 1300191 bytes, client: x.x.x.x, server: , request: "POST /index.php/amfile/adminhtml_file/update/ HTTP/1.1", host: "dev.acme.com", referrer: "http://dev.acme.com/index.php/admin/catalog_product/edit/id/"

1	2014/04/15 15:33:19 [error] 18042#0: *21376 client intended to send too large body: 1300191 bytes, client: x.x.x.x, server: , request: "POST /index.php/amfile/adminhtml_file/update/ HTTP/1.1", host: "dev.acme.com", referrer: "http://dev.acme.com/index.php/admin/catalog_product/edit/id/"

To resolve the issue edit /etc/nginx/nginx.conf and set client_max_body_size by adding the highlighted line:

    server_tokens off;

    client_max_body_size 15m;

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

server_tokens off;

client_max_body_size 15m;

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

}

Fixing “504 Gateway Timeout” Errors On Plesk With Nginx

April 15, 2014

If your Plesk server is configured to run Nginx in from of Apache then you may encounter “504 Gateway Timeout” errors when executing long running PHP pages. Nginx is acting as a reverse proxy for Apache. The “proxy_read_timeout” configuration setting in Nginx controls how long Nginx will wait for Apache to return a response. The default is 60 seconds which may be too short if you have a script that takes several minutes to run. To increase this timeout, just edit /etc/nginx/nginx.conf and add the highlighted line:

    server_tokens off;

    proxy_read_timeout 300;

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

server_tokens off;

proxy_read_timeout 300;

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

}

Don’t forget to restart Nginx after making the change.

To Many PHP Session Files

March 15, 2014

I seen several servers with high traffic PHP sites hosted on Plesk servers building up an excessive number of PHP session files in /var/lib/php/session. Typically we discover this problem when the server runs out of inodes on the root filesystem. Plesk provides a cronjob that runs hourly to clean up PHP session files:

/etc/cron.hourly/plesk-php-cleanuper

1	/etc/cron.hourly/plesk-php-cleanuper

For low traffic sites this script work just fine. But for high traffic sites with thousands of sessions per hour the script is too slow and can’t keep up with the rate that files are created. The problem is the script check each files using the “fuser” utility to determine if the file is in use. This is a slow process. So on these high traffic servers I’ve found it necessary to remove the “fuser” check. Edit /etc/cron.hourly/plesk-php-cleanuper and change this line:

[ -x /usr/lib64/plesk-9.0/maxlifetime ] && [ -d /var/lib/php/session ] && find /var/lib/php/session -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib64/plesk-9.0/maxlifetime) ! -execdir fuser -s {} &nbsp;2>/dev/null \;&nbsp;-delete

1	[ -x /usr/lib64/plesk-9.0/maxlifetime ] && [ -d /var/lib/php/session ] && find /var/lib/php/session -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib64/plesk-9.0/maxlifetime) ! -execdir fuser -s {}  2>/dev/null \; -delete

to:

[ -x /usr/lib64/plesk-9.0/maxlifetime ] && [ -d /var/lib/php/session ] && find /var/lib/php/session -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib64/plesk-9.0/maxlifetime) -delete

1	[ -x /usr/lib64/plesk-9.0/maxlifetime ] && [ -d /var/lib/php/session ] && find /var/lib/php/session -depth -mindepth 1 -maxdepth 1 -type f -cmin +$(/usr/lib64/plesk-9.0/maxlifetime) -delete

Now the session cleanup will run smoothly.

Plesk Upgrade Fails Due To /root/.my.cnf

October 16, 2013

Had a Plesk upgrade fail with the following errors:

ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: YES) 
ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: YES) 
ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: YES)

ERROR 1045 (28000): Access denied for user 'admin'@'localhost' (using password: YES)

After extensive Google searches finally found the answer – the server had a /root/.my.cnf file with credentials, which were valid, but the simple presence of that file breaks the Plesk upgrade. Removing/renaming the file makes the upgrade, or rather, the bootstrap repair, run fine. That bootstrap command, by the way, can be run to repair the failed upgrade:

/usr/local/psa/bootstrapper/pp11.5.30-bootstrapper/bootstrapper.sh repair

1	/usr/local/psa/bootstrapper/pp11.5.30-bootstrapper/bootstrapper.sh repair

Then running the autoinstaller again finishes any unfinished upgrade tasks.

Reliable Penguin provides managed web hosting, systems administration, website and server migrations, and expert consulting.

Recent Updates

Fixing WP‑CLI “eval()’d code” Parse Errors on PHP 8.4 During “wp db import”

Force a 404 With a CloudFront Function (Always)

HTTP Basic Auth Is Dead

WordPress 6.8 Speculative Loading Can Break HTTP Basic Auth

Zero‑Trust for WordPress Admin with Cloudflare Access (Email One‑Time Codes)