Skip to content

v2.5.4 - macOS Port Conflict Fix

Choose a tag to compare

View all tags
@Nostoi Nostoi released this 04 Jan 06:43
· 1624 commits to master since this release
v2.5.4
2a2249d

v2.5.4 - macOS Port Conflict Fix

🐛 Bug Fixes

Telnet Server Port Conflict on macOS

  • Changed default telnet port from 5000 to 5001
  • Resolves conflict with macOS AirPlay Receiver (Monterey+)
  • Updated all configuration files and documentation

📝 Changes

  • mud/main.py: Updated socketserver default port to 5001
  • mud/config.py: Changed PORT environment default from 5000 to 5001
  • Dockerfile: Updated EXPOSE directive to port 5001
  • docker-compose.yml: Updated port mapping to 5001
  • README.md: Updated all port references and added macOS warning note

📚 Documentation

  • Added macOS AirPlay Receiver warning in README Quick Start section
  • Explains port 5000 conflict with macOS Monterey+ AirPlay service
  • Provides example of custom port usage: --port 4000

⚠️ Breaking Changes

None - Backward compatible. Users can still specify custom ports via --port flag.

📊 Impact

This fix resolves the "address already in use" error that macOS users encounter when starting the telnet server, caused by macOS ControlCenter process binding to port 5000 for AirPlay Receiver.

Full Changelog: v2.5.3...v2.5.4

Assets 2
Loading