search

getlantern / lantern-client

Lantern Client code
GNU General Public License v3.0
14 stars 3 forks source link

Update hit_proxy script to use bin/lc #1139

Closed atavism closed 3 months ago

atavism commented 4 months ago

ptool has been subsumed by lantern-cloud/bin/lc. This PR updates hit_proxy.bash to use it instead.

atavism commented 4 months ago

Hey @hwh33, I wanted to do some further debugging why we are getting I/o timeout errors dialing certain proxies:

Jul 30 14:26:51.914 - 0m6s DEBUG bandit: bandit.go:77 Dialer jigglypuff-02205c94-f7ad-408f-a034-c8fe3a47d032 failed: dial tcp 132.145.65.11:443: i/o timeout
Jul 30 14:26:51.915 - 0m6s DEBUG bandit: bandit.go:77 Dialer wigglytuff-d891a837-1f7c-4908-a987-841270710518 failed: dial tcp 158.101.211.21:443: i/o timeout
Jul 30 14:26:51.915 - 0m6s DEBUG bandit: bandit.go:77 Dialer jigglypuff-1a31b4d7-6f8e-422c-b445-a3d004500747 failed: dial tcp 130.162.187.144:443: i/o timeout
Jul 30 14:26:51.915 - 0m6s DEBUG bandit: bandit.go:77 Dialer wigglytuff-af6bdcc3-54f6-421e-becf-b7dc18c793c8 failed: dial tcp 150.230.116.1:443: i/o timeout

I updated hit_proxy.bash to use bin/lc, and I'm trying to run it this way, passing one of the UUIDs or IP addresses listed above. I get the following:

➜  lantern-client git:(atavism/update-hit-proxy) ✗ ./hit_proxy.bash 130.162.187.144
Generating config for 130.162.187.144 in /tmp/hit_lc_proxy/130.162.187.144/proxies.yaml...
➜  lantern-client git:(atavism/update-hit-proxy) ✗ cat /tmp/hit_lc_proxy/130.162.187.144/proxies.yaml
  ERROR   no routes matched (traceID: 082806129b904a17ea93361a4653af1d)

...
➜  lantern-client git:(atavism/update-hit-proxy) ✗ ./hit_proxy.bash 1a31b4d7-6f8e-422c-b445-a3d004500747
Generating config for 1a31b4d7-6f8e-422c-b445-a3d004500747 in /tmp/hit_lc_proxy/1a31b4d7-6f8e-422c-b445-a3d004500747/proxies.yaml...
➜  lantern-client git:(atavism/update-hit-proxy) ✗ cat /tmp/hit_lc_proxy/1a31b4d7-6f8e-422c-b445-a3d004500747/proxies.yaml
  ERROR   no routes matched (traceID: 1f038b7d8664a0bb918bc1cb8459e22d)

Is that because the proxy has already been destroyed, or am I maybe running the script incorrectly?