SRSP di Windows: tersambung tetapi trafik tidak berjalan
Panduan ini merangkum kasus SRSP nyata: aplikasi menampilkan connected, tetapi browser tetap langsung, DNS/API tidak merespons, trafik hilang setelah mode diganti, atau server mencatat error upstream.
Jawaban cepat
Jika curl -x http://127.0.0.1:1080 berhasil, srsp-client berjalan. Masalah biasanya ada di status proxy Windows: PAC/AutoConfigURL aktif, bukan ProxyEnable=1 dan ProxyServer=127.0.0.1:1080.
Mulai dari peta gejala
Panduan ini merangkum kasus SRSP nyata: aplikasi menampilkan connected, tetapi browser tetap langsung, DNS/API tidak merespons, trafik hilang setelah mode diganti, atau server mencatat error upstream.
Jangan hanya melihat status connected. Pastikan local proxy, Windows system proxy, Wintun/routes, dan egress server semuanya sehat.
| Gejala | Kemungkinan penyebab | Cara memeriksa | Cara memperbaiki |
|---|---|---|---|
| Aplikasi tertulis connected, tetapi browser memakai IP lokal | Proxy sistem tidak diterapkan atau PAC masih aktif | Periksa ProxyEnable, ProxyServer, ProxyOverride, dan AutoConfigURL | Reconnect dengan versi terbaru untuk memulihkan 127.0.0.1:1080 |
| curl -x 127.0.0.1:1080 berhasil, browser tidak | Browser mengikuti status proxy/PAC Windows yang lama | Bandingkan curl dengan -x dan tanpa -x | Hapus AutoConfigURL atau perbarui GhostMesh |
| Port 1080 tertutup | srsp-client tidak berjalan atau credentials gagal | Periksa proses srsp-client dan port lokal | Reconnect, login ulang, atau kirim log |
| Log menampilkan Network is unreachable untuk IPv6 | Server tidak punya route IPv6 keluar | Periksa route server dan host tujuan | Gunakan egress IPv4 atau versi yang memfilter IPv6 yang tidak tersedia |
Pemeriksaan proxy Windows
Jika curl -x http://127.0.0.1:1080 berhasil, srsp-client berjalan. Masalah biasanya ada di status proxy Windows: PAC/AutoConfigURL aktif, bukan ProxyEnable=1 dan ProxyServer=127.0.0.1:1080.
Working state: ProxyEnable=1, ProxyServer=127.0.0.1:1080, ProxyOverride=<local>, AutoConfigURL empty.
Checklist
- ✓Test-NetConnection 127.0.0.1 -Port 1080
- ✓curl.exe -x http://127.0.0.1:1080 https://api.ipify.org
- ✓curl.exe https://api.ipify.org
- ✓Check ProxyEnable, ProxyServer, ProxyOverride, AutoConfigURL after reconnect
Installer dan aset bawaan
Users should not install .NET, Rust, srsp-client, or Wintun manually. The Windows installer must include them.
A partial install can show successful login and connected state while no traffic flows.
Checklist
- ✓GhostMesh.exe exists in the install directory
- ✓srsp-client.exe exists next to GhostMesh.exe
- ✓wintun.dll exists next to GhostMesh.exe
- ✓Install version 1.0.323 or later
- ✓Allow administrator elevation when Windows asks
Firewall, Wintun, routes
Windows Defender Firewall can block a new app if the first prompt was denied. TUN mode also needs Wintun routes.
If Wintun appears as a Public unidentified network, stricter firewall rules can block traffic.
- Allow inbound and outbound rules for GhostMesh.exe and srsp-client.exe.
- Check that the GhostMesh/Wintun adapter appears in VPN or Smart routing mode.
- In TUN mode, check routes such as 0.0.0.0/1 and 128.0.0.0/1.
- Reconnect after installing the latest build.
DNS, API, server logs
Separate local proxy/DNS problems from server egress problems. Local failures often send no traffic to the SRSP server; egress failures appear in srsp-server logs.
tls handshake eof, Broken pipe, and connection reset are not always outages. Correlate them with the user's exact timestamp.
| Log | Arti | Tindakan |
|---|---|---|
| failed to lookup address information | DNS could not resolve the host | Check host name and server DNS |
| Network is unreachable for IPv6 | No IPv6 egress route | Use IPv4 egress or filter unavailable IPv6 |
| tls handshake eof | Client or scanner closed early | Usually informational |
| Broken pipe / connection reset | Remote side or client closed | Compare with exact user timestamp |
Yang dikirim ke support
A useful report shows which layer failed: local proxy, Windows proxy registry, Wintun route, firewall, DNS, or server egress.
Do not send passwords, tokens, private account pages, or credential files.
Checklist
- ✓Windows version and GhostMesh version
- ✓Selected server and mode
- ✓Forced proxy IP test and direct IP test
- ✓ProxyEnable, ProxyServer, ProxyOverride, AutoConfigURL values
- ✓Whether srsp-client.exe is running and port 1080 is open
- ✓Exact timestamp of the failed test
FAQ
Mengapa proxy manual berhasil, lalu rusak lagi setelah reconnect?
Older builds could re-apply PAC/AutoConfigURL with ProxyEnable=0. The fixed build restores manual proxy 127.0.0.1:1080 after switching.
Does every Network is unreachable log mean SRSP is broken?
No. It is often one target route, especially IPv6 on a server without IPv6 egress. Confirm forced proxy and normal IPv4 tests first.