By Baiano on

Hi there! Can any body help me to fix this problem, "Sorry, 127.0.0.1 has been banned".

Rgds,

Baiano.

Comments

TapocoL’s picture

TapocoL commented

Well, since you are on your localhost. Just connect to your database in question (phpMyAdmin, Terminal, etc). And either change the status to 1 or delete where mask = '127.0.0.1' and type = 'host' on table 'access'.

For example,
UPDATE {access} SET status = 1 WHERE mask = '127.0.0.1' AND type = 'host';
DELETE FROM {access} WHERE mask = '127.0.0.1' AND type = 'host';

If you used table prefixes, substitute {access} with prefix_access
If not, just remove the curly braces.

-Craig Jackson
-Web Developer

Koldewijn’s picture

Koldewijn commented

Hi TapocoL,

Is this also possible on a remote server?

I have tried to insert a line in the access table setting aid value 1, mask value (my ip address) type value host and status value 1.

But I still get the "Sorry, xxx.xxx.xxx.xxx has been banned" message.

kind regards,
Marcel

kanani’s picture

kanani commented

This happened on a Linode VPS I have. only a single site was affected. I ran the sql command below to fix (thanks TapocoL).

Wish I know why it happened. That's the first time I've seen it in almost 4 years of Drupal Dev.


mysql> select * from access;
+--------+-----------+------+--------+
| aid    | mask      | type | status |
+--------+-----------+------+--------+
| 113650 | 127.0.0.1 | host |      0 | 
+--------+-----------+------+--------+
1 row in set (0.02 sec)



mysql> update access set status = 1 where aid = 113650;
Query OK, 1 row affected (0.00 sec)
Rows matched: 1  Changed: 1  Warnings: 0
mdallmeyer’s picture

mdallmeyer commented

Our server randomly banned its own IP today, no clue how it happened. Anyways, just wanted to say thanks, this was exactly the problem! Any ideas what would trigger something like this?

seefa’s picture

seefa commented

Hi there
Thanks Mr. Craig for your post.
I got a solution to solving my problem based on your response!

of course I'm using Drupal 7.22 and it doesn't have "access" table but I found tow tables with names: "blocked_ips" and "flood" that they consisted of "127.0.0.1" IP address to be blocked. I delete their contents and my problem solved.

I just want to post my experience to others. This problem happened when :
" I made a module with "hook_node_access" function and adjusted some permissions for this module and I didn't use "Clear Cache" finally. Then I logged out and logged in with other username to check status of developed module. But Drupal showed some errors in front of page. I didn't remember to these messages and logged in with Admin user again and Druapl showed "Sorry, 127.0.0.1 has been banned." error message on explorer. I think, it occurred because I didn't clear cache when I changed module table and permission too.

If there is a master Drupal developer on this topic, give us more details about this our problem.
Thanks for everybody

maxilein’s picture

maxilein commented

and absolutely no clue where this may come from.
Even when changing the error message in bootstrap.inc it still says "Sorry, 127.0.0.1 has been banned."
Please, please elaborate someone on how to track down this error.
Thanks!

Breakerandi’s picture

Breakerandi commented

I have the same error, no idea where it comes from..
First I thought my site is hacked because of drupageddon, but i found not any malcode

Drupal User Group Munich

antiden’s picture

antiden commented

Faced with a problem. Decided. I went to the phpmyadmin in table blocked_ips, found and removed from the field 127.0.0.1

Drupal itself get blocked =)

antiden * coderteam.ru

dineshw’s picture

dineshw commented

In Drupal 7, blocked_ips table is used to store a list of banned IP addresses.

You can try truncating blocked_ips table.
TRUNCATE TABLE blocked_ips

Cheers
Dinesh Waghmare (LAMP)
UK, Surrey | India, Mumbai
Web Development | Digital Media Marketing | Strategic Consulting
--
m: +91 9867888266
(Drupal / Wordpress / SugarCRM )

sanjay.soni’s picture

sanjay.soni commented

Don't truncate whole table blocked_ips.
just delete the row with '127.0.0.1' if you found.

Best Regards,
Sanjay
skype:er.sanjaysoni

bluesky_still’s picture

bluesky_still commented

because I use nginx proxy. hope help this link.

https://www.karelbemelmans.com/2015/04/reverse-proxy-configuration-for-d...