I’m experiencing similar issues while attempting to run a cluster on Amazon Web Services.
My setup is quite different though, I run eventstore inside a docker container using this Dockerfile.
On the AWS side, I’ve defined a security group that allows TCP connections on ports 1112, 1113, 2112 and 2113 for all machines within the group (1113 and 2113 are also accessible from the outside).
My first guess was to set int-ip to the private IP of the machine and ext-ip to its public IP but then nodes refused to start with this log. Setting both int-ip and ext-ip to the machine’s public IP raises the same error.
When I leave int-ip and ext-ip unspecified, thus falling back to 127.0.0.1, the nodes start up but fail building the cluster with the same logs that Chris observes.
I will try to skip the docker part and run the node directly on the machine’s OS to rule out a docker-related problem.