I’m trying to run Event Store 3.4.0 in a VM hosted inside Azure and I can access it on the VM but not externally. I’ve had similar problems with running it on Linux and Windows Server 2012; I would prefer to run on Linux but will keep this post specific to Windows since I’m more familiar with it (and currently have a VM to try solutions on).
What I have done:
Created Windows 2012 R2 VM in Azure
Added ports 1113 and 2113 to the Network Security Group in Azure
Changed the VM public IP address to be static in Azure
Downloaded and run Event Store in admin PowerShell: .\EventStore.ClusterNode.exe --db .\data --log .\logs --ext-http-prefixes=“http://*:2113/” At this point I can access the Web UI locally on the VM by browsing to http://127.0.0.1:2113
Run: netsh http add urlacl url=http://+:2113/ user=someadminuser This seems to break access to the Web UI locally on the VM; getting 503 errors. “netsh http show urlacl” shows only one entry for 2113 (see below)
Also tried running Event Store as: .\EventStore.ClusterNode.exe --db .\data --log .\logs --ext-http-prefixes=“http://*:2113/” --ext-ip=vm-ip-address
Any help would be appreciated. I’m at a bit of a loss of what to try next.
This depends on the deployment model. If using the hosted service model then probably not. An interesting test is to run an echo server on port 1113 and see if that is accessible from outside: if not it is an Azure configuration problem rather than an Event Store configuration problem.
We’re not able to use the new RM based VMs yet - so I am more familiar with the endpoint security model then NSG model. That said, it’s my understanding that if you assigned a network security group to a VM and open ports in the NSG you also need to explicitly open the port to the internet (by default it’s only visible within the vnet, I believe.) You don’t specify your exact NSG rule, so if you haven’t done that, maybe that’s a thing. e.g.
Can you please give us the configuration you are using?
In a lot of cases, (this will probably change soon) you need to set --add-interface-prefixes=false as part of your configuration.
So I would say that your effective configuration should read something like this
I’ve added the new network security rule but still have the same problem. I’m almost certain now though that it’s an issue on my azure configuration side.
I’m using the Resource Manager model. I’ve run an echo server over TCP on port 1113 and can’t connect so like you said it must be an Azure configuration problem.
In the case of classic virtual machines, make sure you have an endpoint on the virtual machine that allows access to the port to which you are trying to connect. In the case of RM virtual machines, make sure you have Network Security Groups configured on your vnet/vm/nic in whatever combination makes sense for your configuration to allow access to the port to which you are trying to connect.
I’m trying the same thing (newbie) and have the same issue. It’s a simple dev environment, with a single node, server 2016 in Azure. I’ve disabled Windows Firewall (it’s my throw-away dev). I’ve setup NSG allowing 2113 inbound and outbound.
I get exactly the same issue describe below. Can you please provide me with an example command line, or config file that I can run? I’d like external access to be available to EventStore on the VM.