Closed EchoVRC closed 1 day ago
I think this is not a serious problem. (Not priority) The inbound might takes a while to up, you can retry
The main problem is that if the json contains multiple inbound, it crashes on the first one and the others don't apply.
I think you should do one at a time. Can you post the crash log?
I've already done that. See Server log in the original post.
Another interesting point. If you remove wireguard inboond under load, the server keeps trying to send keepalive... Something seems to remain after removal(((
To some extent, the implementation of Wireguard inbound is not standardized. I think we should declare which protocols the API is applicable to
Check out https://github.com/XTLS/Xray-core/blob/a35d5719f425f061a3274e2ba51481299853ea82/proxy/wireguard/gvisortun/tun.go#L176 this part I'm not an expert, but if you rewrite this part so that it closes all connections/goroutine normally, the problem will be solved
hi in new ver xray i get this error when xray restart
"Failed to start: main: failed to load config files: [bin/config.json] > infra/conf: Failed to build SplitHTTP config. > infra/conf: maxConnections cannot be specified together with maxConcurrency"
Integrity requirements
Description
Summary: When removing and immediately re-adding an inbound with the same tag using the Xray API, the system throws errors. The initial attempt results in a DeadlineExceeded error, and subsequent attempts return an existing tag found error. This indicates a race condition or incomplete state clearance in the Xray API when handling rapid inbound changes.
Reproduction Method
./xray api rmi --server 127.0.0.1:9000 wireguard-7; ./xray api adi --server 127.0.0.1:9000 generated_config/wireguard.json
generated_config/wireguard.json
Client config
Server config
Client log
Server log