Server port 8799 collides with an OpenMausBot server on the same Windows host (WSL localhost forwarding), breaking MausBot's browser tool with "unauthorized"

Open
#25 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

Start by locating the server setup and startup code that binds Dusk to 127.0.0.1:8799, then trace how MCP requests are authenticated. Check how setup handles configuration and where project documentation explains running the server. Done means the port can be configured, collisions and requests using another install’s token get a clear response, and the documented setup covers running alongside MausBot; the issue does not name files or tests.

Written by the indexing model from the issue text.

Description

Version

0.2.15

Platform

Own server in WSL2 on a Windows PC that also runs OpenMausBot natively

What happened

Dusk listens on 127.0.0.1:8799 inside WSL. WSL localhost forwarding publishes that as 127.0.0.1:8799 on Windows (wslrelay.exe). The MausBot server on the same PC listens on 0.0.0.0:8799. On Windows the more specific 127.0.0.1 bind wins, so MausBot's own local calls to 127.0.0.1:8799 reach Dusk instead. Every MausBot bot then fails at the start of a turn with:

The MCP server 'browser' failed to initialize: failed to get tools: calling "tools/list": unauthorized

Nothing tells the user which app took the port.

Suggested fix
  1. Make the server port configurable in setup (DUSK_PORT) and check at start whether 8799 already answers on the host, and pick another port if it does.
  2. When a local request arrives with a token from another install, answer with a clear "this is Dusk, not your other server" error instead of plain unauthorized.
  3. Document running Dusk next to MausBot / OpenMausBot (people migrating keep both running).
Dominant language
TypeScript
Stars
277
Forks
27
Avg merge
2h 47m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from DuskBotAI/duskbot

All issues in DuskBotAI/duskbot

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.