Troubleshooting

Change one thing at a time while troubleshooting. If you change proxies, account type, bot amount, protocol version, and automation settings all at once, you usually lose the real cause.

Use this section when something that should work does not. Start with the symptom that is closest to what you see on screen or in the logs.

Before you change anything

Collect the basics first:

the exact SoulFire version
whether you are using GUI, CLI, or a dedicated server
whether the problem is local or remote
the exact error text, not just a paraphrase
the smallest setup that still reproduces the issue
whether the problem disappears when you remove proxies or automation

That saves time both for you and for anyone else trying to reproduce the problem later.

Pick the closest symptom

Cannot Connect Or Times Out

Use this when the GUI, CLI, or bots cannot stay connected.

Accounts And Authentication

Use this when account import, Microsoft auth, or login-related setup fails.

Proxies

Use this when proxy imports, checks, or connect attempts fail.

Scripts And Automation

Use this when scripts or native automation behave incorrectly.

Dedicated Server And Docker

Use this when the remote server, Docker stack, Cloudflared, or Traefik setup is the failing layer.

Troubleshoot the narrowest layer first

In practice, SoulFire problems usually break down into layers:

the client cannot reach the SoulFire server
the SoulFire server is reachable, but the bots cannot join or stay connected to the target server
the bots can join, but accounts, proxies, scripts, or automation change the behavior

If you can make the problem disappear by turning off one layer, you have found the right page to start from.