This is a must-use feature if you have a team working on your website. Sometimes it’s important to track a user’s actions to see if they have accessed and changed settings that were not supposed to be changed.
Note! For the following features, you need to have the Hide My WP Ghost version installed.
Once you switch on Hide My WP Ghost > Events Log > Log User Events you will start the user logging process on the cloud. The plugin will save all the known actions and details about every action, so it will be easy to understand what a user did on the website.
(more…)In the previous lesson, you learned how to customize the common WordPress paths.
Now it’s time to learn how to protect the custom wp-login path from Brute Force attacks if you make it public for subscribers.
Note! You need to be aware that you don’t need to have just one login path. If your theme has a login path for subscribers, you can activate the theme’s security for that URL and have your own secret login path withHide My WP Ghost.
Good, now that you have set a login path in Hide My WP Ghost, it’s time to activate the Brute Force attack protection for it.
(more…)In the previous lesson you learned how to protect your login page from Brute Force attacks, it’s time to learn how to hide your website from WordPress theme detectors and hackers’ bots.
Note! Please read Hide WordPress from Theme Detectors or from Hackers Bots?
Changing the common WordPress paths will not guarantee that the WordPress CMS is completely hidden. The old paths are still accessible and hackers are still able to inject SQL and Javascript into vulnerable installed plugins and themes.
Follow the next steps, and learn what you need to do to fully protect your website.
(more…)
If WPPlugins founds any security issues, it means that your WordPress CMS is easily detectable, which leaves your site exposed to hackers.
If you don’t act NOW, it’s very likely that hacker bots will manage to break into your website sooner or later. If they do, they usually remove the website content entirely and steal your database information.
The loss and recovery costs can be … oh well … you do the math.
Below you will find more details and solutions for each security breach WPPlugins may uncover for your site.
(more…)You can customize the database permission if the server allows this.
For WordPress website, you can leave only the following permissions enabled:
Follow the pictures:
2. In the “Privileges” tab which list your users click the “Edit Privileges” of the user.
Then select the database:
After that specific the privileges by checking them and then select your table as shown in the picture:
After you select your table, you can define the operations in detailed:
If you followed all the Hide My WP Ghost indications, probably it’s a .htaccess file issue.
Please check the .htaccess file and look for
# BEGIN WordPress
<IfModule mod_rewrite.c>
RewriteEngine On
RewriteBase /
RewriteRule ^index\.php$ - [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule . /index.php [L]
</IfModule>
# END WordPress(more…)= 8.1.02 =
= 8.1.01 =
= 8.0.21 =
= 8.0.20 =
= 8.0.19 =
= 8.0.17 =
= 8.0.16 =
= 8.0.15 =
= 8.0.14 =
= 8.0.13 =
= 8.0.12 =
= 8.0.11 =
= 8.0.10 =
= 8.0.09 =
= 8.0.07 =
= 8.0.06 =
= 8.0.05 =
= 8.0.03 =
= 8.0.02 =
= 8.0.01 =
= 8.0.00 =
= 7.3.05 =
= 7.3.03 =
= 7.3.01 =
= 7.3.00 =
= 7.2.07 =
= 7.2.06 =
= 7.2.05 =
= 7.2.04 =
= 7.2.03 =
= 7.2.02 =
= 7.2.01 =
= 7.2.00 =
= 7.1.17 =
= 7.1.16 =
= 7.1.15 =
= 7.1.13 =
= 7.1.12 =
= 7.1.11 =
= 7.1.10 =
= 7.1.08 =
= 7.1.07 =
= 7.1.06 =
= 7.1.05 =
= 7.1.04=
= 7.0.15 =
= 7.0.14 =
= 7.0.12 =
= 7.0.11 =
= 7.0.10 =
= 7.0.05 =
= 7.0.04 =
= 7.0.03 =
= 7.0.02 =
= 7.0.01 =
= 6.0.24 =
= 6.0.23 =
= 6.0.22 =
= 6.0.20 =
= 6.0.19 =
= 6.0.18 =
= 6.0.16 =
= 6.0.15 =
= 6.0.14 =
= 6.0.13 =
= 6.0.12 =
= 6.0.11 =
= 6.0.10 =
= 6.0.09 =
= 6.0.08 =
= 6.0.07 =
= 6.0.06 =
= 6.0.05 =
= 6.0.04 =
= 6.0.03 =
= 6.0.00 =
If you have a sharing hosting service, you can follow this tutorial and use only the features that don’t need rewrite rules in nginx.conf file:
https://hidemywpghost.com/how-to-use-hide-my-wp-ghost-with-nginx-hosting-without-editing-config-files/
Please follow this tutorial step by step to set up the Hide My WP Ghost for Nginx server:
If your server is a Linux server, the main path to the nginx.conf file is /etc/nginx/nginx.conf (or /etc/nginx/conf/nginx.conf if you’re using Arch Linux). If the server is a Windows server your nginx.conf file will be located at C:/nginx/conf/nginx.conf)
If your nginx doesn’t have sites-enabled option activated (check for sites-enabled subdirectory in the same directory with nginx.conf file), you will find the server configuration in nginx.conf file like in the below example:
server {
server_name [your domain name];
root [path to the website root];
index index.php;
location / {
try_files $uri $uri/ /index.php?$args;
}
}(more…)Step1: Install, Setup Hide My WP Ghost Plugin and click the Save button with the new paths.
Step2: Copy the rewrite rules from Hide My WP Ghost into Bitnamy config file
Bitnami uses “htaccess.conf” files by default instead of “.htaccess” files for security and performance reasons. You can find more info at https://docs.bitnami.com/general/apps/redmine/administration/use-htaccess/
(more…)Setting Hide My Wp Ghost on a Nginx server it’s pretty easy.
Nginx stores its configuration files in the “/etc/nginx” directory.
Inside of this directory, you will find a few directories and various modular configuration files:
cd /etc/nginx ls -F(more…)