Closed mrichman closed 1 year ago
In case anyone else hits this: set chrome://flags/#allow-insecure-localhost
and you're good.
@mrichman, I'm struggling to get my tunnel to respond to curl (let alone graphexp). Seems like an SSL cert issue. Have you seen this?
* Trying ::1:8182...
* connect to ::1 port 8182 failed: Connection refused
* Trying 127.0.0.1:8182...
* Connected to localhost (127.0.0.1) port 8182 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* TLSv1.3 (OUT), TLS handshake, Client hello (1):
* OpenSSL SSL_connect: Connection reset by peer in connection to localhost:8182
* Closing connection 0
curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to localhost:8182
@tslater I haven't seen this specifically, but have you tried the curl -k (or --insecure) option to ignore cert errors? This is mostly for self-signed certs, but maybe it will help. Also, are you sure the EC2 instance you're tunneling through can connect to Neptune directly?
What's your ssh tunnel command, and curl command?
added a remark on the readme for that. Thanks
I have an SSH tunnel, forwarding local port 8182 to my EC2 instance. I can connect to Neptune via curl if I ignore the SSL cert validation:
I set up
graphConf.js
with the following:In the Graphexp interface, I have websocket secure selected, but when I click Get graph info I get a cert error:
How can I make it ignore the cert validation?