Troubleshooting

Troubleshooting

Note

Run python3 start.py DOCTOR first. It catches most install and raw-socket problems faster than reading this page.

On this page

• Installation
• Raw sockets
• Proxies
• Layer 4
• Layer 7
• Web panel
• Processes

Start with:

python3 start.py DOCTOR

It catches missing imports, a bad config, missing wordlists, and raw-socket problems before you spend time on a run.

Installation

ModuleNotFoundError

The virtual environment is not active, or dependencies were installed into another interpreter.

source .venv/bin/activate
python -m pip install -r requirements.txt
python start.py DOCTOR

On Windows:

.venv\Scripts\Activate.ps1
python -m pip install -r requirements.txt

PyRoxy install fails

The requirements use a git URL:

pyroxy @ git+https://github.com/MatrixTM/PyRoxy.git@...

Install git and retry:

sudo apt install git
pip install -r requirements.txt

Python too old

Python 3.11 is the minimum. Check:

python --version

Use python3.11, python3.12, or newer when creating the venv.

impacket build errors

Use a recent Python and a clean virtual environment. On Linux, make sure a compiler is available:

sudo apt install build-essential python3-dev

Wheels are available for common platforms; pinning the supported Python version avoids most source builds.

Raw sockets

Cannot create a raw socket

Run as root on Linux:

sudo python3 start.py SYN 192.0.2.10:80 10 30

Or grant the capability to the interpreter:

sudo setcap cap_net_raw+ep "$(readlink -f "$(which python3)")"

In Docker, add:

cap_add:
  - NET_RAW

Windows normally requires an elevated shell, and some raw-socket features remain limited.

Proxies

Proxy check failed

The download worked but no proxy passed the check. This is usually a network or target problem, not a syntax problem.

• Try again with a different provider.
• Test the check URL in a browser.
• Lower the thread count.
• Verify that the proxy file is not empty.

Empty proxy file, running flood without proxies

This is informational. The run continues without proxies. Add working proxies to files/proxies/<name>.txt or delete the file so it is downloaded again.

Proxy file not found

The CLI accepts a bare filename:

python3 start.py GET https://example.com 0 10 http.txt 5 30

http.txt means files/proxies/http.txt. Paths and subdirectories are rejected.

Layer 4

Port defaults to 80

If no port is supplied, Layer 4 uses 80:

python3 start.py UDP 192.0.2.10 10 30

Supply ip:port for anything else.

Minecraft methods do nothing

• Confirm the server port, usually 25565.
• MCBOT needs a server that accepts the login flow and may need /register.
• The protocol version is read from the server when possible; otherwise MINECRAFT_DEFAULT_PROTOCOL in config.json is used.

Amplification sends but the target sees nothing

The source must be spoofable and the reflector must answer the exact payload. See Amplification.

Layer 7

No output

Add debug at the end:

python3 start.py GET https://example.com 0 10 http.txt 1 30 debug

You should see one line per second with PPS and BPS.

Requests return 403 or a challenge page

The target is using a WAF or bot challenge. Try a bypass method such as CFB, DGB, GSB, or STOMP, and expect them to change over time. A bypass is never guaranteed.

HTTPS errors

MHDDoS uses TLS 1.2+ and intentionally disables certificate and hostname verification. If the target only supports TLS 1.0/1.1, the connection fails by design. If the target uses a self-signed certificate, the connection still works.

Cannot resolve hostname

Check DNS from the same machine:

python3 start.py CHECK example.com
nslookup example.com

A proxy-only DNS failure can also cause this. Try the same target without proxies.

Web panel

See Web Panel for install and port problems.

Common fixes:

cd web
npm ci
npm run build

If the page loads but API calls return 401, set a stable JWT_SECRET in web/.env and restart.

Processes

STOP does not stop my run

STOP only targets other start.py processes launched from the same checkout. It does not kill unrelated Python processes, and it cannot stop a process from another clone. Use Ctrl+C in the original terminal.

Too many threads or file descriptors

Thread and RPC values are not clamped. Lower them, or raise the file-descriptor limit:

ulimit -n 65535

start_workers reports when the OS refuses to create a thread, but it cannot prevent resource exhaustion from values that are too high.

Still stuck

Collect:

python3 --version
python3 start.py --version
python3 start.py DOCTOR

Then open an issue with the target type, method, full command, and the relevant error output. Do not include proxy credentials or private keys.