Recent content by Gregory Matthews

Great news. Thanks! We're looking forward to the upgrade!

Will upgrading to Plesk Onyx from 12.5 require us to reconfigure our server settings such as httpd/2, ssl stapling, etc., currently setup in 12.5?

... thanks again for your help. I'm also going to update to Onyx as soon as it becomes available. Have a good day.

Thanks for your help. So is the Plesk GUI for NGINX additional directives designed to accommodate anything we would need related to NGINX rewrite rules providing the formatting, etc. is correct per your comments above? Does the server process the GUI rules first (before others that may be in...

Actually, we like having NGINX as a reverse proxy sitting in front of Apache. Our only challenge is getting rewrites to work properly, especially when they are more complex and cause problems with the Plesk GUI. Is there a way to have our server process HTACCESS files natively while NGINX sits...

Thanks. I think you answered it. We will add all custom NGINX rewrites within vhost.nginx.conf which our server should interpret and execute accordingly given our above referenced LEMP Stack. I assume then that all Apache rewrite rules do not apply due to NGINX reverse proxy?

Understood. That being said, where should I be placing custom NGINX rewrite rules of a more complex nature that the GUI may allow. Some location rules are causing the GUI to error, and I'm not sure that the GUI is placing the GUI rules in a priority order for execution. Is there a custom conf...

The above snippet was just an example, not necessarily something I am trying to execute on my box. The point of my question is, where should I be placing a rule such as that, i.e., server { ... } with locations, etc., so that NGINX operating in the manner I described above, i.e., reverse proxy...

Any update and or assistance? To further clarify our needs, here is an example of the type of rule we want to insert into our NGINX configuration. Where do we need to place this type of instruction/rule so that NGINX reads and honors it for proper execution: server { server_name newdomain.com...

Our default site is already configured to use a static IP. We've tried everything we can think of in terms of NGINX rules and placing them in a variety of locations, including the Plesk GUI. The GUI snippet above was in fact generated through the Plesk .htaccess to NGINX converter. That said...

Server Setup: VPS Plesk 12.5 Centos 7 NGINX as reverse proxy to Apache 2.4 Path to NGINX config: /etc/nginx/nginx.conf Plesk provides a GUI Apache & nginx Settings dialog box, but is unable to accept server{} blocks from there. I've tried the following within /etc/nginx/nginx.conf, and...