EN
For older nodes (WireGuard core support), update your Docker Compose:
https://github.com/PasarGuard/panel/discussions/377

FA (فارسی)
برای نودهای قدیمی (پشتیبانی WireGuard core)، Docker Compose را آپدیت کنید:
https://github.com/PasarGuard/panel/discussions/377

RU
Для старых нод (поддержка WireGuard core) обновите Docker Compose:
https://github.com/PasarGuard/panel/discussions/377

ZH (中文)
旧节点（支持 WireGuard core）请更新 Docker Compose：
https://github.com/PasarGuard/panel/discussions/377

This goal keeps multi-version MTProto proxies (including latest Fake-TLS) running efficiently under those constraints, with per-account IP limits, connection quotas, and usage ratio display.
For now, all it takes is a ⭐️ on GitHub — no payment needed. We're still finalizing the code before opening contributions, so a star is the easiest way to show support until then.
Help keep access to information alive.

https://github.com/PasarGuard/panel

Since Russian community asked for it, we activate the donation for HWID. To ensure your payment is counted for this goal, create an invoice with the "Donate to this Goal" button; otherwise, it will be counted for admin permission management.

https://donate.pasarguard.org

نتیجه دونیت نکردن

🔧 Bug Fix: User Disconnection via gRPC API — PasarGuard Patch

A known bug in Xray-core allows users removed via the gRPC API to keep their active connections alive and continue sending traffic — even after being deleted. This has caused serious issues for many operators whose customers exploited this loophole, leading to unexpected data overages and inflated bills.

The PasarGuard team has identified and fixed this issue, and submitted a pull request to the upstream Xray\-core repository:
🔗 https://github.com/XTLS/Xray-core/pull/5844

We have also compiled patched builds for Alpine Linux (amd64 / arm64) that have been running on production environments for nearly a month with no reported issues.

---

⚙️ Setup Guide

Step 1 — Upload the zip file to your server, navigate to the directory where you uploaded it, then run:

mkdir -p /var/lib/pg-node/xray-core/
cp xray-amd64.zip /var/lib/pg-node/xray-core/
cd /var/lib/pg-node/xray-core/
unzip xray-amd64.zip
mv xray-amd64 xray
chmod +x xray

⚠️ Make sure you are in the same directory as the zip file before running the commands above\.

Step 2 — Edit your node env file:

pg-node edit-env

Find the line below (or add it if missing) and remove the # comment:

XRAY_EXECUTABLE_PATH = /var/lib/pg-node/xray-core/xray

Step 3 — Restart the node:

pg-node restart

✅ Done! This process is the same as setting a custom Xray-core version and works with any panel that uses the Xray API.

---

💬 How you can help

— Test the builds on your own production setup
— Don't trust pre-built binaries? Build it yourself from our branch:
🔗 https://github.com/ImMohammad20000/Xray-core/tree/UserConnTracker
— Found an issue? Report it on the PR with logs and proof
— Everything working fine? Leave a comment on the PR to help get it merged faster
— Support the team's continued work:
💙 https://donate.pasarguard.org