-
Notifications
You must be signed in to change notification settings - Fork 12.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: 混合端口使用git时好时坏 #6786
Labels
bug
Something isn't working
Comments
#6321 我看了这个issue也有人说,感觉这个不是个例,目前我只能退回老版本使用了 |
换了 V6.33 的版本 git 就一切正常了 |
你切换到 sing-box 内核测试下,排除下是否 xray 的混合端口有问题? |
#6321 |
可能你的git代理需要重新设置一下,我是这么修好的 git config --global --unset http.proxy
git config --global --unset https.proxy
git config --global http.proxy http://127.0.0.1:10808
git config --global https.proxy http://127.0.0.1:10808 也有可能是别的地方修好的,我折腾了蛮久不知道怎么回事就突然好了 |
建议这样测试。
|
老版本的v2ray也出问题了,我怀疑台式机有问题了。我的笔记本看起来v2ray的最新版本是好的 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
操作系统和版本
window 10
预期情况
使用混合端口用git推代码,有时候可以,有时候就不行。
实际情况
使用混合端口用git推代码,有时候可以,有时候就不行。
之前用10809代理git基本上没有失败过,现在使用混合端口10次有5次都是失败的,有时候必须重启才生效。
浏览器科学上网是正常的。
复现方法
v2rayN 7.8.9
git设置代理:
git config --global http.proxy http://127.0.0.1:10808
git config --global https.proxy https://127.0.0.1:10808
错误日志: Failed to connect to 127.0.0.1 port 10808 after 21057 ms: Couldn't connect to server
日志信息
2025/02/23 18:47:27 from 127.0.0.1:56450 accepted //otheve.beacon.qq.com:443 [socks -> block]
2025/02/23 18:47:27 from 127.0.0.1:56452 accepted //h.trace.qq.com:443 [socks -> block]
2025/02/23 18:47:27 from 127.0.0.1:56453 accepted //h.trace.qq.com:443 [socks -> block]
2025/02/23 18:47:27 from 127.0.0.1:56454 accepted //api.github.com:443 [socks >> proxy]
2025/02/23 18:47:28 from 127.0.0.1:56458 accepted //beacons5.gvt3.com:443 [socks >> proxy]
2025/02/23 18:47:28 from 127.0.0.1:56462 accepted //beacons.gcp.gvt2.com:443 [socks -> block]
2025/02/23 18:47:28 from 127.0.0.1:56464 accepted //beacons.gvt2.com:443 [socks -> block]
2025/02/23 18:47:28 from 127.0.0.1:56466 accepted //beacons.gvt2.com:443 [socks -> block]
2025/02/23 18:47:28 from 127.0.0.1:56467 accepted //beacons.gvt2.com:443 [socks -> block]
2025/02/23 18:47:28 from 127.0.0.1:56468 accepted //beacons2.gvt2.com:443 [socks -> block]
2025/02/23 18:47:28 from 127.0.0.1:56471 accepted //beacons2.gvt2.com:443 [socks -> block]
2025/02/23 18:47:28 from 127.0.0.1:56473 accepted //beacons.gvt2.com:443 [socks -> block]
2025/02/23 18:47:28 from 127.0.0.1:56487 accepted //beacons5.gvt2.com:443 [socks -> block]
2025/02/23 18:47:28 from 127.0.0.1:56488 accepted //beacons4.gvt2.com:443 [socks -> block]
2025/02/23 18:47:28 from 127.0.0.1:56490 accepted //beacons4.gvt2.com:443 [socks -> block]
2025/02/23 18:47:40 from 127.0.0.1:56502 accepted //update.googleapis.com:443 [socks -> direct]
2025/02/23 18:47:53 from 127.0.0.1:56505 accepted //download.jetbrains.com:443 [socks >> proxy]
2025/02/23 18:47:54 from 127.0.0.1:56507 accepted //download-cdn.jetbrains.com:443 [socks >> proxy]
2025/02/23 18:48:04 [Warning] [3024495407] proxy/http: failed to read response from github.com:8080 > unexpected EOF
2025/02/23 18:48:04 [Warning] [3024495407] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:10808->127.0.0.1:56347: wsasend: An established connection was aborted by the software in your host machine.
2025/02/23 18:48:04 [Warning] [4069165747] proxy/http: failed to read response from github.com:8080 > unexpected EOF
2025/02/23 18:48:04 [Warning] [4069165747] app/proxyman/inbound: connection ends > proxy/http: connection ends > proxy/http: failed to write response > write tcp 127.0.0.1:10808->127.0.0.1:56348: wsasend: An established connection was aborted by the software in your host machine.
2025/02/23 18:48:08 from 127.0.0.1:56516 accepted //ssl.gstatic.com:443 [socks -> proxy]
2025/02/23 18:48:08 from 127.0.0.1:56518 accepted //www.google.com.hk:443 [socks >> proxy]
额外信息
No response
我确认已更新至最新版本
我确认已查询历史issues
The text was updated successfully, but these errors were encountered: