Title: Wp-Admin blocking
Last modified: November 28, 2023

---

# Wp-Admin blocking

 *  Resolved [SteveHale](https://wordpress.org/support/users/stevehale/)
 * (@stevehale)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/wp-admin-blocking/)
 * Why is your product blocking my IP address when I have whitelisted it!!
 * Please advise URGENTLY

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

 *  Plugin Support [dimitrycleantalk](https://wordpress.org/support/users/dimitrycleantalk/)
 * (@dimitrycleantalk)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/wp-admin-blocking/#post-17236777)
 * Hello [@stevehale](https://wordpress.org/support/users/stevehale/),
 * You can see the reason for the blocking in your logs: [https://cleantalk.org/my/logs_firewall](https://cleantalk.org/my/logs_firewall)
 * When you add a record to your personal lists, you need to wait while the data
   syncs.
 * If you still can’t log in, do the following: 1) Add the parameter “/?access=AUTH_KEY”
   with your Security Access key to your website address. Example: **[http://MyWesbite.com/?access=abc123](http://MyWesbite.com/?access=abc123)**
 * 2) You can see your Security Access key (i.e. API Key) here in your CleanTalk
   Control Panel: [https://cleantalk.org/my/?cp_mode=security](https://cleantalk.org/my/?cp_mode=security)
 * 3) After that, you will have full access to your website for **20 minutes**.
 * Did it help?
    -  This reply was modified 2 years, 6 months ago by [dimitrycleantalk](https://wordpress.org/support/users/dimitrycleantalk/).
 *  Plugin Support [sergecleantalk](https://wordpress.org/support/users/sergecleantalk/)
 * (@sergecleantalk)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/wp-admin-blocking/#post-17246979)
 * Hello,
   We haven’t heard back from you in a few days, so I’m going to mark this
   topic as “resolved”.If you have any further questions, you can start a new topic
   or contact us via our private Ticket System: [https://cleantalk.org/my/support/open](https://cleantalk.org/my/support/open).
 *  Thread Starter [SteveHale](https://wordpress.org/support/users/stevehale/)
 * (@stevehale)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/wp-admin-blocking/#post-17247248)
 * You say this:
 * If you still can’t log in, do the following: 1) Add the parameter “/?access=AUTH_KEY”
   with your Security Access key to your website address. Example: [http://MyWesbite.com/?access=abc123](http://MyWesbite.com/?access=abc123)
 * It is noit clear to me where you make this entry.
 * Regards
 *  Plugin Support [sergecleantalk](https://wordpress.org/support/users/sergecleantalk/)
 * (@sergecleantalk)
 * [2 years, 6 months ago](https://wordpress.org/support/topic/wp-admin-blocking/#post-17247282)
 * Hello,
 * You should add this parameter to your website name in the browser’s address string.
   The **abc123 **should be changed to your Security service access key. You can
   also use this guide:
 * [https://cleantalk.org/help/security-faq#bypass_block](https://cleantalk.org/help/security-faq#bypass_block)

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

The topic ‘Wp-Admin blocking’ is closed to new replies.

 * ![](https://ps.w.org/security-malware-firewall/assets/icon-256x256.gif?rev=3518712)
 * [Security Plugin, Firewall & Malware Scanner with Auto Removal](https://wordpress.org/plugins/security-malware-firewall/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/security-malware-firewall/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/security-malware-firewall/)
 * [Active Topics](https://wordpress.org/support/plugin/security-malware-firewall/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/security-malware-firewall/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/security-malware-firewall/reviews/)

 * 4 replies
 * 3 participants
 * Last reply from: [sergecleantalk](https://wordpress.org/support/users/sergecleantalk/)
 * Last activity: [2 years, 6 months ago](https://wordpress.org/support/topic/wp-admin-blocking/#post-17247282)
 * Status: resolved