Troubleshooting

Common issues and solutions for Miku Miku Beam

Common Issues

Server crashes on startup with 'concurrently' error

This is a Node.js/React issue related to the build process.

Solution:

1. Ensure you have Node.js v18 or higher installed:
   node --version
   
2. Navigate to the web-client directory and reinstall dependencies:
   cd web-client
   npm install
   
3. Rebuild the project:
   make all
   

Nothing appears at http://localhost:3000

The web client needs to be built before the server can serve it.

Solution:

1. Build the web client:
   make webclient
   
2. Ensure the server is running:
   ./bin/mmb-server
   
3. If the issue persists, rebuild everything:
   make all && make run-server
   

In production mode, both frontend and backend are served on the same port (3000).

Requests fail with 'Read timeout' errors

This typically means you don’t have valid proxies configured.

Solution:

1. Add proxies to data/proxies.txt (one per line). Supported formats:

   • protocol://user:password@host:port (with authentication)
   • protocol://host:port
   • host:port (defaults to http)
   • host (defaults to port 8080)

2. Alternatively, run without proxies:

   • CLI: Use the --no-proxy flag
   • Server: Set environment variable ALLOW_NO_PROXY=true

Running attacks without proxies will expose your real IP address to the target.

CLI shows 'No proxies available' error

The attack engine requires proxies by default.

Solution:

Option 1: Add proxies to the file

echo "http://proxy1:8080" >> data/proxies.txt
echo "http://proxy2:8080" >> data/proxies.txt

Option 2: Run without proxies

./bin/mmb-cli attack http_flood http://example.com --no-proxy

Build fails with 'module not found' errors

Dependencies are missing or out of sync.

Solution:

1. Download Go dependencies:
   go mod tidy
   
2. Install Node.js dependencies:
   cd web-client
   npm install
   cd ..
   
3. Or use the prepare command:
   make prepare
   
4. Rebuild the project:
   make all
   

Web client shows errors or doesn't load properly

The React frontend wasn’t built correctly or is outdated.

Solution:

1. Clean previous builds:
   make clean
   
2. Rebuild everything:
   make all
   
3. If issues persist, manually rebuild the web client:
   cd web-client
   npm install
   npm run build
   cd ..
   

Build Issues

Prerequisites Not Met

Ensure you have all required software installed:

Go

Version 1.21 or above

go version

Node.js

Version 18 or above

node --version

npm

Comes with Node.js

npm --version

Missing Data Files

Miku Miku Beam requires certain data files to function:

1. Create data directory

   mkdir -p data
   
2. Create proxies file

   touch data/proxies.txt
   # Add your proxies (one per line)
   echo "http://proxy1:8080" > data/proxies.txt
   
3. Create user agents file

   touch data/uas.txt
   # Add user agents (one per line)
   echo "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36" > data/uas.txt
   

You can also manage proxies and user agents directly through the web interface by clicking the text button to the right of the beam button.

Runtime Issues

Performance Problems

If attacks are running slowly or not performing as expected:

• Increase thread count: Use the --threads flag in CLI or adjust in the web interface

  ./bin/mmb-cli attack http_flood http://example.com --threads 16
  

• Check proxy quality: Slow or dead proxies will impact performance. Test your proxies before use.

• Adjust packet delay: Lower delays send more packets but use more resources

  ./bin/mmb-cli attack http_flood http://example.com --delay 50
  

Connection Issues

If attacks consistently fail to connect, verify:

• Target URL is accessible
• Proxies are working and not blocked
• Firewall settings allow outbound connections
• Target isn’t using advanced DDoS protection

Multi-Client Issues

Simultaneous Attacks Not Working

Each web client maintains its own attack instance. If you’re having issues:

1. Clear browser cache and reload
2. Ensure each client has a unique Socket.IO connection
3. Check browser console for connection errors
4. Verify the server supports multiple connections (it does by default)

Getting Help

If you’re still experiencing issues:

1. Check the FAQ for common questions
2. Review the installation guide to ensure proper setup
3. Open an issue on GitHub with:
   • Your OS and version
   • Go and Node.js versions
   • Complete error messages
   • Steps to reproduce the issue

Enable verbose mode in CLI to get detailed logs that can help diagnose issues:

./bin/mmb-cli attack http_flood http://example.com --verbose