SoulFire LogoSoulFire

Proxy Formats

See supported proxy types, import formats, and proxy settings.

Supported proxy types

TypeAuthenticationNotes
HTTPNone, username, or username and passwordGood for standard proxy lists
SOCKS4None or username onlySOCKS4 does not support passwords
SOCKS5None, username, or username and passwordCommon choice for bot traffic
URIDepends on the schemeLets one file mix HTTP, SOCKS4, and SOCKS5 entries

SoulFire does not accept https:// proxy URLs. Use HTTP, SOCKS4, SOCKS5, or URI entries with these schemes.

Import formats

HTTP

ip:port <- no authentication
ip:port:username <- username
ip:port:username:password <- username & password
username:password@ip:port <- username & password (alternative)

Example:

192.168.0.1:8080
192.168.0.2:1080:root
192.168.0.3:1090:root:PassW0rd
root:PassW0rd@192.168.0.4:1090

SOCKS4

ip:port <- no authentication
ip:port:username <- username
username@ip:port <- username (alternative)
(socks4 doesn't support passwords)

Example:

192.168.0.1:8080
192.168.0.2:1080:root
root@192.168.0.3:1080

SOCKS5

ip:port <- no authentication
ip:port:username <- username
ip:port:username:password <- username & password
username:password@ip:port <- username & password (alternative)

Example:

192.168.0.1:8080
192.168.0.2:1080:root
192.168.0.3:1090:root:PassW0rd
root:PassW0rd@192.168.0.4:1090

URI

Use URI format when you want one file to mix proxy types.

socks5://ip:port <- socks5
socks5://username@ip:port <- socks5 & username
socks5://username:password@ip:port <- socks5 & username & password

socks4://ip:port <- socks4
socks4://username@ip:port <- socks4 & username
(socks4 doesn't support passwords)

http://ip:port <- http
http://username@ip:port <- http & username
http://username:password@ip:port <- http & username & password

Example:

http://192.168.0.1:8080
socks4://root@192.168.0.1:8080
socks5://root:PassW0rd@192.168.0.1:8080

Bot distribution across proxies

SoulFire defaults to -1 bots per proxy, which means unlimited. It still tries to distribute bots evenly across the available proxies.

If you set a hard limit such as 10, SoulFire only allows 10 bots per proxy. Bots that cannot lease proxy capacity remain queued until capacity becomes available.

Proxy settings reference

SettingDefaultWhat it does
Bots per proxy-1Limits how many bots can use one proxy
Shuffle proxiesfalseRandomizes proxy order before bots join
Proxy check addressmc.hypixel.netThe server address used for proxy validation
Proxy check concurrency10How many proxy checks run at once
Proxy check timeout30How many seconds SoulFire waits before a check fails

How is this page?

Last updated on

On this page