# Testing connection to Neo4J fails

**URL:** <https://community.siren.io/t/testing-connection-to-neo4j-fails/103>\
**Category:** Siren Platform/Investigate Tech Support Community\
**Created:** [July 25, 2019, 9:31pm UTC](https://community.siren.io/t/testing-connection-to-neo4j-fails/103 "2019-07-25T21:31:30Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![ekeller](https://yyz2.discourse-cdn.com/flex032/user_avatar/community.siren.io/ekeller/32/40_2.png) [@ekeller](https://community.siren.io/u/ekeller)\
**Post date:** [August 1, 2019, 1:38pm UTC](https://community.siren.io/t/testing-connection-to-neo4j-fails/103/11 "2019-08-01T13:38:51Z")

</div>

Hi Julia,

The timeout error may be caused by the fact that the ElasticSearch server is not able to reach the NEO4J server (due to firewall rules, network issues or a wrong connection URL).

Can you check the connection string you are using ?

You may have a look at the current NEO4J documentation:  
[http://neo4j-contrib.github.io/neo4j-jdbc/](http://neo4j-contrib.github.io/neo4j-jdbc/)

We currently support the HTTP protocol. So, you connection string should look like this:  
`jdbc:neo4j:http://<host>:<port>/`

You may also test from your ElasticSearch server if the Neo4J server is reachable. A typical telnet command should do the job. Typically from a terminal:

```
telnet myneo4jservername 7474

```

Notice that the port is not a standard HTTP port. By default, Neo4J is using 7474:  
[https://neo4j.com/docs/operations-manual/current/configuration/ports/](https://neo4j.com/docs/operations-manual/current/configuration/ports/)

You should check which port is currently in use in your current configuration.

Let me know.

---

_[View the full topic](https://community.siren.io/t/testing-connection-to-neo4j-fails/103)._