OpenBullet categorizes wordlists by their data structure. The most common types are:
| Wordlist Type | Structure | Example Line |
|---------------|-----------|---------------|
| EMAIL:PASS (combo) | email:password | john@example.com:SecureP@ss |
| USER:PASS | username:password | johndoe:SecureP@ss |
| EMAIL | Single email | john@example.com |
| USERNAME | Single username | johndoe |
| PASSWORD | Single password | SecureP@ss |
| PROXY | ip:port or ip:port:user:pass | 192.168.1.1:8080 |
| CUSTOM | Depends on the config | token123 or user|pass|extra |
The error appears when, for example:
Search for wordlists labeled with the exact type the config expects (e.g., “combolist email:pass”).
If you want, paste (anonymized) 3–5 sample lines from your wordlist and a short excerpt of the config’s wordlist/type setting and I’ll tell you exactly what to change.
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
This error occurs in OpenBullet (OB1 or OB2) when the wordlist you've selected does not match the data types authorized within the configuration's settings.
To fix this, you must ensure the configuration is set to "allow" the specific wordlist type (e.g., Credentials ) that you are trying to use. How to Fix the Error Check Your Config Settings Navigate to the Config Manager tab and select the config you want to use. Config Settings (or "Other Options" in OB1) and find the Wordlist Type
Verify that the "Allowed Wordlist Types" list includes the type of the wordlist you are trying to run. Verify Your Wordlist Type
tab and check what type is assigned to your imported file (e.g., If it is assigned a type like but your config only allows , OpenBullet will throw this exception. Update Environment.ini (Advanced)
Wordlist types and their validation rules (regex) are defined in the Environment.ini file located in the
Ensure the type names in this file match what is expected by the config. You must restart OpenBullet after editing this file for changes to take effect. Common Mismatches Credentials vs. EmailPass : A config may be hardcoded for syntax, but you are providing an Email:Pass Missing Types : If you imported a config from a different user, their Environment.ini might have custom wordlist types (like ) that your local installation doesn't recognize. Environment.ini to bypass this?
This config does not support the provided Wordlist Type (MAC)
In OpenBullet, every wordlist is assigned a specific type (e.g., Credentials, Emails, URLs) during import. Simultaneously, each configuration (config) specifies which wordlist types it is compatible with. If you attempt to run a Multi Run Job using a wordlist typed as MAC with a config that only allows Credentials, the software will block the job from starting to prevent processing errors. How to Resolve the Mismatch
You can fix this by updating the config settings or by ensuring your wordlist and environment settings match. 1. Update Allowed Wordlist Types in the Config
If you are sure your wordlist data is correct for the target site, you can tell the config to accept your wordlist's type:
Go to the Config Settings section of the specific config you are using. Navigate to the Data or Other Options tab. Locate the Allowed Wordlist Types list.
Add or check the box for the Wordlist Type that matches your imported wordlist (e.g., UserPass, EmailPass, or a custom type). 2. Re-import the Wordlist with a Compatible Type
If the config requires a specific type that your wordlist doesn't currently have: Delete the wordlist from your Wordlist Manager. Import it again.
During the import process, select the Wordlist Type that is already allowed by your config. 3. Modify the Environment.ini File
The Environment.ini file defines the standard wordlist types available in your OpenBullet installation.
Open the Environment.ini file located in the UserData folder. Ensure the type you need is defined under [WORDLIST TYPE].
If you share configs with others, make sure your Environment.ini matches theirs, as missing types can trigger this error.
Note: You must restart OpenBullet for changes in this file to take effect. Technical Background: Wordlist Type Syntax
Wordlist types do two things: verify the data format using Regex and split the data into Slices (variables like USER and PASS) for the config to use.
Regex: Validates that the input line matches the expected pattern (e.g., checking for an @ in an email). OpenBullet categorizes wordlists by their data structure
Slices: Maps parts of a line (separated by a character like :) to variables used in the script (e.g., input.USER).
Error in OpenBullet: "This config does not support the provided wordlist type" - A Comprehensive Guide
Are you encountering the frustrating error message "This config does not support the provided wordlist type" while using OpenBullet? You're not alone. Many users face this issue, which can be caused by a mismatch between the configuration file and the wordlist type. In this article, we'll delve into the possible causes, solutions, and provide a step-by-step guide to help you resolve the issue.
What is OpenBullet?
OpenBullet is a popular, open-source tool used for testing and analyzing the security of web applications. It allows users to perform various types of attacks, including brute-force attacks, using customizable configuration files and wordlists.
Understanding the Error
The error message "This config does not support the provided wordlist type" typically occurs when the configuration file (config) loaded in OpenBullet is not compatible with the type of wordlist you're trying to use. This can happen due to several reasons:
Solutions and Workarounds
To resolve the error, try the following solutions:
Step-by-Step Guide
To troubleshoot and resolve the issue, follow these steps:
Conclusion
The "This config does not support the provided wordlist type" error in OpenBullet can be frustrating, but it's usually caused by a simple mismatch between the configuration file and the wordlist type. By following the solutions and step-by-step guide outlined in this article, you should be able to resolve the issue and get back to testing and analyzing the security of web applications.
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
Troubleshooting "This Config Does Not Support the Provided Wordlist Type" in OpenBullet
If you are using OpenBullet for web testing or data parsing, encountering the error "This config does not support the provided wordlist type" is a common roadblock. This message is not a bug in the software; it is a built-in safety check to ensure that the data you are feeding into a configuration (the Wordlist) matches the format the configuration is designed to process.
Here is a comprehensive guide on why this happens and how to fix it. Understanding the Root Cause
Every OpenBullet configuration (Config) is designed to handle a specific data format defined by the Wordlist Type. The most common types are: Credentials: Usually User:Pass or Email:Pass. URLs: A list of website links. Numeric: A list of PINs or IDs. Default: A generic single-line string.
If a config is set to Email:Pass but you attempt to run it with a wordlist that contains only single usernames or URLs, OpenBullet triggers this error to prevent the runner from crashing or producing "false negatives." How to Fix the Error 1. Check the Config’s Required Type
First, you need to see what the developer of the config intended for it to use. Go to the Config Manager tab in OpenBullet. Select the config you are trying to use and click Edit. Search for wordlists labeled with the exact type
Look at the Settings or General tab within the config editor.
Find the field labeled Wordlist Type. Note what is selected (e.g., Credentials, Mail, or Custom). 2. Verify Your Wordlist Format
Open your .txt wordlist file. Does it match the requirement found in Step 1?
If the config requires Credentials, your list must have a separator (usually a colon :) like admin:password123.
If your list is just a list of emails like test@gmail.com but the config expects Email:Pass, the runner will reject it. 3. Change the Config Settings (The "Quick Fix")
If you are certain your wordlist is correct for the site you are testing, but the config is being picky, you can manually change the accepted type:
In the Config Editor, change the Wordlist Type dropdown to match your list.
If you want the config to accept anything, you can often set it to Default. Save the config and try adding it to the Runner again. 4. Check the "Stack" or "Blocks"
Sometimes, the error persists because the config uses specific variables like
If the Wordlist Type is Credentials, OpenBullet automatically splits the line at the colon and assigns the first part to
If you change the type to Default, OpenBullet puts the entire line into the variable. If the config blocks are still looking for
Match the Type: Ensure the Runner’s wordlist type matches the Config’s settings.
Clean Your Data: Remove empty lines or malformed strings from your text file.
Check Separators: Ensure you are using colons (:) or semicolons (;) as defined in the OpenBullet environment settings.
By aligning the data format of your wordlist with the expectations of the configuration, you can clear this error and get your runner back online. AI responses may include mistakes. Learn more
Every OpenBullet configuration (config) is designed to process specific data structures defined in its settings. If a config is set to Credentials (usually Email:Password or Username:Password), but you load a wordlist containing only URLs or single strings, the software blocks the process to prevent errors during the "parsing" stage. 2. Common Scenarios
Mismatched Syntax: You are using a wordlist formatted as User:Pass, but the config is set up for Email:Pass (or vice versa).
The "Default" Problem: Many users leave their wordlist type as "Default" when importing, while the config strictly requires a specific type like "URLs" or "CreditCard."
Custom Types: Some advanced configs use custom slices (e.g., Email:Pass:Proxy:UserAgent). If your wordlist is missing any of these parts, it will be rejected. 3. How to Fix It To resolve this, you generally have two options:
Adjust the Wordlist: Reformat your text file to match what the config expects. For most account checking, this means ensuring every line is String1:String2. Adjust the Config Settings: Go to the Config Manager and select the config. Navigate to Settings > General. Look for Accepted Wordlist Types.
Add the type that matches your list (e.g., if your list is User:Pass, make sure Credentials or Default is checked). Summary
This error is a built-in safety feature. It ensures that the "Slices" (the variables the config uses to log in) have the correct data to work with. To fix it, simply ensure the Wordlist Type selected during the job setup matches the Accepted Type in the config's internal settings.
The "This config does not support the provided Wordlist Type" error in OpenBullet occurs when you attempt to run a job using a wordlist that hasn't been enabled in the specific configuration's settings . OpenBullet uses these types (like Credentials, Emails, or UserPass) to determine how to parse each line of your data file into variables like input.USERNAME and input.PASSWORD .
Below is a blog-style guide to understanding and fixing this mismatch.
How to Fix: "This config does not support the provided Wordlist Type" 1. Update the Config Settings (The Quick Fix)
Most of the time, the configuration simply needs to be told that your wordlist type is acceptable.
Open the Config: Go to the Config Manager and select the config you want to use.
Navigate to Settings: Go to Config Settings > Other Options (or Data in OpenBullet 2) .
Enable the Type: Look for a section labeled Allowed Wordlist Types.
Select Your Type: Check the box for the wordlist type you are trying to use (e.g., if your wordlist is "MailPass," ensure "MailPass" or "Credentials" is selected) . Solutions and Workarounds To resolve the error, try
Save: Don't forget to save the config before restarting your job. 2. Re-Import Your Wordlist
If you accidentally imported your wordlist with the wrong type (e.g., imported a list of emails as Default instead of Credentials), the config will reject it even if the data looks correct. Go to the Wordlist Manager. Delete the current wordlist entry. Click Add and re-select your file .
In the Type dropdown, carefully select the format that matches your data (usually Credentials or UserPass) . 3. Modify the Environment.ini File (Advanced)
If you are using a unique data format that isn't listed, you can define it yourself in the core settings.
Locate the Environment.ini file in your OpenBullet root or UserData folder .
Under the [WORDLIST TYPE] section, you can add a new type with a custom Regex and Slices .
Example: Name=MyCustomList, Regex=^.*:.*$, Separator=:, Slices=USER,PASS . Restart OpenBullet for these changes to take effect . Why does this happen?
OpenBullet is designed to be modular. A config built to check Proxy Lists shouldn't accidentally be run with a list of User:Pass combos. By enforcing "Wordlist Types," the software ensures that the script has the exact variables it needs to function properly .
Do you need help defining a custom regex for a specific wordlist format in your Environment.ini?
[REQUEST] Wordlist with Multiple Types · Issue #590 - GitHub
This error occurs when the Wordlist Type assigned to your imported data file does not match the Allowed Wordlist Types specified within your OpenBullet configuration's settings. Core Causes Mismatched Attributes
: The config is hard-coded to only accept certain types (e.g., Credentials
), but you imported your wordlist as a different type (e.g., Missing Environment Definitions
: If the specific wordlist type name used in the config isn't defined in your Environment.ini file, OpenBullet cannot validate the data correctly. Resolution Steps 1. Adjust Config Settings (Most Common Fix)
You must explicitly tell the configuration which data types it is allowed to process. Config Manager and select the problematic config. Navigate to Config Settings Other Options depending on your version). Locate the Allowed Wordlist Types
Move the wordlist type you are using (e.g., "Credentials" or "EmailPass") from the "Available" side to the the configuration before starting the job. 2. Re-import the Wordlist
When importing a new list, ensure you select the correct category that matches what the config expects. section and click
dropdown, select the category that matches your config's requirement (standard options usually include Credentials 3. Update the Environment.ini
If the required wordlist type is missing entirely from your environment, you must add it manually to the OpenBullet Usage Manual configuration file. Environment.ini
Ensure it contains the definition for the type you need, such as:
[WORDLIST TYPE] Name=Credentials Regex=^.*:.*$ Verify=True Separator=: Slices=USERNAME,PASSWORD Use code with caution. Copied to clipboard Restart OpenBullet after saving changes for them to take effect. Technical Overview Table Wordlist Type Categorizes data lines (e.g., email:pass vs user:pass). Allowed Types
A security/logic gate in the config to prevent using wrong data formats.
Validates that each line in your file matches the expected format. , lines that don't match the regex are marked as INVALID. for a specific data 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.,
"This config does not support the provided wordlist type"