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

Client can't access Additional nginx directives dialogue

GlennT

Basic Pleskian
Hello,

I've been trying to configure Plesk Service Plans to give customers access to Web Server Settings > Additional nginx directives dialogue but all they see is what is in the attached screenshot.

Customers can enable Process PHP by nginx but they can't see the Additional nginx directives dialogue per the attached screenshot.

In my service plan, I've enabled Hosting performance settings management which is the only option I can see which might give them access to Additional nginx directives but that doesn't work.

Is there a way to give customers access to Additional nginx directives AND Additional directives for HTTP?

I'm running Plesk 12 on Centos 6.

Thanks in advance,
G
 

Attachments

  • Screen Shot 2015-09-16 at 10.56.24 AM.png
    Screen Shot 2015-09-16 at 10.56.24 AM.png
    134.7 KB · Views: 8
This option is only available for admin accounts. We believe that this is inappropriate to give customers this potentially dangerous possibility.
 
Thanks for your response Igor.

I can understand the rationale behind that decision but this presents some challenges for the client and the hoster.

When php-fpm is enabled for a website, htaccess no longer works and the htaccess directives need to be moved into Additional nginx directives which the client can't access.

This means we as the hoster would have to handle all those requests for the client which is not really a good option.

Is there another way handle htaccess with php-fpm enabled websites that would allow the client to manage on their own?

Alternatively, could we not have the option to enable Additional nginx directives on a site by site basis where I am confident in the developers ability?

For example, I don't enable SSH for clients by default but will on request AND if I feel the client is technically proficient.

Any insights you can provide are greatly appreciated.

Thanks
G
 
Back
Top