Openbullet This Config Does Not Support The Provided ((full)) Link
"I am using a config that worked yesterday, but now it gives this error"
Are you using or OpenBullet 2 , and what is the format of the wordlist you are trying to use? Usage - OpenBullet
You are using a "Proxy-less" config (often meant for high-speed API abuse from your own IP), but you have enabled a proxy in your runner. Result: "This config does not support the provided proxy." 4. Outdated Config or Website Changes
If the error specifies a wordlist or input mismatch, you need to alter the configuration's metadata so it accepts your data format. Navigate to the tab. Open the specific configuration causing the error. Click on the Settings sub-tab within the config builder. Locate the Supported Wordlist Types section.
OpenBullet relies on the Environment.ini file to define available wordlist types. If a config references a wordlist type that isn't properly defined—or missing entirely—the error will occur. You can find this file in OpenBullet2.Native > UserData > Environment.ini . Openbullet This Config Does Not Support The Provided
For example, if a Config expects a wordlist type with Separator=: and Slices=FIRST,SECOND , then your wordlist lines need to look like value1:value2 . You can use text editors or scripting tools (like Python or PowerShell) to reformat your wordlist.
section of the config to see if there are mandatory fields you left blank. 3. OpenBullet Version Incompatibility If you are trying to run an OpenBullet 1 (.loli) OpenBullet 2 (.opk)
The error "This Config Does Not Support The Provided Wordlist Type" is fundamentally a . By understanding wordlist types, properly configuring your Environment.ini file, and following the solutions outlined above, you can resolve this error quickly and efficiently.
When you try to run a job, OpenBullet compares the type you selected from the drop‑down menu (for example, "Mail:Pass") against the allowed types defined inside the config. If you selected "Mail:Pass" but the config only allows "Credentials", the error message will appear. "I am using a config that worked yesterday,
Always use the debugger with sample data before running large jobs. This catches compatibility issues early and saves time.
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.
: Click Save in the config editor and retry your job. Advanced Troubleshooting
The config expects a specific format (like email:pass ) but your list is formatted differently (like user:pass or just emails ). Outdated Config or Website Changes If the error
Think of the config as the “how” of the automation process. It dictates the entire workflow: it uses placeholders for usernames and passwords, defines how to handle proxies and custom request headers, and sets logic to determine if a login was successful, usually by checking for specific keywords in the server’s response. Without the correct config, the software has no idea how to navigate the target website effectively.
[WORDLIST TYPE] Name=MacPass Regex=^([0-9A-Fa-f]2[:-])5([0-9A-Fa-f]2)$ Separator=: Slices=MAC_ADDRESS,OTHER_DATA Verify=True
Ensure the dropdown menu for matches the exact requirement you found in Step 1.
This error is particularly common when using . While OB2 can import and convert many OB1 configs, there are limitations. If the conversion fails or the config contains unsupported features, you might see this error.
