json rpc – bitcoind only accepts the RPC for 127.0.0.1 but the IP address

I use exactly the same command, one use 127.0.0.1 and the other 192.168.3.126, only the first can succeed. Someone here has already encountered a similar problem?

curl --user root --data-binary & # 39; {"jsonrpc": "1.0", "id": "curltest", "method": "getblockchaininfo", "params": [] } -H & # 39; content-type: text / plain; & # 39; http://127.0.0.1:8332/
Enter the host password for the root user:
{"result": {"string": "main", "blocks": 205269, "headers": 571040, "bestblockhash": "0000000000000508cceb43c817c744e04c" 0.02469030455221953, "chainwork": "000000000000000000000000000000000000000000000000001e6f6192f0e1ddb53e", "pruned": false , "softforks":[{"id":"bip34","version":2,"reject":{"status":false}},{"id":"bip66","version":3,"reject":{"status":false}},{"id":"bip65","version":4,"reject":{"status":false}}], "bip9_softforks": {"csv": {"status": "defined", "start time": 1462060800, "wait time": 1493596800, "since": 0}}}, "error" : null, "id": "curltest"}

curl --user root --data-binary & # 39; {"jsonrpc": "1.0", "id": "curltest", "method": "getblockchaininfo", "params": [] } -H & # 39; content-type: text / plain; & # 39; http://192.168.3.126:8332/
Enter the host password for the root user:
curl: (7) Failed to connect to port 8332 of 192.168.3.126: connection refused.

This is my bitcoin.conf

# location to store the blockchain and other data.
datadir = / mnt / hgfs / vmware / data

dbcache = 4000
# Must set txindex = 1 for Bitcoin to keep the full index
txindex = 1

# [rpc]
# Accept the command line and JSON-RPC commands.
server = 1
# Default username and password for JSON-RPC connections
rpcuser = root
rpcpassword = bitcoin

# If you want to allow remote JSON-RPC access
rpcallowip = 0.0.0.0 / 0
# [wallet]
disablewallet = 1

# [ZeroMQ]
# ZeroMQ messages feed the Planaria crawler in real time
# so it's important to define the end point
zmqpubhashtx = tcp: //192.168.3.126: 28332
zmqpubhashblock = tcp: //192.168.3.126: 28332

# BitDB uses a lot JSON-RPC, so it's set to a higher number
# But you can change this number as you wish
rpcworkqueue = 512

This is my IP address

ifconfig -a
br-76ed1d5730c4: Flags = 4099  1500 mtu
inet network mask 172.18.0.1 255.255.0.0 broadcast 172.18.255.255
inet6 fe80 :: 42: 5fff: feb2: 2046 prefixlen 64 scopeid 0x20
        ether 02: 42: 5f: b2: 20: 46 txqueuelen 0 (Ethernet)
Packets RX 2628 bytes 1531664 (1.5 MB)
RX Errors 0 Aborted 0 exceed 0 image 0
TX packets 2732 bytes 3293621 (3.2 MB)
TX errors 0 missed 0 exceedances 0 carrier 0 collisions 0

br-f5226cc26810: Flags = 4099  1500 mtu
inet network mask 172.19.0.1 255.255.0.0 broadcast 172.19.255.255
inet6 fe80 :: 42: 58ff: fe87: 853c prefixlen 64 scopeid 0x20
        ether 02: 42: 58: 87: 85: 3c txqueuelen 0 (Ethernet)
Packets RX 1267140 bytes 83830921 (83.8 MB)
RX Errors 0 Aborted 0 exceed 0 image 0
TX packets 1262839 bytes 2246455481 (2.2 GB)
TX errors 0 missed 0 exceedances 0 carrier 0 collisions 0

docker0: flags = 4099  1500 mtu
inet network mask 172.17.0.1 255.255.0.0 broadcast 172.17.255.255
ether 02: 42: 9c: ed: 2f: 9c txqueuelen 0 (Ethernet)
Packets RX 0 bytes 0 (0.0 B)
RX Errors 0 Aborted 0 exceed 0 image 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 missed 0 exceedances 0 carrier 0 collisions 0

ens33: flags = 4163  1500 mtu
inet network mask 192.168.3.126 255.255.255.0 broadcast 192.168.3.255
inet6 fe80 :: e064: 468a: 3938: cd2b prefixlen 64 scopeid 0x20
        ether 00: 0c: 29: 66: 2nd: d9 txqueuelen 1000 (Ethernet)
Packets RX 30775030 bytes 45032478812 (45.0 GB)
RX Errors 0 Aborted 0 exceed 0 image 0
TX packets 8445739 bytes 637881701 (637.8 MB)
TX errors 0 missed 0 exceedances 0 carrier 0 collisions 0

lo: flags = 73  Mtu 65536
inet network mask 127.0.0.1 255.0.0.0
inet6 :: 1 prefixlen 128 scopeid 0x10
        loop txqueuelen 1000 (local loop)
Packets RX 3321 bytes 292466 (292.4 KB)
RX Errors 0 Aborted 0 exceed 0 image 0
TX packets 3321 bytes 292466 (292.4 KB)
TX errors 0 missed 0 exceedances 0 carrier 0 collisions 0