SoulFire LogoSoulFire

Proxies

Fix proxy import, validation, and connection problems.

Test without proxies first

If SoulFire works without proxies, test the proxy pool first.

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

Make sure that the proxy format is correct

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

Fix the format before you continue.

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. First, test account authentication without proxies.

Start with:

  1. no proxies for account authentication
  2. Make sure that account import works.
  3. Make sure that one bot can join.
  4. Turn proxying on again.

This separates authentication problems from gameplay connection problems.

Replace proxies that often time out

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 use a smaller sample before you continue.

Match bot count to pool size

Too many bots on each proxy can cause unclear errors.

Review these values:

  • 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

A large proxy list can contain many unstable proxies. Proxy quality matters more than list size.

How is this page?

Last updated on

On this page