Troubleshoot
Beacon port conflict
Handling issues with binding to a port
About
XPipe utilizes an internal HTTP server to realize inter-process communication between different terminal processes, API calls, and MCP server functions. The HTTP server binds to localhost on the port 21721 (or 21722 for PTB versions). If this port is occupied or blocked, then XPipe will try to fall back to another port in the range of 21723-21743. If this still fails, then XPipe won't be able to start up.
Managing ports
You can override the default port of the XPipe application. For this, you have to set the XPIPE_BEACON_PORT environment variable on your system to the new port and restart XPipe.
Startup failures
If XPipe reports that it can't bind to a port, you can do multiple things:
- Restart your system: Especially on Windows, the networking can be a bit buggy, sometimes a good old restart fixes these issues
- Check if any AntiVirus or other monitoring program might interfere with the port allocation
- On Windows, check if the port is in the excluded port range with
netsh interface ipv4 show excludedportrange protocol=tcp. Your administrator might have configured something custom there