If the correct type is already allowed but it still fails, check your environment settings:
This is the most frequent cause of the error. Every config file contains a property called AllowedWordlist1 and AllowedWordlist2 within its settings. These properties explicitly define the wordlist types the config is allowed to work with.
What (e.g., email:pass, user:pass, tokens) are you trying to load? Which version of OpenBullet are you currently running?
Look for . This tells you exactly what format the config expects (e.g., Credentials ). Verify Your Wordlist Settings : Go to the Wordlists tab. Check the entry for the wordlist you are trying to use. Openbullet This Config Does Not Support The Provided
Check the config's notes or metadata to see what format it accepts. Format your text file to match that exact structure.
. When you create or load a config, you define what kind of input it expects. This is usually defined in the "Stacker" or "Settings" tab under the Input Data section. Common formats include: Credentials (User:Pass or Email:Pass): The most standard format. Used for single strings like API keys or tokens. Used for bulk URLs or specific IDs.
The error is one of the most common roadblocks encountered by automated testing and cybersecurity professionals using OpenBullet and OpenBullet 2. This error triggers because OpenBullet acts as a strict parsing validation engine. If a configuration file is built to parse one specific format (such as an email/password combination) and you provide data structured differently (such as a list of numerical proxy pins or alphanumeric URLs), the engine deliberately stops execution to prevent corrupted text loops. If the correct type is already allowed but
If your file looks like myemail@gmail.com:mypassword , you will get the error.
He —the input he provided—was what no longer fit.
Test-run sandbox
It sounds like you're running into a common technical error in OpenBullet
Sometimes the error is not about the format, but about data integrity. If your combolist contains blank lines, lines with only a colon ( : ), or lines with special non-printable characters (like UTF-8 BOM), the config parser fails. It reads a line, finds no data to split, and replies with "no support."
If you attempt to use a list of SOCKS5 proxies on a config where the author strictly checked the box for "HTTP Only," the runner will immediately halt with this error message. How to Fix the Error: Step-by-Step What (e
If the config requires custom variables (e.g., [ ] ), ensure they are defined in your wordlist or in the configuration settings. Step 5: Debug the Config
[ Your Combo List ] ---> Must Match ---> [ Config Allowed Type ] (e.g., user@email.com:pass) (e.g., Email:Pass)