SRSP en Windows: conectado pero sin tráfico
Esta guía reúne errores reales de SRSP: la app muestra conexión, pero el navegador sale directo, DNS/API no responde, el tráfico cae al cambiar de modo o el servidor muestra errores upstream.
Respuesta rápida
Si curl -x http://127.0.0.1:1080 funciona, srsp-client está vivo. El fallo suele estar en el proxy de Windows: se aplicó PAC/AutoConfigURL en vez de ProxyEnable=1 y ProxyServer=127.0.0.1:1080.
Empieza por el mapa de síntomas
Esta guía reúne errores reales de SRSP: la app muestra conexión, pero el navegador sale directo, DNS/API no responde, el tráfico cae al cambiar de modo o el servidor muestra errores upstream.
No diagnostiques solo por el estado conectado. Valida proxy local, proxy de Windows, Wintun/routes y egreso del servidor.
| Síntoma | Causa probable | Cómo comprobarlo | Cómo corregirlo |
|---|---|---|---|
| La app dice conectado, pero el navegador usa la IP local | El proxy del sistema no se aplicó o quedó un PAC | Revisa ProxyEnable, ProxyServer, ProxyOverride y AutoConfigURL | Reconecta con la versión reciente para restaurar 127.0.0.1:1080 |
| curl -x 127.0.0.1:1080 funciona, el navegador no | El navegador sigue el estado antiguo de Windows proxy/PAC | Compara curl con -x y sin -x | Quita AutoConfigURL o actualiza GhostMesh |
| El puerto 1080 está cerrado | srsp-client no está ejecutándose o fallaron las credenciales | Comprueba el proceso srsp-client y el puerto local | Reconecta, inicia sesión de nuevo o envía el log |
| El log muestra Network is unreachable para IPv6 | El servidor no tiene ruta IPv6 de salida | Comprueba rutas del servidor y el host destino | Usa egreso IPv4 o una versión que filtre IPv6 no disponible |
Comprobaciones del proxy de Windows
Si curl -x http://127.0.0.1:1080 funciona, srsp-client está vivo. El fallo suele estar en el proxy de Windows: se aplicó PAC/AutoConfigURL en vez de ProxyEnable=1 y ProxyServer=127.0.0.1:1080.
Working state: ProxyEnable=1, ProxyServer=127.0.0.1:1080, ProxyOverride=<local>, AutoConfigURL empty.
Lista de comprobación
- ✓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 y archivos incluidos
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.
Lista de comprobación
- ✓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 | Acción |
|---|---|---|
| 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 |
Qué enviar a soporte
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.
Lista de comprobación
- ✓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 qué el proxy manual arregla y reconnect vuelve a romper?
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.