Second node sync issue

[Johnaverse]

Hi cronos team,

I was try to sync two archive node (active-active) with two private ip and shared public ip.

I got the following error.

5:34PM INF Error reconnecting to peer. Trying again addr={"id":"3032073adc06d710dd512240281637c1bd0c8a7b","ip":"3.69.33.158","port":26656} err="auth failure: secret conn failed: EOF" module=p2p server=node tries=0
5:34PM INF Ensure peers module=pex numDialing=0 numInPeers=0 numOutPeers=0 numToDial=10 server=node
5:34PM INF Error reconnecting to peer. Trying again addr={"id":"337377dcda43d79c537d2c4d93ad3b698ce9452e","ip":"35.208.227.66","port":26656} err="auth failure: secret conn failed: read tcp 172.22.49.51:34692->35.208.227.66:26656: read: connection reset by peer" module=p2p server=node tries=3
5:34PM INF Error reconnecting to peer. Trying again addr={"id":"3032073adc06d710dd512240281637c1bd0c8a7b","ip":"3.69.33.158","port":26656} err="auth failure: secret conn failed: read tcp 172.22.49.51:33646->3.69.33.158:26656: read: connection reset by peer" module=p2p server=node tries=1
5:34PM INF Error reconnecting to peer. Trying again addr={"id":"0d5cf1394a1cfde28dc8f023567222abc0f47534","ip":"13.228.31.77","port":26656} err="auth failure: secret conn failed: read tcp 172.22.49.51:45920->13.228.31.77:26656: read: connection reset by peer" module=p2p server=node tries=1
5:34PM ERR Failed to read request err="websocket: close 1006 (abnormal closure): unexpected EOF" module=rpc-server protocol=websocket remote={"IP":"127.0.0.1","Port":48936,"Zone":""} server=node
5:34PM INF service stop impl={"Logger":{}} module=rpc-server msg={} protocol=websocket remote={"IP":"127.0.0.1","Port":48936,"Zone":""} server=node
5:34PM ERR error while stopping connection error="already stopped" module=rpc-server protocol=websocket server=nod

Is it a known issue? If yes, many I know any ha solution there ?

[yihuang]

seems like networking issue, the connection is reject by the remote end.

[Johnaverse]

I have 2 node within the same subnet, shared public ip. I am not sure is it affecting the second node connect to the same peer.

[Johnaverse]

Issue solved by separated outbound address

[wangtao19911111]

Issue solved by separated outbound address
Can you elaborate on how it was handled