Skip to content
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

使用ss2022+httpupgrade出现时而通,时而不通的情况 #3328

Closed
2 tasks done
moranno opened this issue May 3, 2024 · 4 comments
Closed
2 tasks done

使用ss2022+httpupgrade出现时而通,时而不通的情况 #3328

moranno opened this issue May 3, 2024 · 4 comments

Comments

@moranno
Copy link

moranno commented May 3, 2024

完整性要求

  • 我保证阅读了文档,了解所有我编写的配置文件项的含义,而不是大量堆砌看似有用的选项或默认值。
  • 我搜索了issues,没有发现已提出的类似问题。

版本

1.8.11

描述

使用ss2022+httpupgrade出现时而通,时而不通的情况

重现方式

按如下配置,ss2022+httpupgrade传输
服务端配置:

    "inbounds": [
        {
            "listen": "0.0.0.0",
            "port": 8005,
            "protocol": "shadowsocks",
            "settings": {
                "method": "2022-blake3-aes-128-gcm",
                "password": "Yjg5YzA5NDNhNGQ5NzU1Mw==",
                "clients": [
                    {
                      "password": "NDZmMzM1ZTYtOTg0MS00ZQ=="
                    }
                ]
            },
            "streamSettings": {
                "network": "httpupgrade",
                "httpupgradeSettings": {
                    "path": "/web"
                }
            },
            "sniffing": {
                "enabled": true,
                "destOverride": [
                    "http",
                    "tls",
                    "quic"
                ]
            }
        }
    ],

客户端配置:

    "outbounds": [
        {
            "protocol": "shadowsocks",
            "settings": {
              "servers": [
                {
                  "address": "11.11.11.11",
                  "port": 8005,
                  "method": "2022-blake3-aes-128-gcm",
                  "password": "Yjg5YzA5NDNhNGQ5NzU1Mw==:NDZmMzM1ZTYtOTg0MS00ZQ=="
                }
              ]
            },
            "streamSettings": {
                "network": "httpupgrade",
                "httpupgradeSettings": {
                    "path": "/web?ed=2560"
                }
            },
            "tag": "proxy"
        },
        {
            "protocol": "freedom",
            "tag": "direct"
        }
    ]

日志

不通的时候服务端没有日志,
通的时候服务端日志:

2024/05/03 16:30:23 45.12.3.23:61502 accepted encrypted-tbn3.gstatic.com:443 [direct] email: unnamed-user-0-a44e40e0-199c-454c-8e2a-8e85aa687f5a
2024/05/03 16:30:23 [Info] [1624427075] proxy/freedom: connection opened to tcp:encrypted-tbn3.gstatic.com:443, local endpoint [2xxx:xxx4:6xxxd1:xxxd:4xxb:cxx6:dxx8]:52490, remote endpoint [2404:6800:4004:80a::200e]:443
2024/05/03 16:30:23 [Info] [1624427075] proxy: CopyRawConn readv
2024/05/03 16:30:23 [Info] [1790558026] proxy/shadowsocks_2022: tunnelling request to tcp:www.gstatic.com:443
2024/05/03 16:30:23 [Info] [1790558026] app/dispatcher: sniffed domain: www.gstatic.com
2024/05/03 16:30:23 [Info] [1790558026] app/dispatcher: default route for tcp:www.gstatic.com:443
2024/05/03 16:30:23 [Info] [1790558026] transport/internet/tcp: dialing TCP to tcp:www.gstatic.com:443
2024/05/03 16:30:23 [Debug] transport/internet: dialing to tcp:www.gstatic.com:443
@Fangliding
Copy link
Member

完全没有日志大抵是被阻断了

@Fangliding Fangliding closed this as not planned Won't fix, can't repro, duplicate, stale May 3, 2024
@moranno
Copy link
Author

moranno commented May 3, 2024

完全没有日志大抵是被阻断了

我在本地测试的,麻烦关闭issue的前自己测一下:

不通的时候:

image

通的时候:

image

@Fangliding
Copy link
Member

理论上底层传输只能搭配vless vmess 其他协议不知道有没有和底层连接完全解耦 说白了不支持这么组合 所以完全可能出问题 换掉ss或者去掉http upgrade 再看看

@Fangliding Fangliding reopened this May 3, 2024
@RPRX
Copy link
Member

RPRX commented May 7, 2024

如上所述,如果你需要内层加密,请把 SS2022 换成 VMess,不要执着于奇奇怪怪的组合,SS2022 is not designed for *ray

@RPRX RPRX closed this as not planned Won't fix, can't repro, duplicate, stale May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants