Fix port "0" listen - #6640
Conversation
|
我觉得不要急着合并, bye-panic这个分支代表了还有不少Build成功但"运行时具体状态"和下游假设不一致的问题. goroutine 1 [running]: |
|
现在感觉可以了. 暂时找不到新的 |
|
root@ubuntu:~/Downloads/Xray-linux-64_26.7.28# ./xray -c config.json goroutine 1 [running]: |
There was a problem hiding this comment.
root@ubuntu:~/Xray-core# ./xray -c x.json
Xray 26.7.28 (Xray, Penetrates Everything.) Custom (go1.26.5 linux/amd64)
A unified platform for anti-censorship.
2026/08/20 13:59:16.392675 [Info] infra/conf/serial: Reading config: &{Name:1.json Format:json}
panic: runtime error: index out of range [0] with length 0
goroutine 1 [running]:
github.com/xtls/xray-core/infra/conf.validateOutboundTransportSecurity({0x13a3ca0?, 0xb9ff451c960?}, 0x3b?)
github.com/xtls/xray-core/infra/conf/xray.go:254 +0x166
github.com/xtls/xray-core/infra/conf.(*OutboundDetourConfig).Build(0xb9ff44db988)
github.com/xtls/xray-core/infra/conf/xray.go:361 +0x867
github.com/xtls/xray-core/infra/conf.(*Config).Build(0xb9ff46b0580)
github.com/xtls/xray-core/infra/conf/xray.go:681 +0x17cd
github.com/xtls/xray-core/infra/conf/serial.BuildConfig({0xb9ff43a23d0?, 0x7838ee7601e8?, 0x7839353f9bf0?})
github.com/xtls/xray-core/infra/conf/serial/builder.go:66 +0x2a
github.com/xtls/xray-core/core.LoadConfig({0x160c85f, 0x4}, {0x13428c0?, 0xb9ff43cf368?})
github.com/xtls/xray-core/core/config.go:150 +0x56e
main.startXray()
github.com/xtls/xray-core/main/run.go:219 +0x8f
main.executeRun(0x23d0620?, {0xb9ff44bf5e0?, 0x48f9e6?, 0x8000000000040?})
github.com/xtls/xray-core/main/run.go:82 +0x54
github.com/xtls/xray-core/main/commands/base.Execute()
github.com/xtls/xray-core/main/commands/base/execute.go:64 +0x59f
main.main()
github.com/xtls/xray-core/main/main.go:22 +0x1a5
root@ubuntu:~/Xray-core# cat x.json
{
"log": {
"loglevel": "warning"
},
"outbounds": [
{
"protocol": "vless",
"settings": {
"vnext": [],
"encryption": "none"
},
"streamSettings": {
"network": "tcp",
"security": "none"
}
}
]
}
因为你加了一个vnext[0] 引入了一个新的panic,本来应该failed to build outbound config with tag > infra/conf: failed to build outbound handler for protocol vless > infra/conf: VLESS settings: "vnext" should have one and only one member. Multiple endpoints in "vnext" should use multiple VLESS outbounds and routing balancer instead
这样的.
6b1fc59#diff-2683dbaba14bc856bb5c6f6e664313d25dd246b4e262deb3e886579b4f48a3b4R254
@Fangliding
close #6636
附带一些其他panic 和 close #6600