DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Related

  • Introducing Graph Concepts in Java With Eclipse JNoSQL, Part 2: Understanding Neo4j
  • Spring Data Neo4j: How to Update an Entity
  • Leveraging Neo4j for Effective Identity Access Management
  • The Beginner's Guide To Understanding Graph Databases

Trending

  • LLM-Powered Deep Parsing for Industrial Inventory Search
  • Building a Zero-Cost Approval Workflow With AWS Lambda Durable Functions
  • Introduction to Tactical DDD With Java: Steps to Build Semantic Code
  • Compliance Automated Standard Solution (COMPASS), Part 11: Compliance as Code, the OSCAL MCP Server Way
  1. DZone
  2. Data Engineering
  3. Databases
  4. Using NGINX to Proxy a Neo4j Instance [Snippets]

Using NGINX to Proxy a Neo4j Instance [Snippets]

Need to remotely connect to your Neo4j instance? Here's how to use a reverse proxy server (NGINX here) to help you gain access to your graph database.

By 
Stefan Armbruster user avatar
Stefan Armbruster
·
May. 21, 18 · Tutorial
Likes (1)
Comment
Save
Tweet
Share
8.3K Views

Join the DZone community and get the full member experience.

Join For Free

There are cases when you want to access your Neo4j instance remotely and you live in an environment where direct access is not possible. This might be caused by technical or organizational restrictions.

One generic solution to this kind of problem is using a VPN. Another alternative to be discussed in this blog post is using a reverse proxy server. I want to show how you can proxy Neo4j using NGINX.

First of all, run a neo4j instance. In order to not have false positive results, I’m using non-standard ports for HTTP (default 7474, using 17474 here) and bolt (default 7687, using 17687 here). Spinning up a test instance is easy in Docker:

docker run --rm -e NEO4J_AUTH=none -p 17474:7474 -p 17687:7687 neo4j 


Note that I’ve switched off authentication, something that might be ok for testing, but is a clear no-go for any other kind of usage.

I’m installing NGINX directly on my system:

apt install nginx


Then we need to map both communication channels: HTTP and bolt. For the HTTP part, we add the following inside the server section of /etc/nginx/sites-available/default this snippet:

location /browser/ {<br/> proxy_pass http://localhost:17474/; # <-- replace with your neo4j instance's http servername + port<br /> }


For the bolt protocol, we amend to /etc/nginx/nginx.conf:

stream {
    server {<br/>listen 7687;<br/> proxy_pass localhost:17687; # <--- replace this with your neo4j server and bolt port<br />    }<br />}


After a restart of NGINX, pointing your browser to http://localhost/browser should show the Neo4j browser.

Neo4j

Published at DZone with permission of Stefan Armbruster. See the original article here.

Opinions expressed by DZone contributors are their own.

Related

  • Introducing Graph Concepts in Java With Eclipse JNoSQL, Part 2: Understanding Neo4j
  • Spring Data Neo4j: How to Update an Entity
  • Leveraging Neo4j for Effective Identity Access Management
  • The Beginner's Guide To Understanding Graph Databases

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

  • RSS
  • X
  • Facebook

ABOUT US

  • About DZone
  • Support and feedback
  • Community research

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 215
  • Nashville, TN 37211
  • [email protected]

Let's be friends:

  • RSS
  • X
  • Facebook