SRSP no Windows: conectado, mas sem tráfego
Este guia reúne erros reais de SRSP: a app mostra conexão, mas o navegador sai direto, DNS/API não responde, o tráfego cai ao trocar de modo ou o servidor mostra erros upstream.
Resposta rápida
Se curl -x http://127.0.0.1:1080 funciona, o srsp-client está ativo. O problema geralmente está no proxy do Windows: PAC/AutoConfigURL em vez de ProxyEnable=1 e ProxyServer=127.0.0.1:1080.
Comece pelo mapa de sintomas
Este guia reúne erros reais de SRSP: a app mostra conexão, mas o navegador sai direto, DNS/API não responde, o tráfego cai ao trocar de modo ou o servidor mostra erros upstream.
Não diagnostique apenas pelo estado conectado. Confirme local proxy, proxy do Windows, Wintun/routes e egress do servidor.
| Sintoma | Causa provável | Como verificar | Como corrigir |
|---|---|---|---|
| A app mostra conectado, mas o navegador usa o IP local | O proxy do sistema não foi aplicado ou ficou um PAC | Verifique ProxyEnable, ProxyServer, ProxyOverride e AutoConfigURL | Reconecte com a versão recente para restaurar 127.0.0.1:1080 |
| curl -x 127.0.0.1:1080 funciona, o navegador não | O navegador segue o estado antigo do proxy/PAC do Windows | Compare curl com -x e sem -x | Remova AutoConfigURL ou atualize o GhostMesh |
| A porta 1080 está fechada | srsp-client não está em execução ou credenciais falharam | Verifique o processo srsp-client e a porta local | Reconecte, entre novamente ou envie o log |
| O log mostra Network is unreachable para IPv6 | O servidor não tem rota IPv6 de saída | Verifique rotas do servidor e host de destino | Use saída IPv4 ou versão que filtre IPv6 indisponível |
Verificações do proxy do Windows
Se curl -x http://127.0.0.1:1080 funciona, o srsp-client está ativo. O problema geralmente está no proxy do Windows: PAC/AutoConfigURL em vez de ProxyEnable=1 e 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
Instalador e assets incluídos
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 | Significado | Ação |
|---|---|---|
| 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 |
O que enviar ao suporte
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
Por que proxy manual resolve e depois quebra no 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.