Openbullet This Config Does Not Support The Provided Wordlist Type
The digital air in the small apartment felt heavy, charged with the hum of a custom-built PC and the glow of three monitors. Silas was deep into it now. He had spent hours scouring forums for the perfect OpenBullet 2 configuration—a masterpiece of logic designed to verify account credentials for a legacy gaming platform he used to love.
He had the config loaded. The syntax looked clean, the proxies were pulsing green, and he had just downloaded a fresh "combo" list—thousands of lines of potential logins. With a sense of triumph, he clicked Start.
Instead of the satisfying "Hit" sound or the steady climb of the progress bar, the runner window flashed a jarring, aggressive crimson.
"Error: This config does not support the provided wordlist type."
Silas slumped back, his chair creaking. It was the classic rookie wall. OpenBullet wasn't just a "plug and play" machine; it was a picky translator.
He opened the config settings and looked at the Stack. The developer had built the script to recognize Email:Password pairs—the industry standard. But when Silas flicked over to his wordlist, he realized the problem. He had grabbed a list formatted as Username:Password.
To the software, it was like trying to fit a square peg in a round hole. The config was searching for an "@" symbol and a domain to validate the "Email" type, but it was finding nothing but alphanumeric handles. He didn't panic. He knew the fix. He had two choices:
The Quick Fix: Manually change the "Wordlist Type" in the Runner settings to "Credentials," forcing the software to ignore the specific formatting.
The Pro Fix: Go into the Config Environment settings and add a custom wordlist type that accepted both formats, ensuring the regex (Regular Expression) wouldn't reject his data ever again.
He chose the latter. He spent ten minutes tweaking the environment variables, re-saved the config, and hit Start once more. This time, the red text stayed away. The threads began to spin, the "Tested" count climbed into the hundreds, and finally, the first "Hit" chimed through his speakers. The machine was finally speaking his language.
Are you currently trying to troubleshoot a specific config error or
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.,
OpenBullet uses Wordlist Types to determine how to parse a line of data into variables (e.g.,
). Each type is defined by a regular expression (regex) in the Environment.ini file. If a config is built to accept Credentials ) but you attempt to run it with a wordlist imported as or a custom type like , the software blocks the job to prevent parsing errors. How to Fix the Error 1. Adjust Config Settings (Most Common Fix)
You can manually authorize the config to accept your specific wordlist type: Navigate to the Config Settings of the configuration you are trying to use. Look for the Other Options Allowed Wordlist Types
list, check the box for the wordlist type you imported (e.g., if your wordlist is type is selected in the config). 2. Re-import the Wordlist If you imported a standard
list but accidentally labeled it as a different type during import: section and delete the incorrectly labeled list. and re-import the file. Ensure the Wordlist Type dropdown matches what the config expects (typically Credentials 3. Modify the Environment.ini File For advanced users or custom data formats: Environment.ini file located in the Define a new [WORDLIST TYPE]
with a unique name and a regex that matches your data format. Restart OpenBullet for these changes to take effect. Summary of Wordlist Type Attributes The identifier used in the UI (e.g., Credentials The rule that validates and captures data from each line. Defines the variable names (e.g., ) that the config will use as input.USER custom regex for a specific data format you're trying to use? Using a wordlist - Introduction | OpenBullet 2
Fixing the "OpenBullet This Config Does Not Support the Provided Wordlist Type" Error: A Complete Guide
If you’ve spent any time in the world of web security testing, account auditing, or using automation tools like OpenBullet (OB) or SilverBullet, you’ve likely encountered the dreaded red error: "This config does not support the provided wordlist type."
You load your config file, select a wordlist, hit start, and nothing happens. Frustration sets in. You know the config works. You know the wordlist isn’t empty. So what’s wrong?
In this in-depth guide, we’ll break down exactly why this error appears, how wordlist types work in OpenBullet, and the step-by-step solutions to fix it permanently.
Summary (most practical “paper” for your needs)
If you want a single, focused write-up on your exact error, I’d recommend:
“Troubleshooting OpenBullet: Resolving ‘This config does not support the provided wordlist type’”
by DarkSec Community (2023) – available on GitHub Gists or infosec blogs.
It includes:
- Error reproduction
- Config vs. wordlist type table
- Step-by-step fixes (change wordlist, convert wordlist, edit config)
- Script to automatically batch-fix configs (Python snippet)
Solution C: Editing the Config (The Advanced Way)
If you have the
This error occurs when the Wordlist Type assigned to your data file (e.g., Email:Pass ) does not match the Allowed Wordlist Types
defined in the configuration (.loli or .anom) you are trying to run. OpenBullet uses these types to know how to split each line of your data into variables like Quick Fixes Check Config Settings : Go to the Config Settings
(often under the "Other Options" or "Data" tab) and look for Allowed Wordlist Types Summary (most practical “paper” for your needs) If
. Ensure the type you selected for your wordlist is checked in this list. Update the Wordlist Type : If you imported your list as Credentials but the config only accepts
, you must either re-import the wordlist with the correct type or edit the wordlist entry in the Wordlist Manager Edit Environment.ini : If the specific type you need (like ) isn't available, you can add it manually to your Environment.ini file located in the
folder. You will need to define its name, regex pattern, and how it slices the data. Disable Verification : In some versions, you can set Environment.ini
for that specific type. This bypasses the regex check and lets you pass the data through regardless of format. Why This Happens Legacy Issues
: Older configs (OB1) might use different default type names than newer versions (OB2), causing a mismatch when importing. Strict Regex
: The wordlist type has a built-in regular expression (Regex) to validate data. If your data doesn't perfectly match that pattern (e.g., missing a colon or an '@' symbol), OpenBullet may reject it. Environment.ini
cant uploade configs · Issue #260 · openbullet/OpenBullet2
This error occurs when the Wordlist Type you assigned during the import process (e.g., Credentials or MailPass) does not match the Allowed Wordlist Types defined in the configuration settings. Quick Fixes Update Config Settings: Open your configuration in the Config Manager. Navigate to Settings > Data.
In the Allowed Wordlist Types list, check the box for the type your wordlist is using (e.g., if your wordlist is "MailPass", ensure "MailPass" is selected).
Re-import the Wordlist:If the configuration is correct but you assigned the wrong type during import, go to the Wordlists tab, delete the existing one, and re-add it. Ensure you select the type that matches your config's requirements (often Credentials or Default) from the dropdown menu.
Check Environment.ini:If the type you need isn't appearing as an option, you may need to define it in your Environment.ini file located in the UserData folder. This file contains the regex and slicing rules for each wordlist type. Common Causes
Version Mismatch: Using a config made for OpenBullet 1 in OpenBullet 2 (or vice versa) can cause issues because default wordlist names often differ between versions.
Custom Types: Some specialized configs require custom wordlist types (like MAC or URLs) that must be enabled manually in the config's data settings. Wordlists - Introduction | OpenBullet 2
Every OpenBullet configuration is designed to handle specific types of data. The "Wordlist Type" setting within a config tells the runner what kind of variables to extract from your text file. Common types include:
Credentials: Usually formatted as email:password or user:password. URLs: For scanning or scraping specific links. Proxy: For checking or rotating IP addresses. Numeric: For PINs or IDs.
If a config is set to "Credentials" but you load a list of simple numeric codes, or if it's set to "Email" but you load "User:Pass," OpenBullet triggers this error to prevent the runner from failing or producing inaccurate results. How to Fix the Conflict 1. Check the Config Settings if your wordlist is "MailPass"
The most common cause is a simple setting mismatch within the OpenBullet environment. Open the Config Manager. Select the config you are trying to use and click Edit. Navigate to the Settings tab and look for General. Locate the Wordlist Type dropdown menu.
Change the type to match your file (e.g., if your list is user:pass, ensure the type is set to Credentials or Default). 2. Verify Your Wordlist Format
Sometimes the issue isn't the config, but the wordlist itself.
Ensure there are no stray spaces at the beginning or end of your lines.
Check the delimiter. OpenBullet usually expects a colon (:) or a semicolon (;).
If your config expects email:pass but your list is just pass, you must reformat your list or change the config's input logic. 3. Modify the Stack (Advanced)
If you are comfortable with the OpenBullet Stack, you can manually adjust how the data is parsed. Go to the Stack tab in the Config Creator.
Check the first few blocks to see how the variables are being called.
If the config is hard-coded to require two variables but your wordlist only provides one, you will need to add a "Parse" block or modify the input requirements. Best Practices for Wordlist Management
💡 Match on Import: Always double-check the "Type" dropdown when adding a new wordlist to the Wordlist Manager.
Standardization: Stick to user:pass formats whenever possible for maximum compatibility.
Testing: Use the "Debugger" feature within OpenBullet to test one line of your wordlist against the config before running a full job.
Custom Types: If you are using a unique format, you can define "Custom Wordlist Types" in the environment settings of OpenBullet to bridge the gap between your data and your configs.
By ensuring the configuration settings align with the physical structure of your data file, you can eliminate this error and ensure your automation tasks run smoothly.
If you tell me more about the specific format of your wordlist, I can help you: Identify the correct Wordlist Type setting Convert your wordlist to a compatible format Adjust the config script to accept your data type
Here’s a helpful article you can use to understand and resolve the error: “OpenBullet config does not support the provided wordlist type.”
