Title: iTheme security using my old server public path Last modified: December 17, 2021 --- # iTheme security using my old server public path * [Tommy](https://wordpress.org/support/users/baptistej/) * (@baptistej) * [4 years, 4 months ago](https://wordpress.org/support/topic/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. Viewing 8 replies - 1 through 8 (of 8 total) * [nlpro](https://wordpress.org/support/users/nlpro/) * (@nlpro) * [4 years, 4 months ago](https://wordpress.org/support/topic/itheme-security-using-my-old-server-public-path/#post-15174487) * 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 +++++ - This reply was modified 4 years, 4 months ago by [nlpro](https://wordpress.org/support/users/nlpro/). * Thread Starter [Tommy](https://wordpress.org/support/users/baptistej/) * (@baptistej) * [4 years, 4 months ago](https://wordpress.org/support/topic/itheme-security-using-my-old-server-public-path/#post-15175082) * Hello, * Yes I’m using the latest version and database backups are not enabled. * Also, in the “Check File Permissions” tools at the end I see my old server directory path * srv/users/mysite/public/nginx.conf * It should be home/users/web/public/nginx.conf * It seems that iTheme don’t update the server path properly, maybe something not updated in my database? I’m not sure where to look. * [nlpro](https://wordpress.org/support/users/nlpro/) * (@nlpro) * [4 years, 4 months ago](https://wordpress.org/support/topic/itheme-security-using-my-old-server-public-path/#post-15175143) * Ah ok. So the site is using NGINX web server. * In that case you need to correct the **NGINX Conf File** setting in **Global Settings**. * Navigate to Security > Settings > CONFIGURE and scroll down a bit. * That should do it. * [nlpro](https://wordpress.org/support/users/nlpro/) * (@nlpro) * [4 years, 4 months ago](https://wordpress.org/support/topic/itheme-security-using-my-old-server-public-path/#post-15175228) * 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 😉 - This reply was modified 4 years, 4 months ago by [nlpro](https://wordpress.org/support/users/nlpro/). * Thread Starter [Tommy](https://wordpress.org/support/users/baptistej/) * (@baptistej) * [4 years, 4 months ago](https://wordpress.org/support/topic/itheme-security-using-my-old-server-public-path/#post-15175898) * The nginx option is not showing up for me too, might be a bug? * The debug method worked perfectly! * Thank you very much! * [nlpro](https://wordpress.org/support/users/nlpro/) * (@nlpro) * [4 years, 4 months ago](https://wordpress.org/support/topic/itheme-security-using-my-old-server-public-path/#post-15175982) * Ah great. Thank you for your feedback. * [@timothyblynjacobs](https://wordpress.org/support/users/timothyblynjacobs/) * Probably a known issue, but we noticed that the **NGINX Conf File** setting is not showing up in the **Global Settings** UI when on nginx … * I also noticed the **Enable Grade Report** setting is showing up in the **Global Settings** UI of the free plugin. If I’m not mistaken **Grade Report** is still a **P**apa **R**omeo **O**scar only feature. * Plugin Contributor [Timothy Jacobs](https://wordpress.org/support/users/timothyblynjacobs/) * (@timothyblynjacobs) * [4 years, 4 months ago](https://wordpress.org/support/topic/itheme-security-using-my-old-server-public-path/#post-15222420) * Thanks for the report! We’ll get this fixed in the next release. * [nlpro](https://wordpress.org/support/users/nlpro/) * (@nlpro) * [4 years, 3 months ago](https://wordpress.org/support/topic/itheme-security-using-my-old-server-public-path/#post-15333924) * [@timothyblynjacobs](https://wordpress.org/support/users/timothyblynjacobs/) * I noticed the nginx issue is indeed fixed in the new 7.1.0 **P**appa **R**omeo** O**scar 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 😉 - This reply was modified 4 years, 3 months ago by [nlpro](https://wordpress.org/support/users/nlpro/). Viewing 8 replies - 1 through 8 (of 8 total) The topic ‘iTheme security using my old server public path’ is closed to new replies. * ![](https://ps.w.org/better-wp-security/assets/icon.svg?rev=3529351) * [Kadence Security – Password, Two Factor Authentication, and Brute Force Protection](https://wordpress.org/plugins/better-wp-security/) * [Frequently Asked Questions](https://wordpress.org/plugins/better-wp-security/#faq) * [Support Threads](https://wordpress.org/support/plugin/better-wp-security/) * [Active Topics](https://wordpress.org/support/plugin/better-wp-security/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/better-wp-security/unresolved/) * [Reviews](https://wordpress.org/support/plugin/better-wp-security/reviews/) * 8 replies * 3 participants * Last reply from: [nlpro](https://wordpress.org/support/users/nlpro/) * Last activity: [4 years, 3 months ago](https://wordpress.org/support/topic/itheme-security-using-my-old-server-public-path/#post-15333924) * Status: not resolved