# Remote TransportClient with Transport profile : GRAVE: NoNodeAvailableException

**URL:** <https://discuss.elastic.co/t/remote-transportclient-with-transport-profile-grave-nonodeavailableexception/45428>\
**Category:** Elasticsearch\
**Created:** [March 25, 2016, 9:16am UTC](https://discuss.elastic.co/t/remote-transportclient-with-transport-profile-grave-nonodeavailableexception/45428 "2016-03-25T09:16:30Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\
**Post date:** [March 25, 2016, 9:16am UTC](https://discuss.elastic.co/t/remote-transportclient-with-transport-profile-grave-nonodeavailableexception/45428/1 "2016-03-25T09:16:30Z")

</div>

Hi,

I have a test serveur with several IP : an internal and a VPN

Elasticsearch used to run on the VPN one while we were in development, but now I have  
to secure it for the production env.

After testing lot of configurations, that's what I have :

# publish/bind localhost (127.0.0.1:9300)

```
network.host: 127.0.0.1
transport.tcp.port: 9300

```

# publish/bind VPN for the plugin Head (172.16.50.12:9200)

```
http.port: 9200
http.host: 172.16.50.12

```

# publish/bind internal IP for internal communication (10.90.213.132:9300)

```
transport.profiles.client.port: 9300
transport.profiles.client.bind_host: 10.90.213.132
transport.profiles.client.publish_host: 10.90.213.132

```

# publish/bind VPN IP for remote DEV (172.16.50.12:9300)

```
transport.profiles.dmz.port: 9300
transport.profiles.dmz.bind_host: 172.16.50.12
transport.profiles.dmz.publish_host: 172.16.50.12

```

Everything starts well :

```
[2016-03-25 09:14:13,979][INFO][transport] [es-dev-node-integration] publish_address {127.0.0.1:9300}, bound_addresses {127.0.0.1:9300}
[2016-03-25 09:14:13,980][INFO][transport] [es-dev-node-integration] profile [dmz]: publish_address {172.16.50.12:9300}, bound_addresses {172.16.50.12:9300}
[2016-03-25 09:14:13,980][INFO][transport] [es-dev-node-integration] profile [client]: publish_address {10.90.213.132:9300}, bound_addresses {10.90.213.132:9300}
[2016-03-25 09:14:17,011][INFO][http] [es-dev-node-integration] publish_address {172.16.50.12:9200}, bound_addresses {172.16.50.12:9200}

```

Everything is OK, I can connect to the HTTP head plugin, internal communication works well on 10.\*.  
BUT, remote connections with TransportClient from a VPN PC failed with :

```
GRAVE: NoNodeAvailableException[None of the configured nodes are available: [{#transport#-1}{172.16.50.12}{172.16.50.12:9300}]]
    at org.elasticsearch.client.transport.TransportClientNodesService.ensureNodesAreAvailable(TransportClientNodesService.java:290)
    at org.elasticsearch.client.transport.TransportClientNodesService.execute(TransportClientNodesService.java:207)
    at org.elasticsearch.client.transport.support.TransportProxyClient.execute(TransportProxyClient.java:55)
    at org.elasticsearch.client.transport.TransportClient.doExecute(TransportClient.java:286)
    at org.elasticsearch.client.support.AbstractClient.execute(AbstractClient.java:351)
    at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:85)
    at org.elasticsearch.action.ActionRequestBuilder.execute(ActionRequestBuilder.java:59)

```

Before, this configuration, the same code, connected to the VPN IP was not a problem. There  
is something wrong with the "Transport profile" from a remove IP. The same code on the  
machin works ... Is there something special in remote with a profile ?

Thanks!  
Xavier

---

<div class="post-metadata">

**Author:** ![xavierfacq](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/xavierfacq/32/8744_2.png) [@xavierfacq](https://discuss.elastic.co/u/xavierfacq)\
**Post date:** [March 29, 2016, 3:04pm UTC](https://discuss.elastic.co/t/remote-transportclient-with-transport-profile-grave-nonodeavailableexception/45428/2 "2016-03-29T15:04:28Z")

</div>

After reading this doc : [https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/transport-client.html](https://www.elastic.co/guide/en/elasticsearch/client/java-api/current/transport-client.html)  
I finaly set "client.transport.sniff" to "false". I don't know why, but it's works... I'm not shure it"s the good configuration but it's ok like that...

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 5, 2017, 11:04pm UTC](https://discuss.elastic.co/t/remote-transportclient-with-transport-profile-grave-nonodeavailableexception/45428/3 "2017-07-05T23:04:23Z")

</div>