Error initializing listener of type tcp: listen tcp 127.0.0.1:8200: bind: address already in use

[san6789]

I am trying to start "vault server -dev" i am getting below error azureuser@vault-1:~$ vault server -dev Error parsing listener configuration. Error initializing listener of type tcp: listen tcp 127.0.0.1:8200: bind: address already in use 2021-10-12T12:59:26.053Z [INFO] proxy environment: http_proxy="" https_proxy="" no_proxy="" azureuser@vault-1:~$

NOTE: I have installed vault on azure VM my config.json file looks like :

{ "listener":[ { "tcp": { "address" : "my publicip:8200", "tls_disable" : 1 }

}],
"api_addr": "http://my public ip:8200",
"storage": {
    "file": {
    "path" : "/opt/vault-data"
    }
 },
"max_lease_ttl": "10h",
"default_lease_ttl": "10h",
"ui":true
}

[reyyzzy]

I am trying to start "vault server -dev" i am getting below error azureuser@vault-1:~$ vault server -dev Error parsing listener configuration. Error initializing listener of type tcp: listen tcp 127.0.0.1:8200: bind: address already in use 2021-10-12T12:59:26.053Z [INFO] proxy environment: http_proxy="" https_proxy="" no_proxy="" azureuser@vault-1:~$

NOTE: I have installed vault on azure VM my config.json file looks like :

{ "listener":[ { "tcp": { "address" : "my publicip:8200", "tls_disable" : 1 }

}],
"api_addr": "http://my public ip:8200",
"storage": {
    "file": {
    "path" : "/opt/vault-data"
    }
 },
"max_lease_ttl": "10h",
"default_lease_ttl": "10h",
"ui":true
}

how did u solve it?

[onlookor]

Same error. I looked up the port 8200 with lsof, nothing found.

[onlookor]

Ha! Duplicate listeners attempting to be created #229

[ahmetonurslmz]

Hello,

I’ve written solution in the link. Please check it out to fix the issue. https://en.ahmetonursolmaz.com.tr/error-initializing-listener-of-type-tcp-listen-tcp-127-0-0-18200-bind-address-already-in-use/

[michvllni]

@ahmetonurslmz your workaround won't help when deploying via docker (which is done in this issue) as the container exits after the exception is thrown.

The solution is, as @onlookor pointed out, in #229 (When using a mounted config, use command: server instead of command: server -config=/vault/config/vault-config.hcl)