# EC2 Instance - Remote Console issue **URL:** \ **Category:** Aura & Cloud\ **Tags:** ec2\ **Created:** [January 15, 2019, 2:25pm UTC](https://community.neo4j.com/t/ec2-instance-remote-console-issue/4402 "2019-01-15T14:25:27Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![rosam](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/rosam/32/2860_2.png) [@rosam](https://community.neo4j.com/u/rosam)\ **Post date:** [January 15, 2019, 2:25pm UTC](https://community.neo4j.com/t/ec2-instance-remote-console-issue/4402/1 "2019-01-15T14:25:27Z")
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. ---
**Author:** ![michael.hunger](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/michael.hunger/32/27377_2.png) [@michael.hunger](https://community.neo4j.com/u/michael.hunger)\ **Post date:** [January 15, 2019, 4:21pm UTC](https://community.neo4j.com/t/ec2-instance-remote-console-issue/4402/2 "2019-01-15T16:21:50Z")
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? > **[Configure connectors - Operations Manual](https://neo4j.com/docs/operations-manual/current/configuration/connectors/#connectors-configuration-options)** > > How to configure connectors (Bolt, HTTP, and HTTPS) for Neo4j. ---
**Author:** ![rosam](https://sea1.discourse-cdn.com/flex021/user_avatar/community.neo4j.com/rosam/32/2860_2.png) [@rosam](https://community.neo4j.com/u/rosam)\ **Post date:** [January 16, 2019, 1:18pm UTC](https://community.neo4j.com/t/ec2-instance-remote-console-issue/4402/3 "2019-01-16T13:18:57Z")
```auto # ***************************************************************** # 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 :::* ``` ---
**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:** [February 7, 2019, 11:13pm UTC](https://community.neo4j.com/t/ec2-instance-remote-console-issue/4402/4 "2019-02-07T23:13:53Z")
Have you had a look here? Many common problems addressed. > [@Troubleshooting Connection Issues to Neo4j](https://community.neo4j.com/t/troubleshooting-connection-issues-to-neo4j/129): > > 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: … Some extra details would help. Are you connecting to the console by 7474 or 7473? Do you have an SSL cert?