SRSP Windowsis: ühendatud, kuid liiklust pole
See juhend koondab päris SRSP juhtumid: rakendus näitab ühendust, kuid brauser läheb otse, DNS/API ei vasta, liiklus kaob režiimi vahetamisel või server logib upstream vigu.
Kiire vastus
Kui curl -x http://127.0.0.1:1080 töötab, on srsp-client elus. Viga on tavaliselt Windowsi proxy olekus: PAC/AutoConfigURL rakendus, mitte ProxyEnable=1 ja ProxyServer=127.0.0.1:1080.
Alusta sümptomite kaardist
See juhend koondab päris SRSP juhtumid: rakendus näitab ühendust, kuid brauser läheb otse, DNS/API ei vasta, liiklus kaob režiimi vahetamisel või server logib upstream vigu.
Ära hinda ainult rohelise ühenduse oleku järgi. Kohalik proxy, Windowsi süsteemi proxy, Wintun/routes ja serveri egress peavad kõik korras olema.
| Sümptom | Tõenäoline põhjus | Kuidas kontrollida | Kuidas parandada |
|---|---|---|---|
| Rakendus näitab ühendust, kuid brauser kasutab kohalikku IP-d | Süsteemi proxy ei rakendunud või PAC jäi aktiivseks | Kontrolli ProxyEnable, ProxyServer, ProxyOverride ja AutoConfigURL väärtusi | Ühenda uuesti uue versiooniga, mis taastab 127.0.0.1:1080 |
| curl -x 127.0.0.1:1080 töötab, brauser mitte | Brauser kasutab vana Windows proxy/PAC olekut | Võrdle curl testi -x valikuga ja ilma | Eemalda AutoConfigURL või uuenda GhostMesh |
| Port 1080 on suletud | srsp-client ei tööta või volitused ebaõnnestusid | Kontrolli srsp-client protsessi ja kohalikku porti | Ühenda uuesti, logi sisse või saada logi |
| Logis on IPv6 Network is unreachable | Serveril puudub IPv6 väljundmarsruut | Kontrolli serveri marsruute ja sihthosti | Kasuta IPv4 väljundit või versiooni, mis filtreerib kättesaamatu IPv6 |
Windows proxy kontrollid
Kui curl -x http://127.0.0.1:1080 töötab, on srsp-client elus. Viga on tavaliselt Windowsi proxy olekus: PAC/AutoConfigURL rakendus, mitte ProxyEnable=1 ja ProxyServer=127.0.0.1:1080.
Working state: ProxyEnable=1, ProxyServer=127.0.0.1:1080, ProxyOverride=<local>, AutoConfigURL empty.
Kontrollnimekiri
- ✓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 ja kaasatud failid
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.
Kontrollnimekiri
- ✓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.
| Logi | Tähendus | Tegevus |
|---|---|---|
| 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 |
Mida toele saata
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.
Kontrollnimekiri
- ✓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
KKK
Miks käsitsi proxy aitab, kuid reconnect rikub uuesti?
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.