Azure ESDB - Connection Refused


Recently signed up to the Preview program now that you have Azure support, so keen to trial this.

I’ve created my first network, cluster and peered with existing infrastructure in my Azure subscription. However, I’m not able to reach any of the esdb endpoints from the VNET.

I have a Linux VM connected to the remote network on the same address space as defined in the Peering within the Cloud console. I can ping the following address (and get a reply), but receiving Connection Refused when attempting to reach the TCP ports as detailed in the Cloud Console:


PING ( 56(84) bytes of data.
64 bytes from ( icmp_seq=1 ttl=64 time=2.18 ms
64 bytes from ( icmp_seq=2 ttl=64 time=1.85 ms
64 bytes from ( icmp_seq=3 ttl=64 time=1.44 ms
64 bytes from ( icmp_seq=4 ttl=64 time=1.77 ms
64 bytes from ( icmp_seq=5 ttl=64 time=1.61 ms
64 bytes from ( icmp_seq=6 ttl=64 time=1.77 ms
— ping statistics —
6 packets transmitted, 6 received, 0% packet loss, time 5008ms
rtt min/avg/max/mdev = 1.440/1.772/2.182/0.230 ms

telnet 1113
telnet: Unable to connect to remote host: Connection refused

curl: (7) Failed to connect to port 2113: Connection refused

I’m unsure where to go next with this, anyone have any ideas?


Please contact us through our Support portal.

Hi Yorick,

Sorry, where is that? I don’t see a link in the Cloud portal


Please check your private messages.

I have a similar configuration in Azure AKS with 6 services connecting to a single node cluster in ES Cloud. So far all works really well.

I setup a VM to manage the cluster and peered to it’s VNet. From there I am able to launch the ES console.

I am not certain it’s required but I also peered to the VNet of AKS. On the next AKS deployment I will see if all works without that peering.

The issue was a corrupted esdb cluster in the end. Dropping and recreating it from the console fixed the issue.