MHSanaei 7f64a67ba5 fix(clients): re-enable only quota-disabled clients on a traffic reset ...

Every traffic reset re-enabled its clients unconditionally, in the
client record and in the traffic row a master treats as the client's
state. A master forwards an inbound's scheduled reset and "reset all"
to its nodes through the per-client reset calls, so a client disabled
by hand on a node inbound came back on at the next scheduled reset.

Each reset now decides, before it zeroes the counters, which of its
clients the quota switched off, counting cross-panel usage, and
re-enables only those; a client disabled below its quota keeps its
record and traffic row off. The reset API docs say so.

2026-11-01 08:31:27 +01:00

..

images

feat(hosts): add drag-and-drop and global subscription ordering (#6895)

2026-10-24 07:27:47 +02:00

CNAME

docs: vendor the documentation site into the monorepo

2026-07-07 23:07:14 +02:00

favicon.png

docs: vendor the documentation site into the monorepo

2026-07-07 23:07:14 +02:00

icon.png

docs: vendor the documentation site into the monorepo

2026-07-07 23:07:14 +02:00

logo-dark.png

docs: vendor the documentation site into the monorepo

2026-07-07 23:07:14 +02:00

logo-light.png

docs: vendor the documentation site into the monorepo

2026-07-07 23:07:14 +02:00

openapi.json

fix(clients): re-enable only quota-disabled clients on a traffic reset

2026-11-01 08:31:27 +01:00