Openbullet This Config Does Not Support The Provided Wordlist Type Better May 2026

"This config does not support the provided wordlist type" in OpenBullet occurs when the specific data type assigned to your imported wordlist (e.g., Credentials

) is not listed as an "Allowed Wordlist Type" within the configuration settings. Core Cause OpenBullet uses Wordlist Types (WLTYPE) to define how data lines (like

) are validated and split into variables. If a config is strictly built for but you attempt to run it with a wordlist imported as Credentials , OpenBullet will block the job to prevent variable errors. How to Fix the Error Method 1: Update Config Settings (Recommended)

You can tell the configuration to accept your specific wordlist type. OpenBullet and navigate to the Select the config you want to use and go to its Look for the Other Options Allowed Wordlist Types

and add the type that matches your wordlist (e.g., if your wordlist is "EmailPass", ensure "EmailPass" is checked or listed). the config and restart the job. Method 2: Re-import or Edit Wordlist Type

Alternatively, you can change the type assigned to the wordlist itself so it matches what the config expects. : Delete the wordlist from the tab and re-import it, ensuring you select the correct Wordlist Type Credentials ) from the dropdown menu during the import process. Direct Edit : In some versions, you can right-click the wordlist in the Wordlist Manager and select to change its type. Method 3: Modify the Environment.ini If you frequently use custom types (like "This config does not support the provided wordlist

), you may need to define them in your environment settings. Locate the Environment.ini file in your OpenBullet root folder. Ensure the [WORDLIST TYPE]

definitions match the syntax and separators your wordlist uses.

Note that the first type listed in this file is often the default for new configs. Common Wordlist Types Expected Format Variables Created Credentials input.USER input.PASS email@domain.com:pass input.EMAIL input.PASS username:pass input.USER input.PASS input.DATA Do you need help defining a custom regex for a new wordlist type in your Environment.ini

[REQUEST] Wordlist with Multiple Types · Issue #590 - GitHub 7 Apr 2020 —

Solution B: Add a Custom Wordlist Type (The "Missing Type" Fix)

Sometimes, a config requires a specific, non-standard wordlist type (e.g., Email:Pass:BirthDate). If that type isn't in your settings, you will get the error. Go to Settings > Wordlist Types

1. Go to Settings > Wordlist Types.
2. Click the Plus (+) button to add a new type.
3. Enter the Name (exactly as the config requires, check the config's info or ask the author).
4. Define the Slices.
   • If the format is email:pass:birthdate, you have 3 parts.
   • Usually, OpenBullet defaults to capturing everything, but you may need to verify how the config captures data.
5. Save Settings.
6. Reload your wordlist and select the new type you just created.

OpenBullet 1 vs. OpenBullet 2 Differences

OpenBullet 1 (Legacy): This version relies heavily on preset "Wordlist Types" (e.g., User:Pass, Email:Pass). If you select a config made for Email:Pass and load a User:Pass wordlist, the error triggers immediately because the bot doesn't know how to map "john123" to an email variable.

OpenBullet 2: OB2 is more flexible. It primarily uses a "Lines" type. However, configs define inputs in the Config Settings. If the config defines a variable like <EMAIL> and <PASSWORD> but your wordlist only provides one column of data (like just <USER>), the config will reject it because the required variables are missing.

✅ Step 2 – Inspect Your Wordlist

Open the wordlist file in a text editor (Notepad++ recommended).
Look at the first 5–10 lines:

• Does each line contain : → probably Email:Pass or User:Pass
• Does each line contain | → custom delimiter
• Is there only one field → Email only or User only

How to fix it — step‑by‑step

1. Identify the expected wordlist type

• Open the config file (in the Config Editor) and find where it specifies the wordlist type. Look for labels like Wordlist Type, Combo format, Input type, or check comments in the config.
• Common expected types: single-username, password-only, combo (user:pass), email:pass, JSON, CSV.

2. Inspect your wordlist

• Open the wordlist in a text editor and check its structure:
  • Single items per line → single‑value list (usernames or passwords).
  • Delimiter like ":" or "," or ";" in each line → combo list (user:pass).
  • Lines starting with "{" or "[" → JSON.
  • Comma-separated values and consistent columns → CSV.

3. Convert the wordlist to the expected format

• If config expects combos (user:pass) but you have usernames only, convert or pair them with passwords (or use a passwords list with a different attack mode).
• Simple conversions:
  • Join two lists into combos: paste usernames and passwords into a script or use tools to produce all combos or one‑to‑one pairs.
  • Change delimiter if needed (e.g., replace "," with ":" using find/replace).
  • Convert JSON/CSV to plain combos by extracting the fields.
• Example (one‑to‑one pairing with a script in Python):

# pairs usernames and passwords line-by-line into user:pass combos
with open('users.txt') as u, open('pass.txt') as p, open('combos.txt','w') as o:
    for user, pwd in zip(u, p):
        o.write(f"user.strip():pwd.strip()\n")

4. Adjust the config if safe and appropriate

• If you control the config and understand it, change the expected input type to match your wordlist (only if you’re sure the module supports alternate formats). Do this in the Config Editor where the input type is defined.

5. Use a different attack/wordlist option

• If converting is impractical, select a different combo/wordlist option in OpenBullet that matches your wordlist type or use a config designed for that format.

6. Validate before running

• Load the converted wordlist in OpenBullet and check the preview/validation. Ensure there are no blank lines or malformed entries.
• Run a small test (few lines) before running a full attack.

How Configs Read Data

In the OpenBullet Config editor (specifically inside the Start Block or Key Block), the developer assigns variables to slices of the wordlist line.

For example, if a config is designed for a MailPass wordlist, the developer might write code like: If the format is email:pass:birthdate , you have 3 parts

DATA "email" "password"

This tells the runner: "When you read a line, split it at the colon (:). Call the first part 'email' and the second part 'password'."

If you feed this config a UserPass wordlist (e.g., johndoe:123456), the config might fail if it tries to validate the email format, or it might simply reject the wordlist type entirely if the author has implemented strict type checking (which is what causes this specific error message).

---

Using Notepad++ or PowerShell:

• Replace colon with comma? No — OpenBullet expects colon : as delimiter by default unless config says otherwise.
• Change separator: Use Find & Replace (Ctrl+H), replace , with :.

🔧 Solution 4 – Use OpenBullet’s Wordlist Converter

• Go to Tools → Wordlist → Converter.
• Set source format (your current format).
• Set target format (what config expects).
• Convert and save.

---

2. Reverse-Engineering OpenBullet Configs – Security Analysis (Blog-style paper)

Several cybersecurity researchers have written analytical breakdowns of OpenBullet’s internal logic. Example:
“Anatomy of an OpenBullet Config: Parsing, Proxies, and Payloads” by Jason Parker (2022)

Key insights:

• The error is a safeguard against misrouted data (e.g., sending a password list where a username is expected)
• Workarounds include editing the config’s JSON to change InputType from "combo" to "list" or using OpenBullet’s built-in converter tool

---