Openbullet This Config Does Not Support The Provided May 2026

OpenBullet 1.x (legacy) uses .loli configs. OpenBullet 2 uses .opk files. SilverBullet and other forks have different parsers. Trying to load a config designed for OB2 into OB1 (or vice versa) can sometimes manifest as an input support error before the config even runs.

If you cannot change the combolist, you can modify the config itself (only if you have the author’s permission or for personal use).

For OB1 (.loli configs):

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:

Let’s move from theory to practice. Follow these diagnostic steps in order.

For advanced users: Some configs are built to accept more than two variables. For example, a config for a banking site might expect three variables: USERNAME:PASSWORD:PIN. Or a config for a proxy tester might expect IP:PORT:USERNAME:PASSWORD.

If your wordlist only provides two variables, OpenBullet will throw the error because it cannot map the third required variable.

The Error in Action: The config's LoliScript contains:

SET USERNAME @var1
SET PASSWORD @var2
SET PIN @var3

Your wordlist contains: john_doe:123456. There is no PIN. The config fails at the SET PIN command.

The Fix:

At its core, OpenBullet is a tool that uses Configs (.loli or .opk files) to define a testing workflow. Each config expects a specific type of input data.

OpenBullet supports three primary data types for each line in your combolist (the list of credentials or data you are testing):

The error occurs when the data format in your combolist does not match what the config is programmed to parse. For example, you feed a config expecting User:Pass a combolist formatted as Email:Pass, or you feed it an Auto config a standard User:Pass file.

This error is user-side, not a bug in OpenBullet. Always read the config’s release notes or example wordlist. If the issue persists, the config may be intentionally locked to a specific wordlist structure (hardcoded).

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 Openbullet This Config Does Not Support The Provided

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)

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

cant uploade configs · Issue #260 · openbullet/OpenBullet2

Troubleshooting "This Config Does Not Support The Provided" in OpenBullet

If you are using OpenBullet for web testing or data parsing, encountering the error "This Config Does Not Support The Provided Data" is one of the most common roadblocks. This error essentially means there is a "handshake" failure between the data you are trying to process (your wordlist) and the logic written inside the configuration file (.anom or .loli).

In this guide, we will break down why this happens and how to fix it so you can get your runner back online. What Causes This Error?

OpenBullet is highly logical. Every configuration is designed to handle a specific type of input. When you see this error, the Runner is telling you: "You gave me X, but I was programmed to only handle Y." The three primary culprits are:

Data Type Mismatch: You are using a "Credentials" config but loading a "URL" list (or vice versa). OpenBullet 1

Missing Input Slicing: The config expects a specific format (like email:pass) but your list is formatted differently (like user:pass or just emails).

Config Logic Restrictions: The developer of the config added a check to ensure the input meets certain criteria (e.g., must contain an @ symbol) and your data failed that check. How to Fix It: Step-by-Step 1. Check the "Data Type" Setting OpenBullet configs have a "Data Type" requirement.

The Fix: Go to the Runner tab and look at the config you selected. Right-click it or check the settings to see what Data Type it requires (e.g., Default, Email, Credentials).

Now, look at your Wordlist. When you imported your wordlist, did you select the same type? If the config is set to Credentials and your wordlist was imported as Default, OpenBullet will throw this error. 2. Verify the Separator Most configs expect the standard colon separator (:).

The Fix: Open your wordlist file in Notepad++. Does it look like admin:password123? If it uses a semicolon ; or a comma ,, OpenBullet won't be able to split the data into the variables and .

You can change the separator in the Settings > General tab of OpenBullet, but it’s usually easier to just use a standard : format in your text file. 3. Inspect the Config "Input" Logic If you are comfortable with the Stacker or LoliScript tab: Open the config in the Config Manager. Go to the Settings sub-tab within the config.

Look for Input Settings. Some authors restrict the "Allowed Data Types." Ensure the box for the data type you are using is checked.

Check for any "Custom Inputs" or "Script" blocks at the very beginning of the config that might be filtering out your data based on length or character requirements. 4. Re-import the Wordlist Sometimes the simplest fix is the most effective. Remove the wordlist from the Wordlist Manager. Click Add to re-import it.

Carefully select the Type (usually Credentials for user:pass combos) and ensure the path is correct. Re-assign this wordlist to your Runner.

The "This Config Does Not Support The Provided" error isn't a bug in the software; it's a configuration mismatch. Always ensure that your Wordlist Type matches the Config Requirements, and that your data is cleanly formatted with the correct separator.

If you are using a leaked or shared config, the developer may have locked the input to a specific format (like Email only). In that case, you may need to use a "Mail Combo" instead of a "User Combo."

Troubleshooting "This Config Does Not Support The Provided" in OpenBullet

If you are using OpenBullet for web testing or data scraping, encountering the error "This Config Does Not Support The Provided Data Type" is a common roadblock. This error essentially means there is a mismatch between the information in your wordlist and the requirements of the configuration (.anom or .loli) you are running.

Here is a deep dive into why this happens and how to fix it. 1. Understanding the Root Cause

OpenBullet configs are scripted to handle specific data formats. When you load a wordlist, the software checks if the data structure matches the input variables defined in the config. The most common conflicts are:

Credentials vs. Tokens: The config expects a Credentials format (User/Pass), but you provided a list of Tokens or URLs.

Email vs. Username: The config is strictly set to Email mode, but your list contains simple usernames. The Problem: If you load a User:Pass wordlist,

Combo Format: Your wordlist uses a colon : as a separator, but the config is looking for a semicolon ; or a comma ,. 2. How to Fix the Error Check the Config Settings

Open the Config Manager and select the config giving you trouble. Go to the Settings tab within that config. Look for General or Input Settings.

Check the Accepted Wordlist Types. If it says Credentials and you are trying to use a Proxy list or a Custom list, the error will trigger. Verify Your Wordlist Type When you go to the Runner tab to start your job: Look at the Wordlist section.

Ensure the "Type" dropdown matches what the config requires.

If your wordlist is user:pass, ensure the type is set to Default or Credentials. Edit the Config’s Metadata

If you are certain your data is correct but the config is being picky, you can manually change the requirements: Open the config in the Stacker or a text editor.

In the config’s JSON/Loli metadata, find the line: "TargetWhitelist": [].

You can add your data type there (e.g., "Credentials", "Emails") or leave it empty to allow all types. 3. Quick Checklist for Success

Syntax: Does your list look like example@email.com:password123?

Encoding: Ensure your wordlist is saved in UTF-8 encoding to avoid hidden characters that break the parser.

Empty Lines: Sometimes a massive gap of empty lines at the bottom of a wordlist can cause OpenBullet to throw an input error.

The "This Config Does Not Support The Provided" error isn't a bug in the software; it's a safety gate to prevent you from wasting proxies and time by running the wrong data through a specific script. Always align your Wordlist Type in the Runner with the Accepted Type in the Config Settings.

Even if both the config and wordlist use a combo format, they might disagree on the separator (delimiter). The default delimiter in OpenBullet is a colon (:). However, some configs are hardcoded to expect a pipe (|), a semicolon (;), a tab (\t), or a space ( ).

The Error in Action: Your wordlist looks like this:

[email@example.com,password123]

But the config expects:

[email@example.com:password123]

Because the config's parser sees a comma instead of a colon, it cannot split the line into two variables. You will see: "This config does not support the provided key" or a similar generic refusal.

The Fix: