Title: Ninjafirewall activation using WPCLI
Last modified: January 19, 2021

---

# Ninjafirewall activation using WPCLI

 *  Resolved [eddyferns](https://wordpress.org/support/users/eddyferns/)
 * (@eddyferns)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/ninjafirewall-activation-using-wpcli/)
 * The Ninjafirewall is successfully installed. But when trying to activate receive
   the following message:
 * “You do not have “unfiltered_html” capability. Please enable it in order to run
   NinjaFirewall (or make sure you do not have “DISALLOW_UNFILTERED_HTML” in your
   wp-config.php script).”
 * There is no DISALLOW_UNFILTERED_HTML line in wp-config.php.

Viewing 4 replies - 1 through 4 (of 4 total)

 *  Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/)
 * (@nintechnet)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/ninjafirewall-activation-using-wpcli/#post-13929007)
 * You need the ‘manage_options’ and ‘unfiltered_html’ capabilities to enable and
   disable it. With WP CLI, you need to add the admin user with the “–user” parameter:
 * `$ wp plugin activate ninjafirewall --user=admin_user_here`
 * Replace “admin_user_here” with the admin login name (or email or id).
 *  Thread Starter [eddyferns](https://wordpress.org/support/users/eddyferns/)
 * (@eddyferns)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/ninjafirewall-activation-using-wpcli/#post-13932450)
 * 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?
 *  Plugin Author [nintechnet](https://wordpress.org/support/users/nintechnet/)
 * (@nintechnet)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/ninjafirewall-activation-using-wpcli/#post-13936801)
 * I assume it is. On most servers, 0644 is the right value. The only times NinjaFirewall
   needs to write to that file is when you enable the “Full WAF” mode or uninstall
   the plugin.
 *  Thread Starter [eddyferns](https://wordpress.org/support/users/eddyferns/)
 * (@eddyferns)
 * [5 years, 4 months ago](https://wordpress.org/support/topic/ninjafirewall-activation-using-wpcli/#post-13937119)
 * 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.

Viewing 4 replies - 1 through 4 (of 4 total)

The topic ‘Ninjafirewall activation using WPCLI’ is closed to new replies.

 * ![](https://ps.w.org/ninjafirewall/assets/icon-256x256.png?rev=976137)
 * [NinjaFirewall (WP Edition) - Advanced Security Plugin and Firewall](https://wordpress.org/plugins/ninjafirewall/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/ninjafirewall/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/ninjafirewall/)
 * [Active Topics](https://wordpress.org/support/plugin/ninjafirewall/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/ninjafirewall/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/ninjafirewall/reviews/)

## Tags

 * [wp-cli](https://wordpress.org/support/topic-tag/wp-cli/)

 * 4 replies
 * 2 participants
 * Last reply from: [eddyferns](https://wordpress.org/support/users/eddyferns/)
 * Last activity: [5 years, 4 months ago](https://wordpress.org/support/topic/ninjafirewall-activation-using-wpcli/#post-13937119)
 * Status: resolved