@ivansliskovic
Is it possible that htaccess from root folder have some conflict with this new installation
It’s not a conflict, it’s working fine as expected. It happens with multi-domain hosting plans, where all Addon-Domains and sub-domains folders have their place within the root dorectory/folder.
@dwinden
Ok, so that confirms there is some problem with the content of the .htaccess file in the root.
I don’t think there is a problem with above set of rules on htaccess.
Let us assume, we have a multidomain hosting (shared or similar) with root domain PrimaryDomain.TLD. Now the default directory for this primary domain is root where index.php reside. So, htaccess file will be generated in root. Since htaccess file in root directory which contains rules that restrict install.php (wherever it exist, since htaccess is in root), it will not allow new installations for either Addon or sub-domain.
We have three best possible ways to avoid this.
- Install PrimaryDomain.TLD in a sub directory like blog, eng, index, home etc. So that all files including index.php and htaccess file will be in that sub-directory. Then primary domain url will be PrimaryDomain.TLD/blog or other. Now no rules from root will restrict addons and sub-domains installations.
- Install PrimaryDomain.tld as usual, but remove the rules that restricting new installations.
Or disable the Protect System Files setting in the System Tweaks section on the iTSec plugin Settings which write similar rules on .htaccess in the root directory. After new installations complete, enable the previous option in primary domain.
- Never try to rename .htaccess file in the primary domain if it has significant traffic. Instead put your site in maintenance mode and change whatever you like in .htaccess. After successful new installations for addon or sub domains, revert whatever changes made in .htaccess file. Next disable maintenanace mode for primary domain
Important Note:
If the first method is implemented, then manually add .htaccess file in root directory. And add essential security rules on htaccess like the following one.
# Rules to disable directory browsing
Options -Indexes
So that directory browsing will be restricted.
Once new installations for either Addon or Sub-domains are over, everything work as normal.
.htaccess file protect the directory in which it resides, and all sub-directories within that directory.
@ivansliskovic
Change the status of this thread to resolved, if your issue is over.