# Replica cannot connect to core

**URL:** <https://community.neo4j.com/t/replica-cannot-connect-to-core/19660>\
**Category:** Cypher\
**Tags:** kubernetes, cypher\
**Created:** [June 8, 2020, 4:24am UTC](https://community.neo4j.com/t/replica-cannot-connect-to-core/19660 "2020-06-08T04:24:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![helanyao](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/helanyao/32/11841_2.png) [@helanyao](https://community.neo4j.com/u/helanyao)\
**Post date:** [June 8, 2020, 4:24am UTC](https://community.neo4j.com/t/replica-cannot-connect-to-core/19660/1 "2020-06-08T04:24:10Z")

</div>

Please keep the following things in mind:

Hi admin,  
I have installed neo4j 4.0.4 by helm chart

> <https://github.com/neo4j-contrib/neo4j-helm/blob/master/user-guide/USER-GUIDE.md>

After the cluster is up, the replica cannot connect to the core.  
root@c-neo4j-replica-cbb56c96f-f7lpv:/var/lib/neo4j/bin# ./cypher-shell  
username: neo4j  
password: \*\*\*\*\*\*\*\*  
Failed to obtain connection towards WRITE server. Known routing table is: Ttl 1591175610069, currentTime 1591175310075, routers AddressSet=[[10.42.0.1:7687](http://10.42.0.1:7687/)], writers AddressSet=, readers AddressSet=[[10.42.0.1:7687](http://10.42.0.1:7687/)], database ''

Here is the cluster info

 ![Screen Shot 2020-06-04 at 12.02.24 PM](https://us1.discourse-cdn.com/flex021/uploads/neo4jcommunity/original/2X/d/d2274c08c92d59df4a602ac7116c06f665f3b627.png)

debug.log

 ![Screen Shot 2020-06-02 at 9.37.05 PM](https://us1.discourse-cdn.com/flex021/uploads/neo4jcommunity/original/2X/e/e7dcc94070d99d453e9cc8b314b3cb47db9fa45b.png)

---

<div class="post-metadata">

**Author:** ![david\_allen](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/david_allen/32/13090_2.png) [@david\_allen](https://community.neo4j.com/u/david_allen)\
**Post date:** [June 8, 2020, 12:40pm UTC](https://community.neo4j.com/t/replica-cannot-connect-to-core/19660/2 "2020-06-08T12:40:27Z")

</div>

use the bolt:// scheme to connect to an individual read replica. The replica does not have a full copy of the cluster's upstream routing table, and so it is true that when you use neo4j:// as a connection scheme, you cannot obtain a connection to a WRITE server.

More information:

> **[Neo4j documentation - Neo4j Documentation](https://neo4j.com/docs/)**

---

<div class="post-metadata">

**Author:** ![helanyao](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/helanyao/32/11841_2.png) [@helanyao](https://community.neo4j.com/u/helanyao)\
**Post date:** [June 8, 2020, 1:50pm UTC](https://community.neo4j.com/t/replica-cannot-connect-to-core/19660/3 "2020-06-08T13:50:40Z")

</div>

Thanks. You are right, the replica can be connected through bolt.