search

v2ray / v2ray-core

A platform for building proxies to bypass network restrictions.
https://www.v2ray.com/
MIT License
45.43k stars 8.95k forks source link

RemoteDesktopManager 配置代理后 客户端提示错误 rejected Proxy|Socks: unknown Socks #938

Closed sitsh closed 6 years ago

sitsh commented 6 years ago

中文： 提交 Issue 之前请先阅读 Issue 指引，然后回答下面的问题，谢谢。 除非特殊情况，请完整填写所有问题。不按模板发的 issue 将直接被关闭。

1) 你正在使用哪个版本的 V2Ray？（如果服务器和客户端使用了不同版本，请注明） 服务器 3.12 客户端x64 3.10 2) 你的使用场景是什么？比如使用 Chrome 通过 Socks/VMess 代理观看 YouTube 视频。 RemoteDesktopManager 配置一个代理 用来同步账号中存储的云配置数据 3) 你看到的不正常的现象是什么？（请描述具体现象，比如访问超时，TLS 证书错误等） RemoteDesktopManager 同步时 提示 WebException - 基础连接已经关闭: 连接被意外关闭。 在 System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) 在 System.Net.HttpWebRequest.GetRequestStream() 。。。。 v2客户端日志显示 2018/03/09 20:33:52 tcp:127.0.0.1:12425 rejected Proxy|Socks: unknown Socks version: 67 2018/03/09 20:33:52 tcp:127.0.0.1:12426 rejected Proxy|Socks: unknown Socks version: 67

SSR 代理中 RemoteDesktopManager 工作正常。

4) 你期待看到的正确表现是怎样的？

5) 请附上你的配置（提交 Issue 前请隐藏服务器端IP地址）。

服务器端配置:
    // 在这里附上服务器端配置文件
{
  "log" : {
    "access": "/var/log/v2ray/access.log",
    "error": "/var/log/v2ray/error.log",
    "loglevel": "warning"
  },
  "inbound": {
        "port": 38443,
        "protocol": "vmess",
        "settings": {
            "clients": [
                {
                    "id": "c0cabf35-149d-e143-7d73-87b904c42066",
                    "level": 1,
                    "alterId": 64
                },
        {
                    "id": "a5763252-a0f1-cc8a-f7b1-2e7574a96dce",
                    "level": 1,
                    "alterId": 64
                },
         {
                    "id": "e7492d20-1dab-18bf-6b25-c167b0d45db1",
                    "level": 1,
                    "alterId": 64
                },
                {
                    "id": "1dbb3d04-2cff-5d05-0a72-177597611e78",
                    "level": 1,
                    "alterId": 64
                },
        {
                    "id": "4d027472-ba27-4d59-90ca-72ab1a6b8658",
                    "level": 1,
                    "alterId": 64
                },
                {
                    "id": "04ea32da-7015-41da-b7ea-5fb42e276f88",
                    "level": 1,
                    "alterId": 64
                },
        {
                    "id": "865ab0a9-db80-4bc8-b3ed-993bb01aff3f",
                    "level": 1,
                    "alterId": 64
                },
                {
                    "id": "97d96772-afa9-48b3-9157-a482a6d92e20",
                    "level": 1,
                    "alterId": 64
                }
            ]
        }
    },
  "outbound": {
    "protocol": "freedom",
    "settings": {}
  },
  "outboundDetour": [
    {
      "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"
        }
      ]
    }
  }
}

客户端配置:
    // 在这里附上客户端配置
{
  "log": {
    "access": "",
    "error": "",
    "loglevel": ""
  },
  "inbound": {
    "port": 1081,
    "listen": "0.0.0.0",
    "protocol": "socks",
    "settings": {
      "auth": "noauth",
      "udp": false,
      "ip": "127.0.0.1",
      "clients": null
    },
    "streamSettings": null
  },
  "outbound": {
    "tag": "agentout",
    "protocol": "vmess",
    "settings": {
      "vnext": [
        {
          "address": "xxxxxxx",
          "port": 443,
          "users": [
            {
              "id": "a5763252-a0f1-cc8a-f7b1-2e7574a96dce",
              "alterId": 64,
              "security": "aes-128-gcm"
            }
          ]
        }
      ],
      "servers": null
    },
    "streamSettings": {
      "network": "tcp",
      "security": "",
      "tcpSettings": null,
      "kcpSettings": null,
      "wsSettings": null
    },
    "mux": {
      "enabled": false
    }
  },
  "inboundDetour": null,
  "outboundDetour": [
    {
      "protocol": "freedom",
      "settings": {
        "response": null
      },
      "tag": "direct"
    },
    {
      "protocol": "blackhole",
      "settings": {
        "response": {
          "type": "http"
        }
      },
      "tag": "blockout"
    }
  ],
  "dns": {
    "servers": [
      "8.8.8.8",
      "8.8.4.4",
      "localhost"
    ]
  },
  "routing": {
    "strategy": "rules",
    "settings": {
      "domainStrategy": "IPIfNonMatch",
      "rules": [
        {
          "type": "field",
          "port": null,
          "outboundTag": "direct",
          "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"
          ],
          "domain": null
        }
      ]
    }
  }
}

6) 请附上出错时软件输出的错误日志。在 Linux 中，日志通常在 /var/log/v2ray/error.log 文件中。

服务器端错误日志:
    // 在这里附上服务器端日志
