http.proxy设置了貌似不起作用，github貌似又被墙了
ringa_lee
proxychains
It’s troublesome and unstable to circumvent the wall. Why not spend some money to buy a circumvention tool and provide a Hongxing plug-in invitation link
http://honx.in/_VLUuts6vD1rMcCwd
Instead of https link, using ssh link can solve some problems. But the speed is very slow.
SS opens up a proxy for the socks protocol, which cannot be used directly for http(s)_proxy. Install a privoxy or 3proxy to transfer it yourself.
For example, I use 3proxy, configuration:
nscache 65536 timeouts 1 5 30 60 180 1800 15 60 log logformat "- +_L%t.%. %N.%p %E %U %C:%c %R:%r %O %I %h %T" rotate 7 auth iponly allow * parent 1000 socks5+ 127.0.0.1 2080 proxy -a -p2081
Then export https_proxy=127.0.0.1:2081和export http_proxy=127.0.0.1:2081 and that’s it. Github seems to use https protocol.
export https_proxy=127.0.0.1:2081
export http_proxy=127.0.0.1:2081
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
proxychains
It’s troublesome and unstable to circumvent the wall. Why not spend some money to buy a circumvention tool and provide a Hongxing plug-in invitation link
http://honx.in/_VLUuts6vD1rMcCwd
Instead of https link, using ssh link can solve some problems. But the speed is very slow.
SS opens up a proxy for the socks protocol, which cannot be used directly for http(s)_proxy.
Install a privoxy or 3proxy to transfer it yourself.
For example, I use 3proxy, configuration:
Then
export https_proxy=127.0.0.1:2081和export http_proxy=127.0.0.1:2081and that’s it.Github seems to use https protocol.