Proxies

The first rule of proxy troubleshooting

If SoulFire works without proxies and fails with proxies, assume the proxy pool is guilty until proven otherwise.

Do not keep changing unrelated settings before you test that simple split.

Check the proxy format first

Compare your input against Proxy Formats.

Common mistakes:

• using https:// proxy URLs even though SoulFire expects HTTP, SOCKS4, SOCKS5, or matching URI forms
• mixing several proxy types in a file without using a format that supports that
• importing username/password proxies with the wrong field order

If the format is wrong, every later test is wasted.

Test a tiny sample

Do not start with a huge purchased list.

Start with:

• one to three proxies
• one bot
• a known-good target server

If that fails, the pool is not good enough for production use yet.

Separate gameplay proxies from account-auth proxies

SoulFire can route account authentication through proxies, but that should not be your first test.

Start with:

1. no proxies for account authentication
2. confirm account import works
3. confirm one bot can join normally
4. only then turn proxying back on

This keeps auth failures and gameplay-connect failures from hiding inside the same test.

Treat timeout-heavy proxies as bad proxies

If you see repeated proxy connect timeouts, especially on SOCKS pools, do not assume SoulFire is at fault first.

Usually that means at least one of these:

• the proxy is dead
• the proxy is overloaded
• the proxy provider is rate-limiting you
• the target server is not reachable through that proxy

Replace the proxy or shrink the sample before doing anything more complex.

Match bot count to pool size

If you ask too many bots to share too few proxies, failures become noisy and misleading.

Check:

• how many proxies you actually imported
• the configured bots-per-proxy limit
• whether shuffling is enabled

Then test at a lower bot count.

Validate the simplest path first

A good isolation sequence is:

1. no proxies
2. one known-good proxy
3. a tiny proxy sample
4. normal bot count

If the problem starts at step 2, the proxy path is already broken.

What to capture before you report it

• proxy type
• whether authentication is required
• whether the same test works without proxies
• whether account auth was also routed through proxies
• exact timeout or proxy exception text

Related pages

• Import Proxies
• Proxy Formats
• Cannot Connect Or Times Out
• Accounts And Authentication