Skip to content

Port 8765 is already in use

Symptoms

ArchiveMind normally serves its interface at http://127.0.0.1:8765/, but that address shows something else (or nothing), or a startup message mentions the port being busy.

What this usually means

Port 8765 is just ArchiveMind's preferred address on your machine. Another program — or another copy of ArchiveMind — can already be using it. ArchiveMind's launcher handles this safely by design:

  • If the occupant is ArchiveMind already serving your same catalogue, the launcher simply reuses it and opens the interface there — no second copy is started.
  • If the occupant is anything else (another program, or ArchiveMind on a different catalogue), the launcher notes this and starts on a nearby free port instead (it tries the next ports above 8765). It never interferes with, or shuts down, the other program.

So a busy port is normally absorbed automatically — the interface just lives at a slightly different address for that session.

Safe steps to try

  1. Look at the address of the window ArchiveMind opened — if it opened at all, the port it chose is in the address (for example http://127.0.0.1:8766/). That address is correct; use it.
  2. If no window opened, try http://127.0.0.1:8765/ and the next few ports up (8766, 8767, …) in a browser.
  3. If you suspect a stale ArchiveMind is holding the port, quit it properly — via its own page's Quit ArchiveMind button, or Activity Monitor / Task Manager — then start ArchiveMind again. See Restarting ArchiveMind safely.

What not to delete or change

  • Do not force-quit unknown programs just because they hold port 8765 — ArchiveMind will route around them on its own.
  • Do not change firewall or network settings; the port is machine-internal.
  • Do not delete the catalogue database — port conflicts have nothing to do with the catalogue.

Information to collect for support

  • Any startup message text about the port.
  • Which address finally worked, if any.
  • The newest archivemind.log — see Finding logs.