New Neo4j browser (3.2.0) cannot connect using HTTPS

[sgehrig]

After updating to Neo4j 3.2.0 the browser cannot connect to the database using HTTPS instead of Bolt any more. Due to firewall restrictions we're not able to open the Bolt ports to the world to allow web socket connections to the Bolt port directly. Instead we have to use the opened HTTPS ports.

This worked with 3.1.x but with 3.2.0 we cannot find a way to tell the browser to use HTTPS instead of Bold for connecting to the database.

[akollegger]

Hi @sgehrig !

Thanks for raising this issue. This is a known regression in Neo4j 3.2 which will be addressed in a patch release. The rewritten Neo4j Browser did not migrate the code for http or https. Instead, the javascript driver itself will be upgraded to provide this functionality.

Apologies,
Andreas

[sgehrig]

@akollegger Is there any release date yet? Oh, and thx for taking care of that issue.

[naisanza]

@sgehrig Bolt encryption should still be wrapped within TLS, I believe. So would it work if you set your environment's reverse proxy to forward something like bolt.server.com:443 -> internal-bolt:7687?

[sgehrig]

@naisanza Yes. A proxy would be an option. But in our setup we'd prefer to have the “old" HTTPS connection back. Nobody here wants to change the setup ;-) (and it's not me who's responsible).

[kuzmik]

Bump for release date

[jexp]

Anyone else who is affected by Neo4j Browser in 3.2 not being able to use http(s) anymore, can you please drop an email with all details (why exactly you need it, for us to collect feedback) to devrel@neo4j.com to inform the decision process

As a work-around you can replace the browser-jar with one from 3.1.x and it should work.

[DanielOverdevest]

+1 We've same problem with redirect BOLT protocol traffic (due port restrictions). Please supply a solution to run Neo4J Browser with only ports 80/443.

[arne-at-daten-und-bass]

Also got stuck in this (using the official Docker image). For me it worked to go back to v3.0.9:

Just switched:

FROM neo4j:latest
...

To:

FROM neo4j:3.0.9
...

Of course, not a real "solution" but it got me being able to connect via browser just as before (even with custom self-signed certificates).

Version 3.1.x did not work instantly, yet I did not further investigate that (seemed like the same issue). I rather switched further down to v3.0.9 as I did not need the latest release.

[jfleck1]

bump. I downgraded from neo4j:latest to neo4j:3.0.9 and it also fixed my SSL connection issues with the browser (which is awesome btw).

[chandan4raj4]

@akollegger can you please tell how much more time can we expect for that patch to get released .Now I am using its public version and am planning to use it for my official project and is there any work around for this bug ???

[andrewhl]

+1

[ecirtap]

+1 For sure, https is a more friendly protocol for firewalls and reverse proxies than Bolt can be... Stuck in 3.1.4 (we had to tick "dont'use bolt" in the browser side params for each client to work properly).