Windows पर SRSP: कनेक्शन है, लेकिन ट्रैफिक नहीं चल रहा
यह गाइड वास्तविक SRSP मामलों को जोड़ती है: app connected दिखाता है, लेकिन browser direct जाता है, DNS/API जवाब नहीं देता, mode बदलने पर traffic रुकता है या server upstream errors दिखाता है।
त्वरित उत्तर
अगर curl -x http://127.0.0.1:1080 चलता है, तो srsp-client चल रहा है। समस्या आम तौर पर Windows proxy state में होती है: ProxyEnable=1 और ProxyServer=127.0.0.1:1080 के बजाय PAC/AutoConfigURL लागू है।
लक्षणों से शुरू करें
यह गाइड वास्तविक SRSP मामलों को जोड़ती है: app connected दिखाता है, लेकिन browser direct जाता है, DNS/API जवाब नहीं देता, mode बदलने पर traffic रुकता है या server upstream errors दिखाता है।
केवल हरे connected status पर भरोसा न करें। local proxy, Windows system proxy, Wintun/routes और server egress सभी सही होने चाहिए।
| लक्षण | संभावित कारण | कैसे जाँचें | कैसे ठीक करें |
|---|---|---|---|
| ऐप connected दिखाता है, लेकिन browser local IP उपयोग करता है | system proxy लागू नहीं हुआ या PAC सक्रिय है | ProxyEnable, ProxyServer, ProxyOverride और AutoConfigURL देखें | नए version में reconnect करें ताकि 127.0.0.1:1080 वापस लगे |
| curl -x 127.0.0.1:1080 चलता है, browser नहीं | browser पुराने Windows proxy/PAC state का उपयोग कर रहा है | -x के साथ और बिना curl तुलना करें | AutoConfigURL हटाएँ या GhostMesh update करें |
| port 1080 बंद है | srsp-client नहीं चल रहा या credentials fail हुए | srsp-client process और local port जाँचें | reconnect करें, फिर login करें या log भेजें |
| log में IPv6 Network is unreachable है | server के पास IPv6 egress route नहीं है | server routes और target host जाँचें | IPv4 egress या unavailable IPv6 filter करने वाला build उपयोग करें |
Windows proxy checks
अगर curl -x http://127.0.0.1:1080 चलता है, तो srsp-client चल रहा है। समस्या आम तौर पर Windows proxy state में होती है: ProxyEnable=1 और ProxyServer=127.0.0.1:1080 के बजाय PAC/AutoConfigURL लागू है।
Working state: ProxyEnable=1, ProxyServer=127.0.0.1:1080, ProxyOverride=<local>, AutoConfigURL empty.
चेकलिस्ट
- ✓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 और bundled assets
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.
चेकलिस्ट
- ✓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 | अर्थ | Action |
|---|---|---|
| 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 |
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.
चेकलिस्ट
- ✓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
Manual proxy ठीक करता है, लेकिन 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.