Openbullet This Config Does Not Support The Provided Wordlist Type _top_

Dynamic Digest: "openbullet this config does not support the provided wordlist type"

Summary

• Error: "openbullet this config does not support the provided wordlist type" occurs when OpenBullet (or a similar tool) attempts to use a wordlist whose format or type is incompatible with the active config’s expected input format.
• Impact: brute-force/proxy workflows halt or skip entries; results incomplete; wasted time and resources.

Probable causes

1. Wordlist format mismatch
   • Config expects one entry per line but the wordlist uses delimited pairs (e.g., user:pass) or JSON.
2. Wordlist type mismatch
   • Config expects usernames-only, passwords-only, combo (user:pass), or specific encoding (Base64) and the supplied list differs.
3. Field mapping missing
   • Config’s parser/runner not configured to map wordlist fields to the required request parameters.
4. Character encoding or BOM
   • UTF-8 with BOM or different encoding prevents correct parsing.
5. Line-ending or whitespace issues
   • CRLF vs LF or trailing whitespace breaks detection of fields.
6. Compressed or binary input
   • Wordlist is zipped, gzipped, or otherwise compressed and not auto-extracted.
7. Corrupted or truncated file
   • Partial file or unexpected binary data.
8. Tool/plugin version incompatibility
   • Config built for another OpenBullet version or fork that uses different wordlist handling.

Quick diagnostic checklist (run in order)

1. Confirm expected wordlist type
   • Open the config’s input/wordlist settings; note whether it expects "combos (user:pass)", "single column", "JSON", or "CSV".
2. Inspect first 20 lines of the wordlist
   • Verify formatting, separators, and presence/absence of headers.
3. Check encoding and BOM
   • Ensure UTF-8 without BOM (or the encoding the config expects).
4. Test with a minimal sample
   • Create a 5–10 line sample file matching the expected format and load it.
5. Verify field mapping in config
   • Ensure config maps the correct wordlist fields to request parameters (username/password/form fields).
6. Try alternate line endings
   • Convert LF <-> CRLF and retest.
7. Confirm file is uncompressed
   • Unzip or gunzip if needed.
8. Review config version compatibility
   • If config downloaded from elsewhere, check which OpenBullet version or fork it targets.

Fixes and actionable steps

• If config expects combos (user:pass) but you have single-column:
  1. Convert single-column to combos by pairing or using a fixed password:
     • Example script (Linux/macOS): awk 'print $0":password"' wordlist.txt > combos.txt
• If config expects single column but you have combos:
  1. Extract one side: awk -F: 'print $1' combos.txt > users.txt
• If config expects CSV/JSON:
  1. Convert your data to the expected format (use a script or spreadsheet export).
• If encoding/BOM is the issue:
  1. Remove BOM and ensure UTF-8: iconv -f UTF-8 -t UTF-8 -c infile > outfile; or use a text editor "Save as UTF-8 (no BOM)".
• If line endings:
  1. dos2unix infile
• If compressed:
  1. Decompress before importing.
• If field mapping missing:
  1. In the config editor, map wordlist fields to the appropriate variables/inputs; consult config comments or author notes.
• If using an incompatible config version:
  1. Use the OpenBullet version indicated by the config or adapt the config to your runner’s schema.

Quick example conversions

• Combos to users:

  awk -F: 'print $1' combos.txt > users.txt
  

• Users to combos with fixed password:

  awk 'print $0":MyP@ssw0rd"' users.txt > combos.txt
  

Verification

• Load the small sample that matches expected format; run 1–2 test requests; confirm the runner accepts the file and processes entries.

Prevention tips

• Keep a small, validated sample for each config type.
• Label wordlists with format in the filename (e.g., combos_userpass.txt, users_only.txt, json_list.json).
• Maintain consistent encoding (UTF-8 no BOM).
• Store metadata (expected format, OpenBullet version) alongside downloaded configs.

If you want, I can:

• Convert a provided sample wordlist into the correct type (paste 10–20 lines), or
• Inspect a specific config snippet to point out the expected wordlist format.

