cancel
Showing results for 
Search instead for 
Did you mean: 

Head's Up! These forums are read-only. All users and content have migrated. Please join us at community.neo4j.com.

"Unable to connect to localhost:7687" Ubuntu 20.04.21

Hello. I've checked multiple references, but I'm unable to start cypher on Ubuntu 20.04.2 LTS. Installed via apt from repo https://debian.neo4j.com stable 4.1. I can see the app running via systemctl status.
Error message: "Unable to connect to localhost:7687, ensure the database is running and that there is a working network connection to it."

curl localhost:7687
curl: (7) Failed to connect to localhost port 7687: Connection refused
$ curl localhost:7474
curl: (7) Failed to connect to localhost port 7474: Connection refused

Here is my config:

> dbms.default_listen_address=0.0.0.0
> #dbms.connectors.default_listen_address=0.0.0.0
> 
> #Bolt connector
> dbms.connector.bolt.enabled=true
> #dbms.connector.bolt.tls_level=DISABLED
> dbms.connector.bolt.listen_address=127.0.0.1:7687
> #dbms.connector.bolt.advertised_address=:7687
> 
> # #HTTP Connector. There can be zero or one HTTP connectors.
> dbms.connector.http.enabled=true
> dbms.connector.http.listen_address=127.0.0.1:7474
> #dbms.connector.http.advertised_address=:0.0.0.0:7474

UFW is disabled. Ports after a new install:

tcp        0      0 127.0.0.1:27017         0.0.0.0:*               LISTEN      726/mongod
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      776/nginx: master p
tcp        0      0 127.0.0.53:53           0.0.0.0:*               LISTEN      698/systemd-resolve
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      765/sshd: /usr/sbin
tcp6       0      0 :::80                   :::*                    LISTEN      776/nginx: master p
tcp6       0      0 :::22                   :::*                    LISTEN      765/sshd: /usr/sbin
1 ACCEPTED SOLUTION

Solved. Wrong jdk (v16-headless) instead of mandatory v11-headless. Once change, config is fine.

View solution in original post

1 REPLY 1

Solved. Wrong jdk (v16-headless) instead of mandatory v11-headless. Once change, config is fine.