Open fgggid opened 1 month ago
apt config Acquire::http { Pipeline-Depth "200"; }
and "Acquire::Queue-Mode "host";"
are irrelevant, can reproduce without these.
Thank for reporting. Try the version here https://github.com/XTLS/Xray-core/actions/runs/11303197293 for your server
Ok, I will try it on server from now.
I can see below errors occasionally. Does this mean the issue is successfully mitigated?
2024/10/13 00:08:44 [Error] common/session: Multiple goroutine is tring to access one routing content, tring to write host:security.ubuntu.com
2024/10/13 00:08:44 [Error] common/session: Multiple goroutine is tring to access one routing content, tring to write cache-control:max-age=0
...
2024/10/13 00:16:08 [Error] common/session: Multiple goroutine is tring to access one routing content, tring to write accept:text/*
2024/10/13 00:16:08 [Error] common/session: Multiple goroutine is tring to access one routing content, tring to write :method:GET
...
2024/10/13 00:18:15 [Error] common/session: Multiple goroutine is tring to access one routing content, tring to write host:security.ubuntu.com
2024/10/13 00:18:15 [Error] common/session: Multiple goroutine is tring to access one routing content, tring to write if-modified-since:Thu, 25 Apr 2024 15:11:21 GMT
Yes, mitigate This involves a fairly old problem, and what I can do is not let it panic. A complete fix may require more work
Ok, I'm fine for now.
I would keep this issue open until the actual bug is fixed. Things are potentially getting mis-routed under mux.cool.
Integrity requirements
Description
xray server crash when I do 'apt update' using vless + tls
I don't think I ever see this issue before v24. After I start using v24.9.30, I begin see such crash occasionally on my vps server.
This seems to be a timing issue, not always reproducible, but with time, you can reproduce it.
Reproduction Method
start 3 terminals
terminal 1: (xray server) xray run -config ./config.json
terminal 2: (xray client) xray run -config ./config.json
terminal 3: (do apt update with loop, in case you don't have env, my example is using docker/podman to reproduce) docker run -ti --rm --network host ubuntu:noble bash cat << \EOF | tee /etc/apt/apt.conf.d/99z-custom Acquire::Queue-Mode "host"; Acquire::http { Pipeline-Depth "200"; } Acquire::http::Proxy "http://127.0.0.1:8080"; Acquire::https::Proxy "http://127.0.0.1:8080"; EOF while :; do apt update && sleep 60 || break ; done
Client config
Server config
Client log
Server log