EC2 Instance - Remote Console issue

[rosam]

I have installed Neo4J community edition v.3.5.1.

I can bring up the remote console however I receive error:
"websocket connection to failed establishing a tunnel via proxy server failed."

This is installed on a RHEL7 AWS EC2 instance and I'm stuck on the error when trying to sign in.

[michael_hunger]

Did you open the ports 7474, 7473, 7687 in your security group?

And made the instance in the config listen on all interfaces, not just the loopback interface?

https://neo4j.com/docs/operations-manual/current/configuration/connectors/#connectors-configuration-...

[rosam]

#*****************************************************************
# Network connector configuration
#*****************************************************************

# With default configuration Neo4j only accepts local connections.
# To accept non-local connections, uncomment this line:
dbms.connectors.default_listen_address=0.0.0.0

# You can also choose a specific network interface, and configure a non-default
# port for each connector, by setting their individual listen_address.

# The address at which this server can be reached by its clients. This may be the server's IP address or DNS name, or
# it may be the address of a reverse proxy which sits in front of the server. This setting may be overridden for
# individual connectors below.
dbms.connectors.default_advertised_address=0.0.0.0

# You can also choose a specific advertised hostname or IP address, and
# configure an advertised port for each connector, by setting their
# individual advertised_address.

# 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=true
#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=:7473

# Number of Neo4j worker threads.
#dbms.threads.worker_count=


Also, yes ports are listening...

-bash-4.2$ ss -nlput
Netid State      Recv-Q Send-Q                               Local Address:Port                                              Peer Address:Port
udp   UNCONN     0      0                                                *:68                                                           *:*
udp   UNCONN     0      0                                                *:111                                                          *:*
udp   UNCONN     0      0                                     10.244.8.136:123                                                          *:*
udp   UNCONN     0      0                                        127.0.0.1:123                                                          *:*
udp   UNCONN     0      0                                                *:123                                                          *:*
udp   UNCONN     0      0                                                *:161                                                          *:*
udp   UNCONN     0      0                                                *:514                                                          *:*
udp   UNCONN     0      0                                                *:831                                                          *:*
udp   UNCONN     0      0                                                *:35601                                                        *:*
udp   UNCONN     0      0                                               :::111                                                         :::*
udp   UNCONN     0      0                    fe80::c03:dcff:fe62:24ae%eth0:123                                                         :::*
udp   UNCONN     0      0                                              ::1:123                                                         :::*
udp   UNCONN     0      0                                               :::123                                                         :::*
udp   UNCONN     0      0                                               :::514                                                         :::*
udp   UNCONN     0      0                                               :::831                                                         :::*
tcp   LISTEN     0      128                                      127.0.0.1:199                                                          *:*
tcp   LISTEN     0      128                                              *:111                                                          *:*
tcp   LISTEN     0      128                                              *:22                                                           *:*
tcp   LISTEN     0      100                                      127.0.0.1:25                                                           *:*
tcp   LISTEN     0      128                                             :::7687                                                        :::*
tcp   LISTEN     0      128                                             :::111                                                         :::*
tcp   LISTEN     0      50                                              :::7473                                                        :::*
tcp   LISTEN     0      50                                              :::7474                                                        :::*
tcp   LISTEN     0      128                                             :::22                                                          :::*
tcp   LISTEN     0      100                                            ::1:25                                                          :::*

[david_allen]

Have you had a look here? Many common problems addressed.

Troubleshooting Connection Issues to Neo4j Browser

Troubleshooting Connection Issues to Neo4j (including Browser, Cypher Shell, and Driver Applications) This post describes common issues users may encounter in connecting Neo4j Browser or cypher-shell to a Neo4j database, and how to address them. Connection Timeout Symptom: connection attempts lag for a long time, and then fail with connection timed out errors. Example: $ cypher-shell -a 37.204.217.197 -u neo4j -p myPassword connection timed out: /37.204.217.197:7687 Troubleshooting steps: E…

Some extra details would help. Are you connecting to the console by 7474 or 7473? Do you have an SSL cert?