# "You can't login from that IP address"

**URL:** https://meta.discourse.org/t/you-cant-login-from-that-ip-address/31233
**Category:** Support
**Created:** [21 juli 2015 om 06:02 UTC](https://meta.discourse.org/t/you-cant-login-from-that-ip-address/31233 "2015-07-21T06:02:55Z")
**Posts on this page:** 1
**Showing post:** 26

<div class="post-metadata">

### Author: ![JammyDodger](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jammydodger/32/254611_2.png) [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [15 april 2022 om 15:42 UTC](https://meta.discourse.org/t/you-cant-login-from-that-ip-address/31233/26 "2022-04-15T15:42:53Z")

</div>

This is a tricky one, as I’m not entirely sure how you’ve done it. 🙂

But this is for all users, not just admin? (to rule out the `use admin ip allowlist` setting)

Do you have a CDN in front of your forum? If you disabled a user by deleting them, and then clicked the ‘Block IP’ button, that may account for the unintended blanket lock-out. If so, you could try disabling that.

If you have server access (and are comfortable) you could look at the IP blocklist using the rails console, and delete the one that’s jamming you up:

> [@Unable to log into my discourse - "You can't log in as xxx from that IP address."](https://meta.discourse.org/t/unable-to-log-into-my-discourse-you-cant-log-in-as-xxx-from-that-ip-address/27128/5):
>
> Use ScreenedIpAddress.all to see what’s there and which ones you need to delete.

> [@Unable to log into my discourse - "You can't log in as xxx from that IP address."](https://meta.discourse.org/t/unable-to-log-into-my-discourse-you-cant-log-in-as-xxx-from-that-ip-address/27128/2):
>
> You’ll need to go into the rails console or postgresql command line and delete the ScreenedIpAddress record for your IP address. s = ScreenedIpAddress.match\_for\_ip\_address("...") s.destroy

---

_[View the full topic](https://meta.discourse.org/t/you-cant-login-from-that-ip-address/31233)._