之前我的一篇文章，也是解決Jedis連線不到redis的，但是情況不一樣，之前的問題主要是防火牆的問題，但是現在看來並不是防火牆的問題，因為redis自身也有配置來限制外網的訪問，所以當時也不知道為什麼就可以了，今天主要以redis配置的角度來看一下，如何解決外網訪問redis的問題。

首先還是描述一下問題：

public static void main(String[] args) {
		Jedis jedis = new Jedis("192.168.1.118", 6380);
		System.out.println(jedis);
		jedis.ping();
	}

Exception in thread "main" redis.clients.jedis.exceptions.JedisConnectionException: java.net.ConnectException: Connection refused: connect
	at redis.clients.jedis.Connection.connect(Connection.java:207)
	at redis.clients.jedis.BinaryClient.connect(BinaryClient.java:93)
	at redis.clients.jedis.Connection.sendCommand(Connection.java:126)
	at redis.clients.jedis.Connection.sendCommand(Connection.java:121)
	at redis.clients.jedis.BinaryClient.ping(BinaryClient.java:106)
	at redis.clients.jedis.BinaryJedis.ping(BinaryJedis.java:195)
	at com.atguigu.redis.test.TestPing.main(TestPing.java:10)
Caused by: java.net.ConnectException: Connection refused: connect
	at java.net.DualStackPlainSocketImpl.waitForConnect(Native Method)
	at java.net.DualStackPlainSocketImpl.socketConnect(Unknown Source)
	at java.net.AbstractPlainSocketImpl.doConnect(Unknown Source)
	at java.net.AbstractPlainSocketImpl.connectToAddress(Unknown Source)
	at java.net.AbstractPlainSocketImpl.connect(Unknown Source)
	at java.net.PlainSocketImpl.connect(Unknown Source)
	at java.net.SocksSocketImpl.connect(Unknown Source)
	at java.net.Socket.connect(Unknown Source)
	at redis.clients.jedis.Connection.connect(Connection.java:184)
	... 6 more
 

[[email protected] ~]# systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
   Active: inactive (dead)

然後使用windows的telnet來試一下，上一篇關於遠端連線redis的文章中沒有關於telnet的資訊，這次不上，

C:\Users\Administrator>telnet 192.168.1.118 6379

原來是redis預設只能localhost登入，所以需要開啟遠端登入。解決方法如下：

　　在redis的配置檔案redis.conf中，找到bind localhost註釋掉。

　　　　註釋掉本機,區域網內的所有計算機都能訪問。

　　　　band localhost   只能本機訪問,區域網內計算機不能訪問。

　　　　bind  區域網IP    只能區域網內IP的機器訪問, 本地localhost都無法訪問。

################################## NETWORK #####################################

# By default, if no "bind" configuration directive is specified, Redis listens
# for connections from all the network interfaces available on the server.
# It is possible to listen to just one or multiple selected interfaces using
# the "bind" configuration directive, followed by one or more IP addresses.
#
# Examples:
#
# bind 192.168.1.100 10.0.0.1
# bind 127.0.0.1 ::1
#
# ~~~ WARNING ~~~ If the computer running Redis is directly exposed to the
# internet, binding to all the interfaces is dangerous and will expose the
# instance to everybody on the internet. So by default we uncomment the
# following bind directive, that will force Redis to listen only into
# the IPv4 lookback interface address (this means Redis will be able to
# accept connections only from clients running into the same computer it
# is running).
#
# IF YOU ARE SURE YOU WANT YOUR INSTANCE TO LISTEN TO ALL THE INTERFACES
# JUST COMMENT THE FOLLOWING LINE.
# ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
bind 127.0.0.1
bind 192.168.1.118

# Protected mode is a layer of security protection, in order to avoid that
# Redis instances left open on the internet are accessed and exploited.
#
# When protected mode is on and if:
#
 

bind 192.168.1.118

public static void main(String[] args) {
		Jedis jedis = new Jedis("192.168.1.118", 6379);
		System.out.println(jedis);
		String ping = jedis.ping();
		System.out.println(ping);
	}

[email protected]
PONG