Opencypher not working from local notebook

0

I can successfully connect to Neptune from my local JupyterLab notebook:

%%graph_notebook_config
{
  "host": "xxx-yyy.us-east-1.neptune.amazonaws.com",
  "port": 8182,
  "auth_mode": "IAM",
  "load_from_s3_arn": "",
  "ssl": true,
  "ssl_verify": true,
  "aws_region": "us-east-1"
}

I am able to run Gremlin queries that return results:

%%gremlin
g.V().limit(5)

However, if I run an OpenCypher query:

%%oc
match (n) return n limit 5

I get error:

{'error': ProxyError(MaxRetryError("HTTPSConnectionPool(host='xxx-yyy.us-east-1.neptune.amazonaws.com', port=8182): Max retries exceeded with url: /openCypher (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 503 Service Unavailable')))"))}

Any idea why Gremlin works but OpenCypher does not? Neptune versions is 1.1.1.0

  • Just for validation, can you execute a %status command successfully? Also, what version of the graph-notebook library are you using? Based on the config output, this looks like an older version. I would suggest that you ensure you're using the latest version of graph-notebook.

  • %status returns error

    {'error': ProxyError(MaxRetryError("HTTPSConnectionPool(host='xxx.yyy.us-east-1.neptune.amazonaws.com', port=8182): Max retries exceeded with url: /status (Caused by ProxyError('Cannot connect to proxy.', OSError('Tunnel connection failed: 503 Service Unavailable')))"))}
    

    I suspect a corporate network policy is blocking access. Not sure what to ask to unblock. What proxy is being referred to in error message?

    These are my package versions and dependencies: tornado==6.2 graph-notebook==3.7.3 jupyterlab==3.6.3

asked a year ago287 views
2 Answers
0

Hello,

Can you confirm if the same error is received when using the below:

%%opencypher match (n) return n limit 5

Also, does the error you receive happen intermittently or whenever you try to run it?

AWS
SUPPORT ENGINEER
answered a year ago
  • Yes, same error using %%opencypher. Error occurs consistenly. Never worked.

0

Talked to internal network team. Solution was to disable all proxies. Added below to notebook.

%env HTTP_PROXY=
%env HTTPS_PROXY=
%env NO_PROXY=
%env ALL_PROXY=
%env http_proxy=
%env https_proxy=
%env no_proxy=
%env all_proxy=
answered 5 months ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions