This is the most frequent trigger for "Openbullet this config does not support the provided". The config author explicitly coded the config to split the input by a specific delimiter (usually :). If the delimiter is missing or different, the config cannot extract the Username and Password variables.
OpenBullet is an automation tool, but it isn't telepathic. It relies on specific instructions within a configuration file (the .loli or .ob file) to tell it how to treat the data you feed it.
When you see the "does not support" error, it means there is a mismatch between the format of the data in your Wordlist and the format the Config expects.
Think of it like trying to put a square peg in a round hole. The config is asking for a specific shape (data format), and you are providing a different one.
If you have a format mismatch, you need to transform your data. Use a text editor like Notepad++ or a tool like OpenBullet’s built-in "Toolbox" .
OpenBullet configurations are programmed to process specific data formats (e.g., Credentials, Email:Pass, User:Pass, or custom types). If you attempt to run a config designed for "Email:Pass" with a wordlist you have imported as "User:Pass," the software blocks the job to prevent logic errors. How to Fix the Error
To resolve this, you must align the wordlist type with what the configuration expects: Check Config Requirements:
Open the OpenBullet Configuration Manager and select the config you want to use. Go to the Other Options tab (or Data section in OB2).
Look for the Allowed Wordlist Types list. This shows exactly which formats the developer has authorized for this config. Re-Import the Wordlist:
If your wordlist is technically correct (e.g., it contains emails) but was imported with the wrong label, delete it from the Wordlists tab.
Click Add to re-import it, and this time, select the Type that matches the config’s allowed list. Modify the Config (Advanced):
If you are the developer or want to override the restriction, you can manually add your desired Wordlist Type to the config’s allowed list in the Other Options settings.
Alternatively, you can edit your Environment.ini file to define new, more general regex types (like Credentials) that accept multiple formats. Version Compatibility Note
If you are using OpenBullet 2, ensure you are importing modern .opk files or correctly formatted .loli files. Some older legacy configs from OpenBullet 1 may require you to re-select or rescan them in the manager to update their environmental settings.
Do you need help defining a custom Wordlist Type in your Environment.ini to bypass this error permanently?
This config does not support the provided Wordlist Type (MAC) Openbullet This Config Does Not Support The Provided
This config does not support the provided Wordlist Type (MAC) - Questions - OpenBullet. discourse.openbullet.dev
cant uploade configs · Issue #260 · openbullet/OpenBullet2
The screen flickered once—then held steady.
OpenBullet. The name alone carried weight in certain circles—those corners of the internet where data was currency and anonymity was armor. For Leo, it was just another Tuesday night. A cracked energy drink next to his keyboard, the hum of his desktop fans like white noise, and a fresh list of combos he’d scraped from a half-accessible forum dump.
He dragged the .txt file into the loader. Two hundred thousand lines. Email:password. Most of them garbage, but that was the game—you sifted through the sand until your fingers caught on something sharp.
Leo hit Start.
The bots whirred to life in the log window—green text crawling upward like vines on a trellis. Validating... Retrying... Captcha detected... Skipping. The usual rhythm. He leaned back, waiting for those rare, beautiful words: Hit.
But after thirty seconds, a different message appeared.
OpenBullet: This config does not support the provided input type.
He blinked. Read it again.
“What the hell?”
He’d used this config a hundred times. A custom LoliShift config for a mid-tier retail site—nothing fancy, but reliable. He checked the settings. Input type: Combo (email:pass). His file was exactly that. No weird delimiters. No empty lines. UTF-8 encoding.
He tried a smaller test list—ten combos he’d manually verified earlier that week.
Same error.
“Config’s broken,” he muttered, already reaching for his backup folder. This is the most frequent trigger for "Openbullet
But the backup did the same thing. Then the third one. Every config he tried—old staples, fresh downloads, even a legacy Puppeteer config he’d written himself—threw the same red flag.
Does not support the provided input type.
Leo sat forward, the caffeine suddenly not strong enough. He opened the config file in a text editor.
It looked fine. XML structure intact. The input options clearly listed "email:pass" as accepted.
He closed the editor. Opened the OpenBullet console directly—bypassed the GUI. Same error.
That’s when he noticed something strange.
His system clock read 03:14 AM. He didn’t remember it being that late. Or that early. He’d started at 11:00 PM. Four hours? No—he’d only been running scans for twenty minutes.
He glanced at his phone.
03:14 AM.
He refreshed the browser tab he’d left open—the forum where he’d scraped the combos. The page loaded, but the date on the posts had changed. Last week’s threads now showed timestamps from next month.
Leo’s hands hovered over the keyboard. He wasn’t a superstitious person. If you made a living sneaking through other people’s broken security, you learned to trust only logic, logs, and layers.
But logic had nothing to say about the config error.
He opened a command prompt and pinged the retail site’s login endpoint—the one his config had hammered ten thousand times before without issue.
Request timeout.
He tried a different site. Same timeout. OpenBullet: This config does not support the provided
Every target his configs had ever touched was now unreachable.
Not blocked. Not rate-limited. Just... gone. Like the door had never existed.
His machine’s fans kicked up. The log window on OpenBullet, still frozen on the error message, suddenly scrolled.
Attempting fallback... Fallback failed. This config does not support the provided reality frame.
Leo stared at those last two words.
Reality frame.
That wasn’t in any config he’d ever seen.
His mouse cursor moved on its own—just a pixel, just once. Then stopped.
The energy drink can was empty. He didn’t remember finishing it.
Leo shut the laptop lid.
The error message burned behind his eyes. And somewhere, in the quiet between 03:14 and whenever morning decided to arrive, he realized the truth.
The config hadn’t stopped working.
He—the input he provided—was what no longer fit.
The combos hadn’t changed. The targets hadn’t moved.
The error wasn’t a bug.
It was a door closing. And Leo wasn’t sure which side he’d been left on.