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
To understand the mismatch, you must understand the three most common wordlist types used in OpenBullet:
This public link is valid for 7 days and shares a thread, including any personal information you added. This link or copies made by others cannot be deleted. If you share with third parties, their policies apply. Can’t copy the link right now. Try again later. You can manually authorize the config to accept
Wordlist types, on the other hand, refer to the format and structure of the text files used to provide input data for the attack. OpenBullet supports various wordlist types, including:
Before diving into the error, it's essential to understand how OpenBullet configurations and wordlist types work. OpenBullet configurations, also known as "configs," are files that define the settings and parameters for a specific attack or test. These configs are used to instruct OpenBullet on how to interact with a target system, what type of attack to perform, and what data to use. If you share with third parties, their policies apply
In the , change the Wordlist Type dropdown to match your list.
If you change the type to Default , OpenBullet puts the entire line into the variable. If the config blocks are still looking for , the process will fail. You may need to update the variable names in the to match your data. Summary Checklist Wordlist types, on the other hand, refer to
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:
The "This config does not support the provided wordlist type" error in OpenBullet is common and fixable. By understanding wordlist types, verifying your config's allowed types, and properly importing your wordlist, you can resolve the issue quickly.
If you are trying to run an OpenBullet 1 (Loli format) config in OpenBullet 2 and encountering this error, the best solution is to look for an updated version of the config or convert it using available tools. The development team acknowledges this issue and recommends using up-to-date configs designed for OpenBullet 2.