Replies: 3 comments 6 replies
-
Yet, It's a fantastic feature for a powerful proxy application. |
Beta Was this translation helpful? Give feedback.
-
@RPRX Can you please make a workaround for not restarting the whole service? |
Beta Was this translation helpful? Give feedback.
-
This is not easy to implement, even HA is under criticism for not doing a hot-reload really well. xray server should still hold those 1K ws and accepting new incoming ws connections ? sounds simple but over time that xray server has to hold the oldest connection meanwhile taking care of any new connections as well. a simpler solution is to dump back the whole config.json file via CLI. So when a new inbound is added , an admin by dumping the whole new config, can copy it to config.json and reload manually. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When I add or remove a client/user, I restart xray-core. The problem with this approach is that it breaks ongoing connections for other users. They obviously don't like this, especially when downloading a large file. How do you deal with this?
It seems the api command can add/remove entire inbounds, but not single clients/users?
Ideally xray-core can work like haproxy: when you reload configuration, the old haproxy process lives until all existing connections are closed. Meanwhile new connections are already handled by a new haproxy process. This way the "reload" is just a socket transfer trick and no complicated internal reload handling is needed.
Beta Was this translation helpful? Give feedback.
All reactions