2026/01/16 01:22:56 Using config from STDIN
panic: runtime error: invalid memory address or nil pointer dereference
2026/01/16 01:34:21 Using config from STDIN
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0xd8 pc=0x557b52326bfe]
goroutine 1 [running]:
github.com/v2fly/v2ray-core/v5/infra/conf/v2jsonpb.(*V2JsonProtobufFollowerFieldDescriptor).Number(0x0?)
<autogenerated>:1 +0x1e
google.golang.org/protobuf/encoding/protojson.decoder.unmarshalMessage({0xc0005b66e0, {{}, 0x1, 0x0, {0x557b52b0b010, 0xc0004e99c0}, 0x270f}}, {0x557b52b21f98, 0xc0004e99d0}, 0x0)
google.golang.org/protobuf@v1.36.10/encoding/protojson/decode.go:208 +0x885
google.golang.org/protobuf/encoding/protojson.UnmarshalOptions.unmarshal({{}, 0x1, 0x0, {0x557b52b0b010, 0xc0004e99c0}, 0x2710}, {0xc0001a4768, 0x12, 0x12}, {0x557b52af9d40, ...})
google.golang.org/protobuf@v1.36.10/encoding/protojson/decode.go:80 +0x1bc
google.golang.org/protobuf/encoding/protojson.UnmarshalOptions.Unmarshal(...)
google.golang.org/protobuf@v1.36.10/encoding/protojson/decode.go:63
github.com/v2fly/v2ray-core/v5/infra/conf/v2jsonpb.loadV2JsonPb({0xc0001a4768, 0x12, 0x12})
github.com/v2fly/v2ray-core/v5/infra/conf/v2jsonpb/v2jsonpb.go:21 +0x19c
github.com/v2fly/v2ray-core/v5/infra/conf/v2jsonpb.init.0.func1({0x557b527a7ce0?, 0xc000181740?})
github.com/v2fly/v2ray-core/v5/infra/conf/v2jsonpb/v2jsonpb.go:60 +0x58
github.com/v2fly/v2ray-core/v5.loadSingleConfigByTryingAllLoaders({0x557b527a7ce0, 0xc000181740})
github.com/v2fly/v2ray-core/v5/config.go:174 +0xa2
github.com/v2fly/v2ray-core/v5.loadSingleConfigAutoFormat({0x557b52ac5420?, 0xc00008c040?})
github.com/v2fly/v2ray-core/v5/config.go:148 +0x14c
github.com/v2fly/v2ray-core/v5.LoadConfig({0x557b52465b22, 0x4}, {0x557b527f2100, 0x557b53cc6aa0})
github.com/v2fly/v2ray-core/v5/config.go:110 +0x111
github.com/v2fly/v2ray-core/v5/main/commands.startV2Ray()
github.com/v2fly/v2ray-core/v5/main/commands/run.go:209 +0x4c
github.com/v2fly/v2ray-core/v5/main/commands.executeTest(0x557b536c6840, {0xc000052110, 0x0, 0x0})
github.com/v2fly/v2ray-core/v5/main/commands/test.go:54 +0x8a
github.com/v2fly/v2ray-core/v5/main/commands/base.Execute()
github.com/v2fly/v2ray-core/v5/main/commands/base/execute.go:67 +0x5cb
main.main()
github.com/v2fly/v2ray-core/v5/main/main.go:16 +0x277
你正在使用哪个版本的 V2Ray？
5.42.0/5.43.0
你看到的异常现象是什么？
你期待看到的正常表现是怎样的？
对有效或无效配置文件的响应像是直接读取文件那样
请附上你的配置
本例中的有效但崩溃配置：
{ "status": {} }无效但正常配置：
{ I say Configuration OK. "status": {} }or{ "status": {} I say Configuration OK. }有效且正常配置：
/**/{ "status": {} }无效不通过配置：
{ I "status": {} I }请附上出错时软件输出的错误日志
test 与 run 的错误大同小异