eddyferns

I did try on a test install and there was no issue to begin with.

Not aware of this could affect the WordPress functionality or the theme and so on.

I am aware of these options.

Was referring to the code that you use. Whether you you utilize rewrite rules, if statements etc.

user_nicename has the WordPress login username. The following displays the user_nicename (WordPress login username). Obviously one can change the user_nicename but I need to know how NFW removes or hides this for Nginx.

https://domain.com/author/john/ via https://domain.com/?author=1

https://domain.com/wp-json/wp/v2/users/?per_page=100&page=1

• This reply was modified 3 years, 8 months ago by eddyferns.

Thank you for your reply.

CSP is enabled in Performance>Browser Cache.

Since I need to keep the website confidential, I have sent an email to ‘[email protected]’ with the settings in Performance>Browser Cache and the website URL.

Thanks.

Have sent you the website URL via https://www.w3-edge.com/contact/.

The location of the .htaccess file is /var/www/site.com/public_html.

Is it possible to share the website URL by email?

Thanks.

Actually there was a message displayed on the NinjaFirewall’s Dashboard that the file needs to be writable to activate Full WAF.

Since Full WAF is now activated shall revert to 644.

Thank you for your reply.

There is no Apache at all. It is only Nginx and no other server.

So on a plain Nginx environment W3TC did create the .htaccess file.

Thanks. This works.

To activate the Ninja Firewall plugin’s Full WAF mode feature the user.ini file needs to be writable. The permissions were 644 for $USER:www-data. I set it to 664 and WAF feature is now activated.

So is it okay to revert to 644?

What other rate limiting feature is in the WP+ besides wp-login.php and xmlrpc.php scripts?

In the WP+ Edition, is it possible to implementing Rate Limiting specifically to wp-login.php and xmlrpc.php?

And once the IP address is blocked is it possible to unblock it manually and automatically?

Does the Rate Limiting work on Apache servers?

What kind of protection is available in NinjaFirewall Rate Limiting?

What happens if Nginx Rate Limiting and NinjaFirewall Rate Limiting is implemented?

Is Rate Limiting available only in the NinjaFirewall WP+ Edition?

Sure.

There is no bug in the password for any character.

I have just noticed that I have inadvertently set the password length above the max limit of 32. As I usually set my password length minimum 60+ wherever possible.

Sorry for the convenience.

Wouldn’t it better if you would increase the max length of the password to a greater number?

Nothing is changed in the configuration.

The issue occurred before updating theme and plugins and continues to remain the same after the updates.

There are no cookie options as per the article.

FYI it is the Avada theme.