Service health check fails using [::1] on Windows

Consul
1

I am registering a DB service via Nomad and I am getting a “Get “http://[::1]:27712/ping”: dial tcp [::1]:27712: connectex: No connection could be made because the target machine actively refused it.” error message when viewing service health check status via UI. I confirmed that http://localhost:27712/ping returns 204 (the port is chosen by Nomad). But the following command fails:

consul info -http-addr=http://[::1]:8500
Error querying agent: Get http://[::1]:8500/v1/agent/self: dial tcp [::1]:8500: connectex: No connection could be made because the target machine actively refused it.

When I replace [::1] with localhost or 127.0.0.1 the command succeeds:

consul info -http-addr=http://127.0.0.1:8500
agent:
check_monitors = 0
check_ttls = 0
checks = 5
services = 5
build:
prerelease =
revision = 3111cb8c
version = 1.8.0
consul:
acl = disabled
bootstrap = true
known_datacenters = 1
leader = true
leader_addr = :8300
server = true
…

Ping [::1] works just fine:

ping [::1]
Pinging ::1 with 32 bytes of data:
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Reply from ::1: time<1ms
Ping statistics for ::1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

I have no config files for Nomad and Consul (I am just getting started). Here’s the Nomad job spec:

  datacenters = ["dc1"]

  type = "service"

  group "servers" {
    count = 1

    task "blah" {
      driver = "raw_exec"

      config {
        command = "blah.exe"
      }

      service {
        port = "http"

        check {
          type     = "http"
          path     = "/ping"
          interval = "10s"
          timeout  = "2s"
        }
      }

      env {
        "BIND_ADDRESS" = "localhost:${NOMAD_PORT_http}"
        "CONFIG_PATH" = "blah.conf"
      }

      resources {
        network {
          mbits = 100
          port "http" {}
        }
      }
    }
  }
} 

Windows 8; etc\hosts is default, proxy and HOME env variables are set.
2

I ran this same experiment on Windows 10 with the same result (failed service health check, everything else is green and working fine); then, I tried it on Linux and it worked. How can I force Nomad (or Consul?) to use IPv4 address for localhost instead of [::1] (if it’s a root cause)?