This error is a common "gatekeeper" in OpenBullet that occurs when the Wordlist Type (e.g., Email:Pass) does not match the Config's Requirement (e.g., Credentials). 🛠️ Why This Error Happens

OpenBullet configs are coded to parse specific formats. If a config is designed to use Credentials (usually User:Pass) but you upload a wordlist set to Emails (Email:Pass), the software blocks the runner to prevent a "parsing error" during the check. 💡 How to Fix It (The Quick Way) Go to the Runner tab. Look at your Wordlist selection. Change the Type dropdown to match what the config expects.

Common swaps: Change "Emails" to "Credentials" or "Default." Re-start the Runner. ⚙️ How to Fix It (The Permanent Way)

If you are the config creator or want to modify it so it always accepts your list type: Go to the Config Manager tab. Select your config and click Edit. Navigate to the Settings tab within the config editor. Go to General. Locate the Allowed Wordlist Types list.

Add the type you are trying to use (e.g., Email:Pass or Credentials). Save the config. 🔍 Understanding Wordlist Types Credentials: Generally used for User:Pass. Emails: Specifically for Example@mail.com:Pass. Numeric: Used for Phone:Pin or ID:Code. URLs: Used for scraping or crawling tasks.

📌 Pro Tip: If you aren't sure what the config needs, check the Stacker or LoliScript tab. Look at how the variables are defined (e.g., vs ).

Common Causes

1. Config expects email:pass but wordlist has only emails
   Example: You load a combolist into a config designed for username enumeration. Dynamic Digest: "openbullet this config does not support

2. Config expects single lines but you provide combos
   Some configs check login forms with one field only (e.g., username). Using user:pass will break it.

3. Config requires proxies, but you load a wordlist in the proxy field
   Easy to accidentally swap inputs in the OpenBullet UI.

4. Corrupt or mislabeled config
   Some older .loli configs have incorrect metadata.

1. The Root Cause: A Mismatch of Logic

To understand the fix, you must first understand how OpenBullet (OB) processes data.

When a Config developer writes a configuration file (.loli or .opk), they write specific code telling OpenBullet how to process an account. This code says something like:

• "Take the Username from the wordlist."
• "Combine it with the Password."
• "Send it to the website."

However, not all wordlists are created equal. Some contain just emails, some contain email:password combos, and others contain complex strings like user:pass:proxy.

The error occurs simply because the data columns inside your Wordlist do not match the specific columns the Config was programmed to expect. Error: "openbullet this config does not support the

If the Config is programmed to look for a "Password" field, but you load a Wordlist type that only contains "Username," the Config "does not support" that data structure.

Fix 6: Write a Simple Python Script to Transform Your Wordlist

When manual conversion fails, script it. This example converts any format to EMAIL:PASS:

import sys
input_file = "your_wordlist.txt"
output_file = "converted.txt"
with open(input_file, 'r') as infile, open(output_file, 'w') as outfile:
for line in infile:
parts = line.strip().split(':')
if len(parts) == 2:
# Assume first part could be email or username
email = parts[0] if '@' in parts[0] else parts[0] + '@domain.com'
outfile.write(f"email:parts[1]\n")

Save, run, then load the new file in OpenBullet.

6. Final Checklist Before Rerunning

• [ ] I have confirmed the config’s required wordlist type.
• [ ] I have opened my wordlist to see its actual format.
• [ ] I have converted my wordlist to match the config exactly.
• [ ] I have reloaded the wordlist in OpenBullet after conversion.
• [ ] The error no longer appears when starting the attack.

3. Change Wordlist Type in OpenBullet (If Config Allows Multiple Types)

• Some configs support both combos and wordlists.
  In OpenBullet 1, click on the config → “Change Wordlist Type” → select correct one.
  ⚠️ This only works if the config was built with multiple types enabled.

🔧 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.

Fix 2: Convert Your Wordlist to the Correct Type (Manual Method)

Once you know the required format, convert your existing wordlist. Probable causes