v2ray/v2ray-core

4.45.2 v2ray sock5 forward failed

Opened this issue · 2 comments

blackjack550 commented

Please answer all the questions with enough information. All issues not following this template will be closed immediately.
If you are not sure if your question is truely a bug in V2Ray, please discuss it here first.

  1. What version of V2Ray are you using (If you deploy different version on server and client, please explicitly point out)?
    V2Ray 4.45.2 (V2Fly, a community-driven edition of V2Ray.) Custom (go1.18.3 linux/amd64)
  2. What's your scenario of using V2Ray? E.g., Watching YouTube videos in Chrome via Socks/VMess proxy.
    i explored website in chrome
  3. What did you see? (Please describe in detail, such as timeout, fake TLS certificate etc)
    i want to setup socks configure in outbound,some traffic go out from cloudflare-warp.it's standard sock5 server.
    but the v2ray is not work fine.i'll try my sock5server is work fine.
    curl http://if.1117life.com --socks5 127.0.0.1:4018
    104.28.152.116
  4. What's your expectation?
    some traffic can send to sock5 server
  5. Please attach your configuration file (Mask IP addresses before submit this issue).

Server configuration:
{
"log": {
"access": "/var/log/v2ray/access.log", #路径自定
"error": "/var/log/v2ray/error.log", #路径自定
"loglevel": "debug"
},
"inbounds": [{
"port": 3333,
"tag":"default",
"protocol": "vless",
"settings": {
"decryption":"none",
"clients": [
{
"id": "ac0f3e32-f22d-11ec-b939-0333ac120002", #UUID自定
"level": 0
}
]
},
"streamSettings": {
"network": "ws",
"wsSettings": {
"path": "/wp-admin"
}
}
}],
"outbounds": [
{
"protocol": "freedom",
"tag": "direct",
"settings": {}
},
{
"protocol": "freedom",
"tag": "direct6",
"settings": {"domainStrategy": "UseIPv6"}
},
{
"protocol": "socks",
"sendThrough":"127.0.0.1",
"tag": "warp",
"settings":{"servers":[{"address": "127.0.0.1","port": 4018 }]}
},
{
"protocol": "blackhole",
"settings": {},
"tag": "blocked"
}
],
"routing": {
"strategy": "rules",
"settings": {
"rules": [
{
"type": "field",
"ip": [
"0.0.0.0/8",
"10.0.0.0/8",
"100.64.0.0/10",
"127.0.0.0/8",
"169.254.0.0/16",
"172.16.0.0/12",
"192.0.0.0/24",
"192.0.2.0/24",
"192.168.0.0/16",
"198.18.0.0/15",
"198.51.100.0/24",
"203.0.113.0/24",
"::1/128",
"fc00::/7",
"fe80::/10"
],
"outboundTag": "blocked"
},
{
"type": "field",
"domain": [
"if.1117life.com"
],
"outboundTag": "warp",
"inboundTag": ["default"]
},
{
"type": "field",
"outboundTag": "direct",
"inboundTag":["default"]
}

  ]
}

}
}

    // Please attach your server configuration here.

Client configuration:
client is ok

    // Please attach your client configuration here.
  1. Please attach error logs, especially the bottom lines if the file is large. Error log file is usually at /var/log/v2ray/error.log on Linux.

Server error log:
2024/10/30 01:44:04 [Info] [1420811145] proxy/vless/inbound: firstLen = 38
2024/10/30 01:44:04 [Info] [1420811145] proxy/vless/inbound: received request for tcp:if.1117life.com:80
2024/10/30 01:44:04 [Info] [1420811145] app/dispatcher: taking detour [warp] for [tcp:if.1117life.com:80]
2024/10/30 01:44:04 [Info] [1420811145] transport/internet/tcp: dialing TCP to tcp:127.0.0.1:4018
2024/10/30 01:44:04 [Warning] [1420811145] app/proxyman/outbound: failed to process outbound traffic > proxy/socks: failed to establish connection to server > proxy/socks: server rejects request: 1
2024/10/30 01:44:04 [Info] [1420811145] app/proxyman/inbound: connection ends > proxy/vless/inbound: connection ends > io: read/write on closed pipe

    // Please attach your server error log here.

Client error log:

    // Please attach your client error log here.
  1. Please attach access log. Access log is usually at '/var/log/v2ray/access.log' on Linux.
    // Please attach your server access log here.

  1. Other configurations (such as Nginx) and logs.
    work fine

  2. If V2Ray doesn't run, please attach output from --test.
    v2ray runing is ok
    The command is usually /usr/bin/v2ray/v2ray --test --config /etc/v2ray/config.json, but may vary according to your scenario.

  3. If V2Ray service doesn't run, please attach journal log.

Usual command is journalctl -u v2ray.

Please review your issue before submitting.

blackjack550 commented

I capture network packages, i found:
Curl:
PSH,ACK i got payload infomation,like this:GET / HTTP/1.1 User-Agent:Curl 7.29.Host:if.1117life.com.....
v2ray:
PSH,ACK like this: if.1117life.com.P...
diff this, i guess that v2ray doesn't send correct format ,like http

fish4terrisa-MSDSM commented

Also faced this problem... Does anyone knows how to solve this?