服务器错误日志 
2018/03/08 12:38:24 [Warning] Core: V2Ray v3.12 started
2018/03/08 12:39:38 [Warning] Core: V2Ray v3.12 started
2018/03/09 06:59:38 [Warning] Core: V2Ray v3.12 started
2018/03/09 07:00:56 [Warning] Core: V2Ray v3.12 started
2018/03/09 07:17:10 [Warning] Core: V2Ray v3.12 started

客户端错误日志:
    // 在这里附上客户端日志
2018/03/09 20:33:52 tcp:127.0.0.1:12425 rejected  Proxy|Socks: unknown Socks version: 67
2018/03/09 20:33:52 tcp:127.0.0.1:12426 rejected  Proxy|Socks: unknown Socks version: 67

7) 请附上访问日志。在 Linux 中，日志通常在 /var/log/v2ray/access.log 文件中。

    // 在这里附上服务器端日志
2018/03/08 22:17:51 180.153.194.207:6578 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:17:51 180.153.194.207:6583 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:18:57 180.153.194.207:1172 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:18:58 180.153.194.207:1213 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:19:42 180.153.194.207:2565 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:19:43 180.153.194.207:2570 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:20:27 180.153.194.207:1137 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:20:27 180.153.194.207:1150 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:36:12 180.153.194.207:2060 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:36:12 180.153.194.207:2071 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:36:56 180.153.194.207:2518 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:36:57 180.153.194.207:2522 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:52:41 180.153.194.207:1157 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:52:42 180.153.194.207:1162 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:53:25 180.153.194.207:1523 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 22:53:25 180.153.194.207:1534 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:09:10 180.153.194.207:2534 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:09:11 180.153.194.207:2536 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:09:54 180.153.194.207:2788 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:09:55 180.153.194.207:2793 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:25:41 180.153.194.207:1638 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:25:41 180.153.194.207:1648 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:26:30 180.153.194.207:2266 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:26:41 180.153.194.207:2317 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:42:24 180.153.194.207:4052 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:42:24 180.153.194.207:4053 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:43:07 180.153.194.207:1165 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:43:08 180.153.194.207:1168 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:58:48 180.153.194.207:2200 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:58:49 180.153.194.207:2214 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:59:32 180.153.194.207:2574 rejected  Proxy|VMess|Encoding: invalid user
2018/03/08 23:59:33 180.153.194.207:2576 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:11:20 180.153.194.207:3270 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:11:21 180.153.194.207:3276 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:15:17 180.153.194.207:1100 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:15:18 180.153.194.207:1103 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:16:02 180.153.194.207:1404 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:16:03 180.153.194.207:1407 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:31:48 180.153.194.207:1897 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:31:49 180.153.194.207:1900 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:32:28 180.153.194.207:2194 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:32:28 180.153.194.207:2199 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:48:13 180.153.194.207:1726 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:48:14 180.153.194.207:1734 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:48:53 180.153.194.207:2230 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 00:48:54 180.153.194.207:2232 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:04:38 180.153.194.207:3805 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:04:39 180.153.194.207:3809 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:05:21 180.153.194.207:1091 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:05:22 180.153.194.207:1112 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:21:09 180.153.194.207:2293 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:21:10 180.153.194.207:2301 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:21:53 180.153.194.207:2882 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:21:53 180.153.194.207:2884 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:37:38 180.153.194.207:1092 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:37:39 180.153.194.207:1102 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:38:22 180.153.194.207:1773 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:38:23 180.153.194.207:1789 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:54:07 180.153.194.207:2851 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:54:08 180.153.194.207:2854 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:54:51 180.153.194.207:3994 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 01:54:51 180.153.194.207:4009 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:10:37 180.153.194.207:1667 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:10:37 180.153.194.207:1680 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:10:38 180.153.194.207:1696 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:10:39 180.153.194.207:1701 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:11:21 180.153.194.207:2195 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:11:21 180.153.194.207:2222 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:26:24 180.153.194.207:4396 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:26:24 180.153.194.207:4401 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:26:32 180.153.194.207:4435 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:26:33 180.153.194.207:4442 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:42:17 180.153.194.207:1254 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:42:18 180.153.194.207:1260 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:43:01 180.153.194.207:1746 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:43:02 180.153.194.207:1751 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:47:19 180.153.194.207:2265 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:47:20 180.153.194.207:2303 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:49:35 180.153.194.207:1471 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 02:49:35 180.153.194.207:1478 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 03:01:38 180.153.194.207:2304 rejected  Proxy|VMess|Encoding: invalid user
2018/03/09 03:01:38 180.153.194.207:2313 rejected  Proxy|VMess|Encoding: invalid user

8) 其它相关的配置文件（如 Nginx）和相关日志。

请预览一下你填的内容再提交。

如果你已经填完上面的问卷，请把下面的英文部份删除，再提交 Issue。

DarienRaymond commented 6 years ago

socks 的错误是你把 http 代理指向了 socks 的端口

vmess 的错误大概是系统时间不对。

sitsh commented 6 years ago

@DarienRaymond 我又去看了我的 RemoteDesktopManager 软件代理中确实没有选择 代理类型的方法。 而我的 客户端 "inbound" 配置的是 "protocol": "socks", 所以照成不兼容的吗。 那有啥 版本能解决这个不兼容呢。 本地"inbound" 能配置 多个吗 既支持 socks 有支持 http 吗

sitsh commented 6 years ago

已经自己 搞明白了 v2rayN win 客户端没有 "inboundDetour": 配置项，只能自己写json 添加了。 但是感觉 需要 配置 多协议 有些麻烦。 如果能像ssr客户端 自动在一个端口上判断 输入协议就好了呢。