Neo4j社区版无法连接求助：同步骤安装改端口仍失败

Hey there, let's break down why your Neo4j Community Edition isn't connecting even after adjusting ports, and walk through actionable fixes step by step:

When running two Neo4j editions side-by-side, the most common problems stem from service conflicts, incomplete config changes, or resource locks. Here's how to tackle each:

1. Service Name Conflict #

By default, both editions try to register a Windows service named neo4j—and you can't have duplicate service names. This means your Community install either failed to register properly or overrode the Enterprise service without you noticing.

• Fix: Clean up old services and install Community with a unique name:
  1. Open CMD as Administrator
  2. Uninstall any existing Neo4j services (run this from both Enterprise and Community directories):

     neo4j.bat uninstall service
     

  3. Install Community Edition with a distinct service identifier:

     neo4j.bat install service --name neo4j-community
     

  4. Start the new service:

     net start neo4j-community
     

2. Incomplete Port Configuration #

Changing just the bolt port isn't enough—Neo4j uses three core ports, all of which need to be unique from your Enterprise instance.

• Open <community-neo4j-dir>/conf/neo4j.conf and update these lines (use ports not used by Enterprise):

  # Bolt connection port
  dbms.connector.bolt.listen_address=:7688
  # HTTP web interface port
  dbms.connector.http.listen_address=:7475
  # HTTPS port (adjust if Enterprise uses 7473)
  dbms.connector.https.listen_address=:7476
  

• Restart the Community service to apply changes:

  net stop neo4j-community
  net start neo4j-community
  

3. Data Directory Lock Conflict #

If you didn't set a unique data folder for Community, it's likely trying to access the same directory as Enterprise—Neo4j locks its data folder, so two instances can't share it.

• Update the data directory path in neo4j.conf:

  dbms.directories.data=data-community
  

• Make sure the Windows user running the neo4j-community service has full read/write permissions to this new folder.

4. Check Service Status & Logs #

If the service starts but you still can't connect, logs will tell you exactly what's wrong:

• Logs live in <community-neo4j-dir>/logs/neo4j.log and <community-neo4j-dir>/logs/debug.log
• Look for errors like "Address already in use" (port conflict still exists) or "Permission denied" (folder access issue)
• Verify the service is running with:

  sc query neo4j-community
  

  A STATE: 4 RUNNING result means the service is active—if not, the logs will explain why it failed to start.

5. Firewall/Antivirus Block #

Windows Firewall or third-party antivirus might be blocking the new ports you assigned to Community.

• Add inbound/outbound rules for your new ports (7688, 7475, etc.) in Windows Firewall
• Temporarily disable antivirus to test if it's the blocker (remember to re-enable it afterward)

内容的提问来源于stack exchange，提问作者Pantea