Skip to content

docs(faq): add port-already-in-use troubleshooting entry - #191

Open
TimeToBuildBob wants to merge 1 commit into
ActivityWatch:masterfrom
TimeToBuildBob:docs/port-conflict-troubleshooting-169
Open

TimeToBuildBob wants to merge 1 commit into
ActivityWatch:masterfrom
TimeToBuildBob:docs/port-conflict-troubleshooting-169

Conversation

@TimeToBuildBob

Copy link
Copy Markdown
Contributor

Adds a troubleshooting entry to the FAQ for ActivityWatch/docs#169: the "Address already in use" / "Port 5600 is in use" startup error.

Content:

Closes #169

Addresses ActivityWatch#169: explain that 'Address already in use'
on port 5600 usually means ActivityWatch is already running, how to
check, and per-OS commands to find the blocking process.

Also notes the improved detection in aw-server-rust >= 0.14
(see ActivityWatch/aw-server-rust#773).

Git-Session-Id: a3f7
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Port conflict handling is not user-friendly (should fallback or guide user)

1 participant