Bug: always syncing with client.yml generated by the self hosted docker compose

[Jasdent]

Have you read a contributing guide?

• I have read CONTRIBUTING.md
• I have searched the existing issues and didn't find any that were similar
• I have considered creating a pull request with fixes instead of a bug report and want to proceed

Current Behavior

Everything happens inside a intranet.

1. I have machine A on 192.168.2.12, after running make start in any-sync-dockercompose/, I have got a client.yml file and some docker containers running

CONTAINER ID   IMAGE                                            COMMAND                  CREATED          STATUS                    PORTS                                                                                                                                                                                 NAMES
43df7bdb710c   ghcr.io/anyproto/any-sync-node:v0.3.34           "/bin/sh -c '/bin/an…"   49 minutes ago   Up 23 minutes             443/tcp, 0.0.0.0:1002->1002/tcp, :::1002->1002/tcp, 0.0.0.0:1012->1012/udp, :::1012->1012/udp, 0.0.0.0:8002->8000/tcp, :::8002->8000/tcp, 0.0.0.0:8082->8080/tcp, :::8082->8080/tcp   any-sync-dockercompose-any-sync-node-2-1
23176e2fd683   ghcr.io/anyproto/any-sync-filenode:v0.6.5        "/bin/sh -c '/bin/an…"   49 minutes ago   Up 23 minutes             443/tcp, 8080/tcp, 0.0.0.0:1005->1005/tcp, :::1005->1005/tcp, 0.0.0.0:1015->1015/udp, :::1015->1015/udp, 0.0.0.0:8004->8000/tcp, :::8004->8000/tcp                                    any-sync-dockercompose-any-sync-filenode-1
7c739b30f83f   ghcr.io/anyproto/any-sync-node:v0.3.34           "/bin/sh -c '/bin/an…"   49 minutes ago   Up 23 minutes             443/tcp, 0.0.0.0:1003->1003/tcp, :::1003->1003/tcp, 0.0.0.0:1013->1013/udp, :::1013->1013/udp, 0.0.0.0:8003->8000/tcp, :::8003->8000/tcp, 0.0.0.0:8083->8080/tcp, :::8083->8080/tcp   any-sync-dockercompose-any-sync-node-3-1
77bf2cb1a93d   ghcr.io/anyproto/any-sync-node:v0.3.34           "/bin/sh -c '/bin/an…"   49 minutes ago   Up 23 minutes             443/tcp, 0.0.0.0:1001->1001/tcp, :::1001->1001/tcp, 0.0.0.0:1011->1011/udp, :::1011->1011/udp, 0.0.0.0:8001->8000/tcp, :::8001->8000/tcp, 0.0.0.0:8081->8080/tcp, :::8081->8080/tcp   any-sync-dockercompose-any-sync-node-1-1
f80b868c98ef   ghcr.io/anyproto/any-sync-consensusnode:v0.1.7   "/bin/sh -c '/bin/an…"   49 minutes ago   Up 19 seconds             443/tcp, 8080/tcp, 0.0.0.0:1006->1006/tcp, :::1006->1006/tcp, 0.0.0.0:1016->1016/udp, :::1016->1016/udp, 0.0.0.0:8006->8000/tcp, :::8006->8000/tcp                                    any-sync-dockercompose-any-sync-consensusnode-1
27444f3c6db5   ghcr.io/anyproto/any-sync-coordinator:v0.3.25    "/bin/sh -c '/bin/an…"   49 minutes ago   Up 23 minutes             443/tcp, 8080/tcp, 0.0.0.0:1004->1004/tcp, :::1004->1004/tcp, 0.0.0.0:1014->1014/udp, :::1014->1014/udp, 0.0.0.0:8005->8000/tcp, :::8005->8000/tcp                                    any-sync-dockercompose-any-sync-coordinator-1
005f3b6a6f22   redis/redis-stack-server:7.2.0-v6                "redis-server --port…"   49 minutes ago   Up 23 minutes (healthy)   0.0.0.0:6379->6379/tcp, :::6379->6379/tcp                                                                                                                                             any-sync-dockercompose-redis-1
93d8ccead607   minio/minio:RELEASE.2024-01-16T16-07-38Z         "/usr/bin/docker-ent…"   49 minutes ago   Up 23 minutes (healthy)   0.0.0.0:9000-9001->9000-9001/tcp, :::9000-9001->9000-9001/tcp                                                                                                                         any-sync-dockercompose-minio-1

2. I used the client.yml generated after make start in my other machine B (192.168.2.14), it had been in syncing for quite a while and finally become disconnected

Note: the yml file has dozens of 127.0.0.1, not sure if this is relevant

Expected Behavior

Using the generated yml, I should be able to successfully sync.

Steps To Reproduce

Machine A:

git clone [email protected]:anyproto/any-sync-dockercompose.git
git checkout v4.1.0
cd any-sync-dockercompose
make start # ensure nothing goes wrong, it outputs client.yml to $(project)/etc

Machine B:
with the yml file generated, I can see the synced after creating vault.

Environment

Hosting Machine:
OS: Debian 12
Kernel Version:  x86_64 Linux 6.1.0-18-amd64
any-sync-dockercompose codebase: tag v4.1.0

Client:
OS: Debian 12
Kernel Version:  x86_64 Linux 6.1.0-12-amd64
AnyType Client Version: 0.41.1

Anything else?

No response