I deployed three servers in the LAN to test the Ipfs-cluster service. Everything is fine. But when I deployed three servers (A, B, C) on Amazon, A is the default node, and when B connects to A, the connection is down. The error is:
.......
12:06:45.153 INFO service: Bootstrapping to /ip4/xxx.xxx.xxx.xxx/tcp/9096/ipfs/QmSNij94E6hFM6Y48LDna94PL3YYkr5ZirgTFPkXJTnsPc asm_amd64.s:2361
12:06:45.154 INFO ipfshttp: IPFS Proxy: /ip4/127.0.0.1/tcp/9095 -> /ip4/127.0.0.1/tcp/5001 asm_amd64.s:2361
12:07:05.153 ERROR cluster: ***** ipfs-cluster consensus start timed out (tips below) ***** cluster.go:133
12:07:05.154 ERROR cluster:
**************************************************
This peer was not able to become part of the cluster.
This might be due to one or several causes:
- Check the logs above this message for errors
- Check that there is connectivity to the "peers" multiaddresses
- Check that all cluster peers are using the same "secret"
- Check that this peer is reachable on its "listen_multiaddress" by all peers
- Check that the current cluster is healthy (has a leader). Otherwise make
sure to start enough peers so that a leader election can happen.
- Check that the peer(s) you are trying to connect to is running the
same version of IPFS-cluster.
**************************************************
cluster.go:133
12:07:05.154 INFO cluster: shutting down Cluster cluster.go:369
12:07:05.154 INFO consensus: stopping Consensus component cluster.go:440
12:07:05.154 ERROR raft: NOTICE: Some RAFT log messages repeat and will only be logged once logging.go:71
12:07:05.154 ERROR raft: Failed to take snapshot: nothing new to snapshot logging.go:48
12:07:05.154 INFO monitor: stopping Monitor cluster.go:461
12:07:05.154 INFO restapi: stopping Cluster API cluster.go:466
12:07:05.154 INFO ipfshttp: stopping IPFS Proxy cluster.go:470
12:07:05.155 INFO pintracker: stopping MapPinTracker cluster.go:475
Comment:
xxx.xxx.xxx.xxx is the public IP address of A
Later, I found that only the local address and local area network of I’s Ipfs-cluster service. Address without external network ip address,as follows
ipfs-cluster-service daemon
11:57:40.518 INFO service: Initializing. For verbose output run with "-l debug". Please wait... app.go:485
11:57:40.522 INFO cluster: IPFS Cluster v0.4.0 listening on:
/ip4/127.0.0.1/tcp/9096/ipfs/QmSNij94E6hFM6Y48LDna94PL3YYkr5ZirgTFPkXJTnsPc
/ip4/172.31.26.154/tcp/9096/ipfs/QmSNij94E6hFM6Y48LDna94PL3YYkr5ZirgTFPkXJTnsPc
daemon.go:134
11:57:40.523 INFO restapi: REST API (HTTP): /ip4/127.0.0.1/tcp/9094 asm_amd64.s:2361
11:57:40.523 INFO restapi: REST API (libp2p-http): ENABLED. Listening on:
/ip4/127.0.0.1/tcp/9096/ipfs/QmSNij94E6hFM6Y48LDna94PL3YYkr5ZirgTFPkXJTnsPc
/ip4/172.31.26.154/tcp/9096/ipfs/QmSNij94E6hFM6Y48LDna94PL3YYkr5ZirgTFPkXJTnsPc
asm_amd64.s:2361
11:57:40.524 INFO consensus: existing Raft state found! raft.InitPeerset will be ignored consensus.go:152
11:57:40.524 INFO ipfshttp: IPFS Proxy: /ip4/127.0.0.1/tcp/9095 -> /ip4/127.0.0.1/tcp/5001 asm_amd64.s:2361
11:57:42.524 INFO consensus: Current Raft Leader: QmSNij94E6hFM6Y48LDna94PL3YYkr5ZirgTFPkXJTnsPc consensus.go:120
11:57:42.524 INFO cluster: Cluster Peers (without including ourselves): cluster.go:133
11:57:42.524 INFO cluster: - No other peers cluster.go:133
11:57:42.524 INFO cluster: ** IPFS Cluster is READY ** cluster.go:133
11:57:47.525 INFO cluster: peerset change detected. Saving peers addresses asm_amd64.s:2361
I think the service is not exposed to the public network, but I don’t know what to do. If it is not for this reason, I hope to point out my problem. Thank you!