Remote interface connection issue while configuration file changed (localhost instead of remote)

Hi there !

I've installed the neo4j version 3.5.8, and I'm experiencing an issue while enabling the remote HTTPS support.
I've followed this quick tutorial here --> https://neo4j.com/developer/kb/how-do-i-enable-remote-https-access-with-neo4j-30x/

But when I restart the neo4j service, the remote interface is still unavailable:

INFO ======== Neo4j 3.5.8 ========
INFO Starting...
INFO Bolt enabled on 0.0.0.0:7687.
INFO Started.
INFO Remote interface available at https://localhost:7473/

On my configuration file (On path: /etc/neo4j/neo4j.conf), I've enabled the following:

[...]
dbms.connectors.default_listen_address=0.0.0.0
[...]
# Bolt connector
dbms.connector.bolt.enabled=true
#dbms.connector.bolt.tls_level=OPTIONAL
#dbms.connector.bolt.listen_address=:7687

# HTTP Connector. There can be zero or one HTTP connectors.
dbms.connector.http.enabled=false
#dbms.connector.http.listen_address=:7474

# HTTPS Connector. There can be zero or one HTTPS connectors.
dbms.connector.https.enabled=true
dbms.connector.https.listen_address=0.0.0.0:7473

Did I forgot something here ?

Thank you for your help :slight_smile:

what are you getting upon sudo netstat -atnp | grep LISTEN ?

Yup ! I didn't seen any connection unless the following line:
tcp6 0 0 :::7473 :::* LISTEN 5450/java

Complete output:

tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN      1384/master
tcp        0      0 127.0.0.1:5601          0.0.0.0:*               LISTEN      684/node
tcp        0      0 127.0.0.1:27017         0.0.0.0:*               LISTEN      1506/mongod
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      1305/nginx: master
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      1061/sshd
tcp6       0      0 ::1:25                  :::*                    LISTEN      1384/master
tcp6       0      0 :::7687                 :::*                    LISTEN      5450/java
tcp6       0      0 ::1:9200                :::*                    LISTEN      1112/java
tcp6       0      0 127.0.0.1:9200          :::*                    LISTEN      1112/java
tcp6       0      0 :::7473                 :::*                    LISTEN      5450/java
tcp6       0      0 ::1:9300                :::*                    LISTEN      1112/java
tcp6       0      0 127.0.0.1:9300          :::*                    LISTEN      1112/java
tcp6       0      0 :::22                   :::*                    LISTEN      1061/sshd

You have a machine featuring both, ipv4 and ipv6 networking. You could either switch off ipv6 on a network level or amend dbms.jvm.additional=-Djava.net.preferIPv4Stack=true to your neo4j.conf to force neo4j to use ipv4 networking.