• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Step by step guide to install and integrate Varnish with Plesk 12.x

elemental.tm

Basic Pleskian
Hi,

I have searched this forum and the internet in general and have been unable to find a definitive guide on how to install, configure and integrate Varnish with Plesk 12.x, Nginx, Apache, PHP-FPM and APC.
Do Virtual Hosts Settings need to be configured Using Configuration Templates?

It would be great if someone from Parallels or a super users could create an 'official guide' for the perfect solution in a step by step guide.

I'm using Debian 7.6 but I assume any guide would be fairly universal.

Any takers?, thanks in advance.
 
Last edited:
Plesk uses per-domain .php template files to generate the full '/etc/nginx/nginx.conf' and '/etc/httpd/conf/httpd.conf' server configurations files. If you follow the instructions contained in @IgorG's link, you'll probably run into a situation where your direct edits to the nginx.conf or httpd.conf files will conflict with the directives coming from the per-domain .php template includes.

You may want to consider editing the .php templates directly. The default templates for httpd.conf and ngnix.conf are:
  1. /usr/local/psa/admin/conf/templates/default/domain/domainVirtualHost.php,
  2. /usr/local/psa/admin/conf/templates/default/domain/nginxDomainVirtualHost.php
Do not edit the original .php files that already exist in the /usr/local/psa/admin/conf/default/domain/ folder. Instead, create a directory path that looks like this: /usr/local/psa/admin/conf/custom/domain. Duplicate the specific .php file(s) that you need to edit and copy it to the /custom/domain/ folder.

The two template files are available online as well:
http://autoinstall.plesk.com/PSA_11.0.9/microupdates/MU9/common/nginxDomainVirtualHost.php
http://autoinstall.plesk.com/PSA_11.0.9/microupdates/MU15/common/default/domainVirtualHost.php

You have to figure out the conditional logic so that the template will produce the correct output for the specific vhost that you are trying to configure. Make sure that you run a '

php -l /usr/local/psa/admin/conf/templates/custom/domain/nginxDomainVirtualHost.php' to check the edited .php template for errors.

Once you have confirmed that there are no errors in the template, you can then run '
/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain your.domain.tld' to rebuild the configuration for your domain.

The output of the template will be visible in either of these two files:

  1. /var/www/vhosts/system/your.domain.tld/conf/last_nginx.conf
  2. /var/www/vhosts/system/your.domain.tld/conf/last_httpd_ip_default.conf
If you need to undo the custom configuration, then you can rename or remove the duplicated .php files inside the /custom/domain/ folder. Then run the '/usr/local/psa/admin/sbin/httpdmng --reconfigure-domain your.domain.tld' command again. The httpdmng will default back to the original .php templates to rebuild the server configuration.
 
Last edited:
which Cache module does plesk support??
We will officially support APC module and Zend OPcache module in next Plesk 12.1 version. You will be able use (enable/disable) it per domain.
 
We will officially support APC module and Zend OPcache module in next Plesk 12.1 version. You will be able use (enable/disable) it per domain.

Alright, good news then. Sorry to ask but is it possible to use Nginx only? Instead of as a reverse proxy
 
Sorry to ask but is it possible to use Nginx only? Instead of as a reverse proxy
No way. A lot of Plesk webhosting features related to Apache and can be used in scope of Nginx only.
 
Plesk uses per-domain .php template files to generate the full '/etc/nginx/nginx.conf' and '/etc/httpd/conf/httpd.conf' server configurations files. If you follow the instructions contained in @IgorG's link, you'll probably run into a situation where your direct edits to the nginx.conf or httpd.conf files will conflict with the directives coming from the per-domain .php template includes.

You may want to consider editing the .php templates directly. The default templates for httpd.conf and ngnix.conf are:
  1. /usr/local/psa/admin/conf/templates/default/domain/domainVirtualHost.php,
  2. /usr/local/psa/admin/conf/templates/default/domain/nginxDomainVirtualHost.php
...
.

Sean_MacInnes do you have a manual, how to fix this problem with Plesk 12?

I try intergate Plesk with the Varnish cache, with no luck... my problem is, all domains contain the same website from the file: /var/www/index.php instead from /var/www/vhost/domain......./.../

Please advise
 
Back
Top