-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Frequent restarts Xray #3027
Comments
What is the reason for the restart? OOM? |
I have the same problem Here is my warning log 2024/02/16 14:17:30 WARNING - XRAY: [1646272470] app/dispatcher: non existing outTag: blocked , after couple hours (mostly 12 hours) i have to restart xray to fix it |
Add Conf: {
"outbounds": [
{
"tag": "blocked",
"protocol": "blackhole"
}
]
}
|
this is for me ? or not ? this is my xray config : ` "api": { |
I add it but it doesn't help , i still have to restart it every couple hours |
yep i think 1.8.7 is unstable and is poppy choppy |
do you use trojan config? |
I have the same problem I have 2 types of configuration
Single service using VPS 2 Core 4 GB RAM, then I tried upgrading to 4 Core 8 GB RAM, as a result the RAM always runs out and get OOM Error. User active < 20 NB: single service vmess and vless work fine |
i did test hardware config but It had no effect but xray 1.8.3 is very good and It restarts very rarely and its acceptable |
Try 1.8.4 |
The only solution that worked 100% is that the RAM of the vps is at least 4GB and version of xray must 1.8.1 |
I had this error in log before restart config: vless+TLS+TCP -- fallback --> vless + ws |
i have a bing problem with xray 1.8.7 after few hours xray automatically restarted from few minutes to 4 hours in max duration that can work without restart
so i change xray to 1.7.5 now this problem Much better than before but now every 13h will restart but very better that 1.8.7
1.8.7 is very unstable but 1.7.5 90% is more stable
But this problem is not completely solved
Can anyone guide me?
tnx
The text was updated successfully, but these errors were encountered: