Openbullet This Config Does Not Support The Provided May 2026

This is the most frequent culprit.

Every OpenBullet config is programmed to accept a specific "Input Type." When a developer makes a config, they usually choose one of three standard types:

The Problem: If you load a User:Pass wordlist, but the Config is set to expect an Email:Pass format, OpenBullet will reject the input because it doesn't know how to handle the data structure (or the config has validation logic checking for @ symbols that aren't there).

The Fix:

OpenBullet primarily supports two data structures in a wordlist:

The Error in Action:

The Fix: Check the config's requirements.

If you spend time working with OpenBullet (OB) or OpenBullet 2, you know the feeling: you’ve found a promising config, loaded your wordlist, set your proxies, and hit "Start." But instead of the satisfying "HIT" notifications, you are immediately greeted by a wall of red text in the logger:

"This config does not support the provided input format."

It is one of the most common errors for beginners and intermediate users alike. It usually stops your run dead in the tracks before it even begins.

In this post, we are going to break down exactly what this error means, why it happens, and how to fix it so you can get your checks running smoothly.

The "This config does not support the provided" error is essentially OpenBullet's way of telling you it's confused. It’s a data formatting issue, not a software bug.

By double-checking your Wordlist type against the Config's requirements and ensuring your slicers are set up correctly, you can clear this error in seconds and get back to what matters: checking your accounts.

Have a specific OpenBullet error you'd like us to cover? Drop a comment below!

The error message "This Config Does Not Support The Provided Wordlist Type" in OpenBullet occurs when the format of your imported wordlist (e.g., Email:Pass or User:Pass) does not match the data types allowed in the configuration's settings. Core Cause

Every OpenBullet config is designed to handle a specific format of data. If you try to run a configuration set for Credentials (standard User:Pass) with a wordlist that the system identifies as a different type (like Emails or URLs), the job will fail to start. How to Fix the Error 1. Update Configuration Settings

You need to tell the configuration that it is allowed to accept your wordlist type.

Open the Config: Go to the Configs tab and select the config giving you trouble.

Navigate to Settings: Go to Config Settings > General (or Data in some versions).

Change Wordlist Type: Look for a section labeled Allowed Wordlist Types.

Add Your Type: If your wordlist is Email:Pass, ensure that Credentials or MailPass is moved to the "Allowed" side.

Save: Don't forget to save the config before trying to run the job again. 2. Check the Environment.ini File

If the wordlist type you need isn't appearing as an option, you may need to define it in your environment settings.

Navigate to your OpenBullet folder and find UserData\Environment.ini (OB2) or Settings\Environment.ini (OB1).

Ensure it contains the correct regex for your type. For standard credentials, it should look like:

[WORDLIST TYPE] Name=Credentials Regex=^.*:.*$ Separator=: Slices=USERNAME,PASSWORD Use code with caution. Copied to clipboard

Restart OpenBullet after making changes to this file to ensure they take effect. 3. Verify Wordlist Formatting

Ensure your actual text file matches the expected separator (usually a colon :). If your wordlist uses semicolons ; but the config expects colons, OpenBullet may fail to recognize the type correctly. Quick Troubleshooting Tips

Manual Override: In some cases, you can simply rename your wordlist type to "Credentials" when importing it to force compatibility, provided the internal script logic matches.

Stacker View: Ensure you are saving changes from the Stacker view to confirm they are written to the config file.

OB1 vs. OB2: If you are using an old .loli config in OpenBullet 2, it may not automatically detect the correct wordlist types due to different default settings.

Are you working with a custom wordlist format, or are you using a standard User:Pass list?

This error usually pops up in OpenBullet when the configuration file (.loli or .anom) you are using is missing the necessary settings for the type of data you are trying to process (e.g., trying to run a "Proxyless" config with proxies, or using a "Login" config for "Sign up" data). 💡 Common Causes

Data Type Mismatch: The config is built for Email:Pass but you loaded User:Pass.

Proxy Settings: The config is hardcoded for a specific proxy type (or none at all).

Missing Inputs: The config requires a specific custom input that isn't provided.

Version Issues: Using an OpenBullet 2 config in SilverBullet or vice versa. 🛠️ How to Fix It

Check the Config Header: Open the config in the "Stacker" or "Editor" tab. Check the "Data Type" setting and ensure your wordlist matches it.

Toggle Proxy Mode: If the error mentions proxies, try switching the "Proxies" button to "On" or "Off" depending on the config's requirements.

Review "Custom Inputs": Some configs require you to enter a specific API key or URL in the "Input" field before starting.

Check "Accept Service": Ensure the wordlist you are using is accepted by the config's specific target site. Openbullet This Config Does Not Support The Provided

🚀 Pro Tip: Always check the Log tab at the bottom of the Runner; it will usually tell you exactly which requirement is missing.

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.

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.

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. This is the most frequent culprit

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.

OpenBullet: The Config Conundrum - Understanding and Resolving the "This Config Does Not Support The Provided" Error

OpenBullet, a popular open-source tool, has gained significant traction among cybersecurity professionals and enthusiasts alike for its versatility in managing and stress-testing web applications. However, users often encounter a frustrating error message: "This config does not support the provided." In this article, we'll delve into the world of OpenBullet configurations, explore the possible causes of this error, and provide actionable steps to resolve it.

Understanding OpenBullet Configurations

Before we dive into the error, let's briefly discuss OpenBullet configurations. A configuration, or "config" for short, is a set of predefined settings that determine how OpenBullet interacts with a target web application. These settings include parameters such as request headers, cookies, and payloads. Configurations are essential in OpenBullet, as they enable users to tailor their testing approach to specific applications and use cases.

The "This Config Does Not Support The Provided" Error

The "This config does not support the provided" error typically occurs when OpenBullet is unable to reconcile the configuration file with the provided data. This error can manifest in various scenarios:

Troubleshooting Steps

To resolve the "This config does not support the provided" error, follow these step-by-step troubleshooting guidelines:

Best Practices for OpenBullet Configurations

To minimize the likelihood of encountering the "This config does not support the provided" error, follow these best practices:

By understanding the causes of the "This config does not support the provided" error and following the troubleshooting steps outlined in this article, you'll be better equipped to resolve issues and optimize your OpenBullet experience. Additionally, adhering to best practices for OpenBullet configurations will help you get the most out of this powerful tool while minimizing errors and downtime.

"This Config Does Not Support The Provided" in OpenBullet typically occurs when the configuration (.loli or .anom file) is being used with a it wasn't designed for Common Causes and Fixes Data Type Mismatch : The config might be built for Credentials

(Email:Password or User:Pass), but you are trying to run it with a list of : Check the tab in OpenBullet. Ensure the Input Data Type matches your wordlist. If the config requires Email:Pass and you provide , it may fail if it specifically looks for an "@" symbol. Missing or Incorrect Captures

: The config is looking for a specific data field (like a "Numeric" PIN or a "SSN") that isn't present in your text file.

: Verify the format required by the config author. Usually, this is listed in the config's notes or the block of the LoliScript. Config Version Incompatibility : You are trying to run an OpenBullet 1 OpenBullet 2 (Native) without importing it correctly, or vice-versa.

: Use the "Import" function in OB2 to convert legacy configs, or ensure you are using the specific version of the environment (OpenBullet, SilverBullet, or Anomaly) the config was built for. Proxies vs. Proxyless

: If the config is set to "Proxyless" but you have loaded a proxy list into the runner, it may trigger a support error in certain modded versions of the software.

: Disable proxies in the Runner settings if the config is meant to run hits directly. How to Check the Required Format Config Manager Right-click the config and select Look at the Settings > General Accepted Data Types

field. It will show you exactly what format the config expects (e.g., Are you trying to run a specific data format like a combo list, or is this happening with

The error message "This config does not support the provided wordlist type" occurs because the data format of your wordlist (e.g., user:pass) doesn't match the format allowed in your OpenBullet config settings. Quick Fix Steps

Open the Config Manager: Go to the Configs tab and select the specific config you are trying to use.

Navigate to Settings: Click on Stacker (the config editor) and find the Settings or Other Options tab. Update Allowed Types: Locate the Wordlist Type or Data section. Find the list of "Allowed Wordlist Types".

Ensure the type that matches your wordlist (usually Credentials for user:pass) is moved to the Allowed side or checked.

Save and Reload: Click Save in the config editor and retry your job. Advanced Troubleshooting

If the correct type is already allowed but it still fails, check your environment settings:

Verify Environment.ini: Ensure your Environment.ini file (found in the UserData or root folder) actually defines the wordlist type you are trying to use.

Regex Match: OpenBullet uses a Regex pattern in Environment.ini to validate your data. If your wordlist line doesn't match that pattern (e.g., using a semicolon ; instead of a colon :), it will reject the file.

Matching Slices: Ensure the "Slices" defined in the environment match the variables used in your config (e.g., USER and PASS).

Did you download this config from a forum, or are you creating it yourself from scratch?

Mismatch in Config SettingsEach config has an "Allowed Wordlist Types" setting. If your wordlist is categorized as Credentials but the config only allows MailPass, the runner will block the job.

Fix: Go to the Config Manager, edit the config, navigate to Other Options (or Data tab in OB2), and ensure the wordlist type you are using is moved to the Allowed side.

Environment.ini MisconfigurationThe Environment.ini file defines the rules (regex) for what constitutes a valid wordlist type. If your wordlist doesn't match the regex defined for its type, OpenBullet may fail to process it.

Fix: Check your Environment.ini (located in the UserData folder). Ensure the regex for types like Credentials or UserPass matches your data (e.g., ^.:.$ for a standard colon separator).

Incorrect Data Selection in the RunnerWhen starting a new job, the Runner requires you to select both a config and a wordlist. If the wordlist was imported with the wrong type assigned to it, the conflict triggers this error.

Fix: Re-import your wordlist and explicitly select the type that matches your config's requirements (e.g., Credentials, URLs, or Emails). The Problem: If you load a User:Pass wordlist,

Version Incompatibility (OB1 vs. OB2)Configs for OpenBullet 1 (.loli) and OpenBullet 2 (.opk) handle data types differently. While OB2 can often import older configs, manual adjustments to the data settings are frequently needed after the import. Quick Checklist for Fixing Open Config Manager: Check the Data or Other Options tab.

Verify Allowed Types: Ensure your specific wordlist type is in the "Allowed" list.

Save & Rescan: Always save the config and click "Rescan" in the Runner after making changes to ensure they take effect.

Are you using OpenBullet 1 or OpenBullet 2, and what is the specific Wordlist Type you are trying to run?

Here’s a short, clear write-up explaining the error “This config does not support the provided” in OpenBullet, including causes and fixes.

A niche but real cause: older versions of OpenBullet (pre-2020) have a bug where long lines or Unicode characters cause false positives for "does not support input." Update to OpenBullet 2 or the latest Ruri fork to resolve underlying parser bugs.

Bad wordlist:

username:password123

Fix: Use a text editor to remove everything after the colon, including the colon itself. Or, in OpenBullet, use the Wordlist > Transform feature: Extract only the first column (split by : and take index 0). Result:

username

When you see "This config does not support the provided," follow this forensic checklist:

| Step | Action | What to look for | | :--- | :--- | :--- | | 1 | Examine the full error in the OpenBullet Logs tab. | The exact suffix (e.g., "data type", "key", "variable"). | | 2 | Inspect your wordlist (first 5 lines). | Are there colons? Are lines single words? Any empty lines? | | 3 | Check Config Settings (Edit Config > Settings > Data). | Look for "Input type" (Single/Combo) and "Separator". | | 4 | Run a single test in Debug mode. | Right-click combo > "Test" or use the "Debug" runner. The detailed error will appear. | | 5 | Test with a known good wordlist. | Use test@test.com:password for combo configs or testuser for single configs. If it works, your wordlist is the problem. |

The error message "This config does not support the provided..." is intimidating at first glance, but it is fundamentally a communication problem between your wordlist and your config file. By understanding the expected data type (Single vs. Combo), verifying the delimiter, and ensuring config integrity, you can resolve this error in under a minute.

OpenBullet is a tool of precision. Treat your configs and wordlists as a lock and key—they must be cut exactly for one another. Now that you understand the "why" behind the error, you can debug it with confidence and get back to your security testing or data processing tasks.

Happy testing, and always ensure you have explicit permission to test any target systems.

The solution generally involves aligning the "Allowed Wordlist Types" in your config settings with the actual type of data you are loading.

Adjust Config Settings: Navigate to the Configs tab, select your configuration, and open the Other Options (or Settings) section. Under the Data or Wordlist Type tab, ensure that the type matching your wordlist (e.g., Credentials, EmailPass, or UserPass) is moved to the Allowed side.

Verify Environment.ini: Ensure your Environment.ini file (found in the UserData folder) correctly defines the wordlist type. A standard Credentials entry should look like this: Name: Credentials Regex: ^.:.$ (matches the basic format) Separator: : (or whatever character separates your data)

Check Input Variables: If you are using OpenBullet 2, ensure you aren't manually prefixing variables with input. if they are not coming directly from the wordlist.

Re-save and Rescan: After making changes, save the configuration in the Stacker view and use the Rescan button in the Config Manager to ensure the updates are recognized. Community Perspectives on Fixes

“It's a problem with environment.ini... be sure that it contains [WORDLIST TYPE] Name=Credentials... When you make a config choose credentials in settings.” discourse.openbullet.dev · 3 years ago

“Make sure “Credentials” is clicked over to the Allowed side, save config from stacker view.” discourse.openbullet.dev · 3 years ago

Are you using OpenBullet 1 or OpenBullet 2, and what is the format of the wordlist you are trying to use? Usage - OpenBullet

) and the data types allowed within the configuration settings. Root Cause

Configurations in OpenBullet are built to accept specific data formats defined by regular expressions (Regex) in the Environment.ini

file. If a config is set only to accept the "Credentials" type and you upload an "Email" wordlist, the software blocks the job to prevent processing errors. How to Fix the Error 1. Adjust Config Settings (OpenBullet 2)

Most modern configs can be quickly updated through the user interface: Config Manager and select the problematic config. Navigate to the view, then find the Other Options Look for a section titled Wordlist Types Allowed Wordlist Types Ensure the type of your wordlist (e.g., Credentials ) is moved to the the config before trying to run the job again. Environment.ini Configuration

If the required wordlist type is missing entirely from your options, you must define it in your environment file: Locate the file at OB2\UserData\Environment.ini (for OpenBullet 2) or the root folder (for OB1).

Check that it includes a valid definition for the data you are using. A standard "Credentials" entry looks like this:

[WORDLIST TYPE] Name=Credentials Regex=^.*:.*$ Verify=True Separator=: Slices=USERNAME,PASSWORD Use code with caution. Copied to clipboard Ensure the matches the format of your text file (e.g., for colon-separated data). 3. Re-Select the Config in the Runner After making changes to a config's settings or the Environment.ini If you have a job already created in the , the changes may not apply immediately. Stop the current job, re-select the config

from the list, and then re-upload your wordlist to refresh the settings.

If you are importing configs from third parties, they may come with a custom Environment.ini

OpenBullet uses specific data formats (like Credentials, Emails, or Cards) to know how to parse your input file. If a config is built to use UserPass (username:password) but you try to run it with a MailPass (email:password) wordlist, it will trigger this error. How to Fix It Check the Config Requirements: In OpenBullet, go to the Configs tab.

Find your config, select it, and go to Other Options -> Data.

Look for Allowed Wordlist Types. 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.

Ensure the Type dropdown for that wordlist matches one of the "Allowed Wordlist Types" you found in the config. Adjust and Re-select:

If they don't match, you can either change the type of your Wordlist in the Wordlists tab or add the new type to the "Allowed Wordlist Types" in the config settings.

After making changes, you may need to re-select the config in the Runner to refresh the settings.

Are you using a custom wordlist format, or is this a standard User:Pass list?

This config does not support the provided Wordlist Type (MAC)

This config does not support the provided Wordlist Type (MAC) - Questions - OpenBullet. discourse.openbullet.dev

[REQUEST] Wordlist with Multiple Types · Issue #590 - GitHub