Repository navigation
Multik Sila 1.0.25
What's new
- One odd server no longer stops the VPN from starting. Some free server lists
contain servers written for other apps, for example withfp=unsafein the link.
The app refused to connect at all with an error like
unknown uTLS fingerprint: unsafe. Such settings are now converted to ones the
core understands. If the core still rejects a server, the app skips that one
server, says so in the log and connects without it. - Auto mode finds a working free server much faster. It used to check servers one
by one and wait up to 15 seconds for each dead one. Now it checks the current server
and the next best ones at the same time. On a list of 141 free servers, the time from
tapping the shield to "traffic gets through" went from 32 seconds to 4. - Android: "Full path through the proxy" latency now works without a connection.
Before, without the VPN on, this mode quietly measured only the time to connect to
the server, so the numbers changed once you connected. Now it sends a real request
through every server, with or without the VPN.
Which file do I need?
| Device | File |
|---|---|
| Windows 10 / 11 | MultikSila-1.0.25-setup.exe |
| Android — almost any phone | MultikSila-1.0.25-android-arm64-v8a.apk |
| Android — old 32-bit phones | MultikSila-1.0.25-android-armeabi-v7a.apk |
| Android emulator | MultikSila-1.0.25-android-x86_64.apk |
Already using Multik Sila on Windows? It offers this update on its own.
MultikSila-1.0.25-windows-x64.zip is what it downloads for that — you don't need it.
On Android with 1.0.13 or newer the app offers this update itself; the first time,
Android asks you to allow installing from Multik Sila. On 1.0.12 or older, install this
file by hand once.
Technical details
- Links are usually written for Xray, which accepts uTLS fingerprints and VLESS flows
that sing-box 1.14 does not:unsafe(plain Go TLS),hellochrome_131and other
hello…names,chromefp,flow=xtls-rprx-vision-udp443. sing-box failed the whole
config withinitialize outbound[N]: …. They are now mapped when the subscription is
parsed (unsafe= TLS without uTLS; REALITY servers, which go through Xray, get
chrome, since Xray does not allowunsafewith REALITY). - Safety net for anything else: the outbound index from the core's error identifies the
server, which is dropped before an immediate restart (Android: the VPN service's error
event; Windows: the core's stderr). No extra check before every connect. - All five igareck lists pass
sing-box checkthrough the app's own parser; without the
fix three of them could not start. Checked on an emulator with a list containing
fp=unsafeplus a server with a made-up flow: the bad server was skipped and the
tunnel came up. - Auto mode: the Clash API
delaycheck runs in batches of 12 (up to 36 servers); the
current server wins if it answers within 3 s. Lists over 60 servers are measured with
2 handshakes per server instead of 5. - Android full-path latency without a connection: an in-app probe sing-box without a
tunnel (plus its own Xray instance for Xray servers), measured through its Clash API,
like the probe processes on Windows. If it cannot start, the app falls back to the
handshake time.