search

bepass-org / warp-plus

Warp+Psiphon, an anti censorship utility for iran
MIT License
1.46k stars 247 forks source link

Warp-plus couldn't establish a connection #182

Open sunba91-su opened 2 months ago

sunba91-su commented 2 months ago

V1.2.3

Hello every one. I have one Ubuntu server VPS with a static IP address, that hosted in my Lab zone. I deploy warp-plus latest release (V1.2.3) on my Ubuntu server and make port binding (-b 0.0.0.0:20301) to make this service available to all of my clients that exist in my Lab zone. I make one systemd Unit to make warp-plus available automatically on reboot or failure.

From two day a go I couldn't connect to Warp-plus, and when I check the logs I got this error :

warp --cfon --scan -b 0.0.0.0:20301
time=2024-07-06T14:54:00.721Z level=INFO msg="psiphon mode enabled" country=AT
time=2024-07-06T14:54:00.722Z level=INFO msg="scanner mode enabled" max-rtt=1s
time=2024-07-06T14:54:00.724Z level=INFO msg="successfully loaded warp identity" subsystem=warp/account
time=2024-07-06T14:54:06.961Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=162.159.192.215 error="read udp 192.168.1.110:47836->162.159.192.215:500: i/o timeout"
time=2024-07-06T14:54:12.847Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=162.159.195.109 error="read udp 192.168.1.110:34930->162.159.195.109:1180: i/o timeout"
time=2024-07-06T14:54:20.162Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=188.114.96.251 error="read udp 192.168.1.110:47643->188.114.96.251:2506: i/o timeout"
time=2024-07-06T14:54:20.163Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=2606:4700:d0:0:5dec:f198:2997:3481 error="dial udp [2606:4700:d0:0:5dec:f198:2997:3481]:946: connect: network is unreachable"
time=2024-07-06T14:54:27.292Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=188.114.99.43 error="read udp 192.168.1.110:52940->188.114.99.43:894: i/o timeout"
time=2024-07-06T14:54:27.410Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=162.159.193.31 error="error sending random packet: write udp 192.168.1.110:53334->162.159.193.31:1387: write: connection refused"
time=2024-07-06T14:54:27.412Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=2606:4700:d1:0:d9a8:4f05:896a:a995 error="dial udp [2606:4700:d1:0:d9a8:4f05:896a:a995]:1843: connect: network is unreachable"
time=2024-07-06T14:54:35.917Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=188.114.97.211 error="read udp 192.168.1.110:46143->188.114.97.211:894: i/o timeout"
time=2024-07-06T14:54:42.669Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=162.159.192.54 error="read udp 192.168.1.110:42918->162.159.192.54:890: i/o timeout"
time=2024-07-06T14:54:44.725Z level=INFO msg="scan results" endpoints="[{AddrPort:162.159.195.74:2408 RTT:144.690111ms CreatedAt:2024-07-06 14:54:44.423329106 +0000 UTC m=+43.705755470} {AddrPort:188.114.98.157:945 RTT:156.689925ms CreatedAt:2024-07-06 14:54:29.011617443 +0000 UTC m=+28.294043820}]"
time=2024-07-06T14:54:44.725Z level=INFO msg="using warp endpoints" endpoints="[162.159.195.74:2408 188.114.98.157:945]"
time=2024-07-06T14:54:44.725Z level=INFO msg="running in Psiphon (cfon) mode"
time=2024-07-06T14:54:44.725Z level=INFO msg="successfully loaded warp identity" subsystem=warp/account
time=2024-07-06T14:54:46.033Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=188.114.96.78 error="invalid handshake response length 16 bytes"
time=2024-07-06T14:56:55.939Z level=ERROR msg="connection test failed" error="Get \"http://1.1.1.1:80/\": connect tcp 1.1.1.1:80: operation timed out"
time=2024-07-06T14:56:55.939Z level=ERROR msg="context deadline exceeded"

I try to run warp-plus service with --gool option, but got this error:

time=2024-07-06T14:58:52.858Z level=INFO msg="scanner mode enabled" max-rtt=1s
time=2024-07-06T14:58:52.860Z level=INFO msg="successfully loaded warp identity" subsystem=warp/account
time=2024-07-06T14:58:53.063Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=2606:4700:d1:0:d467:fab5:410:e09b error="dial udp [2606:4700:d1:0:d467:fab5:410:e09b]:3138: connect: network is unreachable"
time=2024-07-06T14:59:00.537Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=162.159.195.111 error="read udp 192.168.1.110:52009->162.159.195.111:2371: i/o timeout"
time=2024-07-06T14:59:06.492Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=162.159.192.129 error="read udp 192.168.1.110:53545->162.159.192.129:3581: i/o timeout"
time=2024-07-06T14:59:07.862Z level=INFO msg="scan results" endpoints="[{AddrPort:188.114.99.213:946 RTT:147.849582ms CreatedAt:2024-07-06 14:59:07.629510139 +0000 UTC m=+14.775215946} {AddrPort:188.114.98.127:859 RTT:174.749581ms CreatedAt:2024-07-06 14:58:54.264488683 +0000 UTC m=+1.410194509}]"
time=2024-07-06T14:59:07.863Z level=INFO msg="using warp endpoints" endpoints="[188.114.99.213:946 188.114.98.127:859]"
time=2024-07-06T14:59:07.864Z level=INFO msg="running in warp-in-warp (gool) mode"
time=2024-07-06T14:59:07.864Z level=INFO msg="successfully loaded warp identity" subsystem=warp/account
time=2024-07-06T14:59:14.418Z level=ERROR msg="ping error" subsystem=scanner subsystem=scanner/engine addr=162.159.193.255 error="read udp 192.168.1.110:46334->162.159.193.255:2371: i/o timeout"
time=2024-07-06T14:59:26.033Z level=ERROR msg="connection test failed" error="Get \"https://1.1.1.1/\": net/http: timeout awaiting response headers"
time=2024-07-06T14:59:46.123Z level=ERROR msg="connection test failed" error="Get \"http://1.1.1.1:80/\": net/http: timeout awaiting response headers"
time=2024-07-06T14:59:46.123Z level=ERROR msg="context deadline exceeded"

what's the problem and how can i fix it? thanks.

sunba91-su commented 1 month ago

I was reviewing the source code and found a line that defines constants const connTestEndpoint = "https://www.gstatic.com/generate_204" but this URL is inaccessible. Does it affect my issue?

sunba91-su commented 1 month ago

it's like wireguard protocol blocked by most ISPs