Backlinko readers get
access for 14 days. 55+ tools.
Backlinko readers get
access for 14 days. 55+ tools.
You will see a list that looks like this: AllowedWordlistTypes: ["EmailPass"] .
Authors: Kurt Thomas et al. (IEEE S&P 2019)
This error triggers when the selected in your Runner does not match the Allowed Wordlist Types defined inside the Config's metadata. For example:
Many users leave their wordlist type as "Default" when importing, while the config strictly requires a specific type like "URLs" or "CreditCard." You will see a list that looks like
This config does not support the provided Wordlist Type (MAC)
Below is a blog-style guide to understanding and fixing this mismatch.
Method 1: Change the Wordlist Type in OpenBullet (Easiest Fix) For example: Many users leave their wordlist type
OpenBullet is a powerful HTTP/HTTPS brute-forcing and web testing tool. It relies on two critical components:
The most important things to remember are:
This error typically appears when you try to start a job in the tab. It signals a mismatch between the data format required by the Config (the automation script) and the format of the Wordlist (the input data) you are trying to feed it. It signals a mismatch between the data format
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]
If you feed this config a 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).
The error "OpenBullet this config does not support the provided wordlist type" is frustrating but almost always fixable. It’s not a bug — it’s a safeguard to prevent OpenBullet from feeding garbage data into a config expecting a clean structure.
For example, if a config is designed for a wordlist, the developer might write code like: