# Custom transport port
**URL:** https://discuss.elastic.co/t/custom-transport-port/56689
**Category:** Elasticsearch
**Created:** [July 29, 2016, 1:44am UTC](https://discuss.elastic.co/t/custom-transport-port/56689 "2016-07-29T01:44:17Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@zozo6015](https://discuss.elastic.co/u/zozo6015)
#### Post date: [July 29, 2016, 1:44am UTC](https://discuss.elastic.co/t/custom-transport-port/56689/1 "2016-07-29T01:44:17Z")
Hello,
I have an es cluster and I need to use custom transport path for various reasons. I have set transport.tcp.port: 19300:19400 on all nodes but the nodes cannot discover eachother.
Any help how to get it running?
cheers,
Peter
---
### Author:  [@Joshua\_Rich](https://discuss.elastic.co/u/Joshua_Rich)
#### Post date: [July 29, 2016, 5:04am UTC](https://discuss.elastic.co/t/custom-transport-port/56689/2 "2016-07-29T05:04:28Z")
I don't think Elasticsearch accepts a colon separating the port range. Did it throw an exception on start-up?
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 29, 2016, 8:27am UTC](https://discuss.elastic.co/t/custom-transport-port/56689/3 "2016-07-29T08:27:45Z")
You need to define the nodes as unicast list.
Elasticsearch tries only to connect to ports from 9300-9399 if port is not set in unicast list.
---
### Author:  [@zozo6015](https://discuss.elastic.co/u/zozo6015)
#### Post date: [July 29, 2016, 1:54pm UTC](https://discuss.elastic.co/t/custom-transport-port/56689/4 "2016-07-29T13:54:42Z")
Actually auto discovery is working with custom ports. It was firewall blocking the nodes from talking to eachother.
Thanks all for you help.
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 29, 2016, 6:57pm UTC](https://discuss.elastic.co/t/custom-transport-port/56689/5 "2016-07-29T18:57:54Z")
Oh? Really?
I guess all nodes are using the same range then???
---
### Author:  [@zozo6015](https://discuss.elastic.co/u/zozo6015)
#### Post date: [July 30, 2016, 11:34am UTC](https://discuss.elastic.co/t/custom-transport-port/56689/6 "2016-07-30T11:34:44Z")
Yes, all nodes using the same exact same range and we are also using the gce plugin for the autodiscovery.
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [July 30, 2016, 11:48am UTC](https://discuss.elastic.co/t/custom-transport-port/56689/7 "2016-07-30T11:48:53Z")
Ha! So you changed es-port in GCE metadata then?
---
### Author:  [@zozo6015](https://discuss.elastic.co/u/zozo6015)
#### Post date: [July 30, 2016, 12:12pm UTC](https://discuss.elastic.co/t/custom-transport-port/56689/8 "2016-07-30T12:12:15Z")
No, not touched any metadata on GCE, only thing I did I set up the transport.tcp.port: and http:port inside the elasticsearch configuration and modified the firewall settings on GCE to allow traffic on the configured ports. And added the gce related configuration in the elasticsearch.yml. Anything else worked out of the box if I can say that.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [July 5, 2017, 10:31pm UTC](https://discuss.elastic.co/t/custom-transport-port/56689/9 "2017-07-05T22:31:33Z")