Neo4J Server not responding to browser

General Startups
1

Using Neo4J Community edition...detail below:

The problem that we're encountering has been recurring in out current bare mental centos 9 env. Can't seem to pin point what cause this. The status show below the server was up and running for 4 days. But then browser/curl cli can't call up the /browser. It keep returning 404 as show in the curl cli.
The server has to be stopped/wait 5 sec/started...then browser/curl cli can connect the /browser page successfully.

Has anyone seen this problem before? A know bug?

sudo systemctl status neo4j
● neo4j.service - Neo4j Graph Database
Loaded: loaded (/usr/lib/systemd/system/neo4j.service; enabled; preset: disabled)
Active: active (running) since Wed 2026-06-10 10:21:27 PDT; 1 month 4 days ago
Main PID: 3283564 (java)
Tasks: 113 (limit: 203060)
Memory: 921.2M (peak: 1.3G)
CPU: 4h 5min 49.617s
CGroup: /system.slice/neo4j.service
├─3283564 /usr/bin/java -Xmx128m -classpath "/usr/share/neo4j/lib/*:/usr/share/neo4j/e>
└─3283595 /usr/lib/jvm/java-21-openjdk-21.0.10.0.7-2.el9.x86_64/bin/java -cp "/var/lib>

curl -s http://10.206.237.212:7474/ | grep -i version
{"bolt_routing":"neo4j://10.206.237.212:7687","query":"http://10.206.237.212:7474/db/{databaseName}/query/v2","transaction":"http://10.206.237.212:7474/db/{databaseName}/tx","bolt_direct":"bolt://10.206.237.212:7687","neo4j_version":"5.26.25","neo4j_edition":"community"}

curl -i http://10.206.237.212:8474/browser/
HTTP/1.1 404 Not Found
Date: Wed, 15 Jul 2026 23:40:29 GMT
Access-Control-Allow-Origin: *
Pragma: no-cache
Content-Security-Policy: default-src 'self'; script-src 'self' cdn.segment.com canny.io; img-src 'self' guides.neo4j.com data:; style-src 'self' fonts.googleapis.com 'unsafe-inline'; font-src 'self' fonts.gstatic.com; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; connect-src 'self' api.canny.io api.segment.io ws: wss: http: https:
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
X-XSS-Protection: 1; mode=block
Cache-Control: must-revalidate,no-cache,no-store
Content-Type: text/html;charset=iso-8859-1
Content-Length: 371

Error 404 Not Found

HTTP ERROR 404 Not Found

URI:/browser/
STATUS:404
MESSAGE:Not Found
SERVLET:default
2

@akso

this is Neo4j version 5.26.25. correct?

Also your example includes

curl -s http://10.206.237.212:7474/ | grep -i version
{"bolt_routing":"neo4j://10.206.237.212:7687","query":"http://10.206.237.212:7474/db/{databaseName}/query/v2","transaction":"http://10.206.237.212:7474/db/{databaseName}/tx","bolt_direct":"bolt://10.206.237.212:7687","neo4j_version":"5.26.25","neo4j_edition":"community"}

which appear to be requesting a connection to host=10.206.237.212 and on port 7474 and this succeeds. but then the 2nd connection, i.e.

curl -i http://10.206.237.212:8474/browser/
HTTP/1.1 404 Not Found

results in a 404-Page Not found but it is for the same host=10.206.237.212 but now a different port, i.e. 8474. Is this a typo? or are you running multiple Neo4j instsances on the same host, where the 1st instance serves its browser on port 7474 and the 2nd on 8474?

3

Correct...the version is 5.26.25 as shown in the curl -s cli.

Sorry about the port confusion.

let me clarify:

We have 2 instances running. one on port http://7484 bolt://7687. Another on port http://8474 bolt://8687. The http://7484 is working fine, so I use that instance to grap the version of the server.

the http://8474 is the one that have problem. In fact, I can connect to http://7484 direct the connection to bolt://8687 and this work. So only the http://8474 return 404.

We found that if the server's been running for while (days) and there's been no client(browser) access, then the server would fall into this trap...and must be restarted. I simply just restart through systemctl restart neo4j2.service and everything is good again.