Why shadowsocks-rust
shadowsocks-rust is the actively maintained Rust implementation of the Shadowsocks protocol. It supports full SIP002 URIs and runs as a lightweight local SOCKS5/HTTP proxy daemon.
Step 1 — Get the binary
Direct download (no GitHub required)
Download shadowsocks-v1.24.0.x86_64-unknown-linux-musl.tar.xz from our mirror on the install page, or directly from github.com/shadowsocks/shadowsocks-rust/releases.
Extract and install:
tar -xf shadowsocks-v1.24.0.x86_64-unknown-linux-musl.tar.xz
sudo mv sslocal /usr/local/bin/
sudo chmod +x /usr/local/bin/sslocal
The musl build has no external library dependencies — it runs on any x86_64 Linux.
Step 2 — Get your Store4Gateway access key URL
- Log in to store4gateway.com/dashboard.
- Copy your
ss://access key URL.
Step 3 — Connect
Run sslocal with your access key URL directly:
sslocal --server-url "ss://YOUR_ACCESS_KEY_URL_HERE" \
--local-addr 127.0.0.1:1080 \
--protocol socks5
This starts a local SOCKS5 proxy on port 1080.
Route browser traffic:
Set your browser's proxy to SOCKS5 127.0.0.1:1080, or export for CLI tools:
export ALL_PROXY=socks5://127.0.0.1:1080
Run as a systemd service:
# /etc/systemd/system/sslocal.service
[Unit]
Description=Shadowsocks local client
After=network.target
[Service]
ExecStart=/usr/local/bin/sslocal \
--server-url "ss://YOUR_ACCESS_KEY_URL_HERE" \
--local-addr 127.0.0.1:1080 \
--protocol socks5
Restart=on-failure
[Install]
WantedBy=multi-user.target
sudo systemctl enable --now sslocal
Step 4 — Verify
curl --proxy socks5://127.0.0.1:1080 https://store4gateway.com/check
You should see connected in the response. Or open store4gateway.com/check in a proxied browser.
Troubleshooting
"Connection refused" on sslocal startup
- Check your access key URL is complete and unmodified. The URL contains the server address, port, encryption method, and password encoded in base64.
Permission denied on /usr/local/bin
- Use
sudofor themvandchmodcommands, or install to~/.local/binand add that to$PATH.
Still stuck? Contact support.