-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Bug Report: Inbound Addition Failure in Xray API #3806
Comments
I think this is not a serious problem. (Not priority) |
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? |
To some extent, the implementation of Wireguard inbound is not standardized. |
Check out Xray-core/proxy/wireguard/gvisortun/tun.go Line 176 in a35d571
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
The text was updated successfully, but these errors were encountered: