Repository navigation
Two things: the second upstream 3x-ui sync, and the rename of the IP-limit
Fail2ban names to this project's own.
The rename is the part that needed care. Upstream called the jail 3x-ipl and
the panel's ban log 3xipl.log; they are now easyxray-ipl and
easyxray-ipl.log, and the iptables chain follows the jail to
f2b-easyxray-ipl. The panel and the jail have to name the same file — the panel
appends a ban line, the jail tails it — so the renamed path is compiled into the
binary, and the renamed jail is installed by the same release that ships it.
A host that already carries the old jail is converted by the update: the old jail
is stopped first, which is what runs its actionstop and takes the old chain
down, and then its four config files are removed and each log file is moved to
its new name. Moving rather than recreating keeps the inode, so a panel that
already holds the log open keeps writing into the file Fail2ban now reads.
Running the update twice is a no-op. Containers make the same conversion at
start, and also drop a stale f2b-3x-ipl chain, which under --network=host
sits in the host netns and would otherwise outlive a daemon that died without
running its actionstop.
The rest of the diff is the upstream sync merged this cycle, through f8b72de9;
its behaviour change is that the node traffic merge now writes only the client
rows that changed.
Upgrading from 1.0.0 through 1.0.2 needs no manual step — the conversion runs
with the update.
Install (Linux):
bash <(curl -Ls https://raw.githubusercontent.com/EasyXrayTeam/EasyXray/main/install.sh)
Docker:
docker run -d --network=host --cap-add=NET_ADMIN --cap-add=NET_RAW
-v $PWD/db/:/etc/easyxray/ -v $PWD/cert/:/root/cert/
ghcr.io/easyxrayteam/easyxray:latest
Per-architecture archives and their sha256 checksums are attached below.