The problem is probably right here. Read the comment:
# 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.default_advertised_address=0.0.0.0
The way Neo4j clients work, the server needs to know what it's externally valid IP address is, and that's what this setting controls. 0.0.0.0 isn't a valid IP address, so probably your client is getting confused by Neo4j's routing table.
So I think your solution is going to be to set that setting to the externally valid IP that your client (the browser) uses to contact the server.
Full gory details on why are here: Querying Neo4j Clusters. How Neo4j clusters and smart query… | by David Allen | Neo4j Developer Blog | Medium