Title: BPS block the WpRemote Plugin
Last modified: August 20, 2016

---

# BPS block the WpRemote Plugin

 *  Resolved [didit s.banuardi.n](https://wordpress.org/support/users/didithoe/)
 * (@didithoe)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/bps-block-the-wpremote-plugin/)
 * From this conversation :
    [https://twitter.com/wpremote/status/260740856724717568](https://twitter.com/wpremote/status/260740856724717568)
   When using BPS Mode fo .htaccess, It seems that BPS block the [WpRemote ](http://wordpress.org/extend/plugins/wpremote/)
   Plugin API Request.
 * How to solve this issue? can you add the WPRemote API request in whitelist ?
 * Thankypu
 * [http://wordpress.org/extend/plugins/bulletproof-security/](http://wordpress.org/extend/plugins/bulletproof-security/)

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

 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/bps-block-the-wpremote-plugin/#post-3143924)
 * I have contacted wp-remote to get more info and am waiting on their response/
   reply. Whitelisting wp-remote is going to be done with the example code i have
   posted in the thread below, but what i need to know from them is the URI condition.
 * Please see this thread
    [http://wordpress.org/support/topic/heads-up-need-confirmation-on-this-whitelist-skipbypass-code?replies=1](http://wordpress.org/support/topic/heads-up-need-confirmation-on-this-whitelist-skipbypass-code?replies=1)
 * Or of course this additional RFI and remote file website security protection 
   can be negated/not used by simply commenting out the HTTP Rererrer line of code
   with a # sign. i included the additional wp-remote whitelisted IP address line
   of code just for reference since you would not actually see this in your root.
   htaccess file and has been specifically added to move forward with finding the
   complete solution.
 * # RewriteCond %{HTTP_REFERER} ^.*your-website-domain-name.com.* [OR]
    # RewriteCond%{
   REMOTE_ADDR} ^107.22.153.142
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/bps-block-the-wpremote-plugin/#post-3143931)
 * Or maybe a better approach would be to create a separate Whitelist rule such 
   as this and to add this above skip/bypass rule #12. This would logically allow
   full access to all website files from IP 107.22.153.142 and would skip to RewriteRule./
   index.php [L] and skip/bypass all BPS security filters.
 *     ```
       # Whitelist wpremote skip/bypass
       RewriteCond %{REMOTE_ADDR} ^107.22.153.142
       RewriteRule . - [S=13]
       ```
   
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/bps-block-the-wpremote-plugin/#post-3143932)
 * I am not getting any response from the wpremote folks so if you are willing to
   test this code above i would very much appreciate that. Thanks.
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/bps-block-the-wpremote-plugin/#post-3143935)
 * And i had a similar issue with another type of remote plugin and just adding 
   a typical plugin skip/bypass rule worked fine so actually try this first. This
   skip/bypass rule would go right above skip/bypass rule #12 – # Adminer MySQL 
   management tool data populate – in your root .htaccess file.
 *     ```
       # wpremote skip/bypass rule
       RewriteCond %{REQUEST_URI} ^/wp-content/plugins/wpremote/ [NC]
       RewriteRule . - [S=13]
       ```
   
 *  Plugin Author [AITpro](https://wordpress.org/support/users/aitpro/)
 * (@aitpro)
 * [13 years, 6 months ago](https://wordpress.org/support/topic/bps-block-the-wpremote-plugin/#post-3143941)
 * This is not a new problem and is a very old issue. I got thrown off by several
   folks telling me this was a new problem and it is not. This is of course my fault
   for not checking that first. That was my first thought, but 3 people telling 
   me this was a new issue got me going down the stupid road. 😉
 * here is the old solution >>> [http://www.ait-pro.com/aitpro-blog/2252/bulletproof-security-plugin-support/checking-plugin-compatibility-with-bps-plugin-testing-to-do-list/#wpremote](http://www.ait-pro.com/aitpro-blog/2252/bulletproof-security-plugin-support/checking-plugin-compatibility-with-bps-plugin-testing-to-do-list/#wpremote)

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

The topic ‘BPS block the WpRemote Plugin’ is closed to new replies.

 * ![](https://ps.w.org/bulletproof-security/assets/icon-128x128.png?rev=1731938)
 * [BulletProof Security](https://wordpress.org/plugins/bulletproof-security/)
 * [Support Threads](https://wordpress.org/support/plugin/bulletproof-security/)
 * [Active Topics](https://wordpress.org/support/plugin/bulletproof-security/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/bulletproof-security/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/bulletproof-security/reviews/)

 * 5 replies
 * 2 participants
 * Last reply from: [AITpro](https://wordpress.org/support/users/aitpro/)
 * Last activity: [13 years, 6 months ago](https://wordpress.org/support/topic/bps-block-the-wpremote-plugin/#post-3143941)
 * Status: resolved