Iptables accidentally put 127.0.0.1, causing Redis to not connect

Wrote a script to scan the Apache log, automatically put a malicious attacker's IP to iptables to seal off

Who knows the way to accidentally 127.0.0.1 also to seal the ...

directly causing Redis to be unable to link.

Redis-server service start Normally, the port is also open, log all normal, is Redis client (REDIS-CLI and Python API) not connected, error timeout.

Check the link status, found that the client is syn_sent, that is, "the client made a connection request, waiting for the service side response."

Iptabls the 127.0.0.1 to the seal, it returned to normal.

Iptables accidentally put 127.0.0.1, causing Redis to not connect