• 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.

Customer should be able to set nginx rules

Tommy10

Basic Pleskian
I have a lot of customers who want to use nginx with WordPress. That because they need access to the nginx rules field. I cannot find any way to let them get access to it.
 
If I correctly understood you mean access to Additional nginx options in Plesk UI? This is a potentially dangerous feature therefore, only admins have access. You can create additional admin's account if you trust your customer.
 
But aren't these performance issues also possible with htaccess files for apache?

We need the nginx rules UI field to set important settings like similar for htaccess (example: WordPress).

Our customers really like to use nginx (it's fast!) but don't like to ask us each time to add specific WordPress nginx rules to their domains.
 
Specifically for apps it would have determined a solution to offer it there.
So the Plesk makes some of the work and specifically choose a server.
 
IF ( and only IF this is really the case! ) you would like a customer being able to add their own nginx - rules, you are able to insert an "include" inside the customers additional nginx directives box ( which will lead to create the file "/var/www/vhosts/system/domain.tld/conf/vhost_nginx.conf" ). The "include" can be linked to any location, where the customer has access to, as for example the webspace - root and you might give the customer the information about the location specification.

Example inside "vhost_nginx.conf":
Code:
    # Special modifications to unique nginx rules
    include /var/www/vhosts/domain.tld/httpdocs/.customer_config/customer_nginx.conf;
    # Special modifications to unique nginx rules

The customer is now able to add his own nginx directives inside the file "/var/www/vhosts/domain.tld/httpdocs/.customer_config/customer_nginx.conf", after the folder ".customer_config" and the file "customer_nginx.conf" have been created.


Pls. note, that this example is insecure and not recommended, so pls. use this at your own risk!
 
Back
Top