iTheme security using my old server public path
-
Hello,
iTheme security is using my old server path.
I get this error when trying to write server config rules:
The directory /srv/users/apps/mysite/public could not be created due to an unknown error. This could be due to a permissions issue.This is because my site is not located in this directory on my new host.
It’s in /home/user/web/public
Not sure how to fix this.
-
Hi Donnie,
Are you using the latest iTSec plugin release (8.0.2) ?
Is the plugin Database Backup feature enabled ?
If so you may need to correct the Backup Location setting. Note this setting will only show up if Backup Method is set to Save Locally and Email or Save Locally Only.
If you changed host, you need to change the Backup Location setting anyway…
+++++ To prevent any confusion, I’m not iThemes +++++
Hmm, it seems like the NGINX Conf File setting in Global Settings is not showing up …
If that is also the case in your env there is an alternative way to change the value of this setting.
First we’ll need to enable an extra Debug menu option by adding the line below to the wp-config.php file:
define('ITSEC_DEBUG', true);This should add an extra Debug menu item under the Security menu option.
Navigate to Security > Debug.
Under the Settings section select Global and then click on the Load button.
Look for the “nginx_file” entry. You should see it’s value is pointing to the wrong file path. Correct the path and then click on the Save button.
If this solves the issue, don’t forget to remove the added line from the wp-config.php file 😉
I noticed the nginx issue is indeed fixed in the new 7.1.0 Pappa Romeo Oscar release.
Also noticed the nginx setting is now placed as the second setting right after the “Write to Files” setting on the Global Settings page. That new position makes sense BUT the “Write to Files” setting’s label always refers to a “.htaccess“ file. This is confusing for anyone using nginx…
It’s a bug that has existed ever since the first release of the iTSec plugin. The new position of the nginx setting has now made that bug more obvious, so wouldn’t you agree it’s about time to get that “Write to Files” label fixed ?
Simply use “.htaccess“ for Apache or the file name as specified in the NGINX Conf File setting (default “nginx.conf”) for nginx.
So by default it would read like below on nginx:
Allow iThemes Security to write to wp-config.php and nginx.conf automatically. If disabled, you will need to place configuration options in those files manually.
Alternatively, make things simple and use “server Conf File” instead of specifying a platform specific configuration file 😉
The topic ‘iTheme security using my old server public path’ is closed to new replies.
