Accounts And Authentication
Diagnose Minecraft account import and authentication failures without mixing them up with remote-server access tokens.
Start by separating two different auth problems
SoulFire has two different authentication layers that people often mix together:
- logging a GUI or CLI client into a SoulFire server
- importing and refreshing Minecraft accounts for bots
If your GUI cannot log into a remote SoulFire server, start with Cannot Connect Or Times Out. This page is mainly about bot account import and Minecraft-side authentication.
Identify the account type first
Before changing anything, confirm which type you are trying to import:
- offline
- Microsoft Java
- Microsoft Bedrock
- cookie-based formats
Then compare your input against Account Formats. A lot of "auth is broken" reports turn out to be input-format mistakes.
Test without proxies first
If you have proxying enabled for account authentication, disable it and try the same account again.
That is the fastest way to answer an important question:
- does the account itself fail?
- or does the proxy path fail?
Only re-enable auth-through-proxy after the plain import path works.
Use the current install requirements
Do not troubleshoot authentication on an unsupported runtime and assume the auth provider is at fault.
Before going deeper:
- make sure you are on the current SoulFire release you intend to run
- use the Java/runtime version required by the current install docs
- retest with one account before importing a large batch
Re-import a minimal sample
If a large account set is failing, do not keep retrying the entire batch.
Instead:
- pick one known-good account
- import only that account
- test without proxies
- test with the exact target server you care about
If one account works and fifty do not, the batch shape is part of the problem.
If import succeeds but joining still fails
That is no longer just an account-import problem. Check:
- whether the target server needs additional in-game login or registration
- whether proxies are only failing after the join step
- whether the wrong protocol version is selected
At that point, continue with Cannot Connect Or Times Out or Proxies.
Access tokens for remote SoulFire servers
If the problem is your GUI or CLI login to a remote SoulFire server, generate a fresh API token:
generate-token apiThat token is for SoulFire server access. It is not the same thing as a Minecraft account credential.
What to capture before you report it
- account type
- whether proxies were used for account auth
- whether a single account reproduces the problem
- the exact error text
- whether import fails, refresh fails, or join fails after import
Never post raw passwords, cookies, JWTs, or browser-exported secrets in logs or issue reports.
Related pages
How is this page?
Last updated on