WhiteTiger
Basic Pleskian
- Server operating system version
- Ubuntu 22.04.2 LTS
- Plesk version and microupdate number
- 18.0.50
I have a VPS with these features:
Admin Tools has a facility to generate an .htaccess or configuration file for Nginx depending on the required levels of protection.
I asked Akeeba technical support for advice on how to proceed given my configuration of Nginx as Apache Reverse Proxy.
The answer was "create .htaccess because Admin Tools work badly with Reverse Proxies".
So I would like to create .htaccess, convert its directives for Nginx with the Plesk converter and then insert them in the "Additional nginx directives" field.
The problem is, however, that Admin Tools is recognizing as active Nginx and not Apache. So I have the button to generate the file for Nginx and not for Apache.
I report this difficulty to tech support and their next response is that it shouldn't be the correct configuration if Apache is doing the job and Nginx is the Reverse Proxy. Their opinion is that Admin Tools should see Apache as active and not Nginx.
At this point I wonder if there is some other configuration to do because in Plesk I should have kept the default configuration.
- OS: Ubuntu 22.04.2 LTS
- Plesk Obsidian: Version 18.0.50 Update #2, last updated on Feb 16, 2023 06:25 PM
- Domain PHP PHP version 8.1.18, run PHP as Dedicated FPM application served by nginx
- The "Common Apache settings" are all Default
- At the moment the "Additional nginx directives" are still these:
if (!-e $request_filename) {
rewrite ^.*$ /index.php last;
}
#include "/var/www/vhosts/DOMAIN/httpdocs/nginx.conf";
- Joomla! Version 4.3.0 Stable
- In Joomla at the moment there is no .htaccess yet, but only the default file (htaccess.txt)
Admin Tools has a facility to generate an .htaccess or configuration file for Nginx depending on the required levels of protection.
I asked Akeeba technical support for advice on how to proceed given my configuration of Nginx as Apache Reverse Proxy.
The answer was "create .htaccess because Admin Tools work badly with Reverse Proxies".
So I would like to create .htaccess, convert its directives for Nginx with the Plesk converter and then insert them in the "Additional nginx directives" field.
The problem is, however, that Admin Tools is recognizing as active Nginx and not Apache. So I have the button to generate the file for Nginx and not for Apache.
I report this difficulty to tech support and their next response is that it shouldn't be the correct configuration if Apache is doing the job and Nginx is the Reverse Proxy. Their opinion is that Admin Tools should see Apache as active and not Nginx.
At this point I wonder if there is some other configuration to do because in Plesk I should have kept the default configuration.