Remnawave Admin 5.1.0

September 26, 2026 · GitHub release · discussion in Telegram

A release about soft measures against violators: warn first, and block only if that did not help. Automations learned to delay a step by hours and re-check the case before acting, warning templates got separate texts for Telegram and email, and the email now reaches customers without Telegram too. Plus fixes for scheduled backups and reg.ru in the DNS manager.

Before upgrading

Read the Important section: the customer warning is now also sent after an automatic action, and the channels of warning templates became strict.

✨ New

Warn first, act later

A chain step in a violation rule (the “Violation detected” and “Torrent detected” events) can be delayed: the “Run after N h after the trigger” field, up to 30 days; delays along the chain do not decrease. The typical scenario is “warn the customer → limit speed after 12 hours → block after a day”.

A waiting step is stored in the database and survives a restart. Before running, the case is re-checked, and the step is skipped if the rule was turned off, the violation was annulled or already resolved, the customer is no longer in the panel, the action is already in place (a delayed one-day block will not unblock someone blocked forever, and a limit will not override a manual one), the customer is whitelisted or wrote to support after the trigger — this check can be turned off for the step. If the warning in the chain did not reach the customer, the delayed action is not applied at all, and a repeated trigger for the same customer does not add a second one while the first is waiting.

The automations log shows what is waiting and when, what ran and why a step was skipped; a test run shows the step delays. Idea by @fesevu (#289). More in Warn first, act later.

Action on trial-abuse accomplices too

The “Block user”, “Disable user” and “Limit speed” actions in violation rules have the “Also trial-abuse accomplices on the same HWID” checkbox — in the main action and in a chain step, including a delayed one. The list comes from the analyzer: other subscriptions with a live trial on the same device. This way the detector's built-in auto-block is replaced with a soft chain “warn → block after N hours”, and the bundle still does not keep working. The action does not touch customers who are already blocked, limited or whitelisted; the outcome for accomplices is in the log.

External support contact

The “customer wrote to support” check of a delayed step looks at Bedolaga tickets, and now at any support of your own too: POST /api/v3/support-events — a bot or helpdesk reports a contact, and the waiting step for the customer's violation will be skipped, leaving the decision to an operator. The customer is found by user_uuid, telegram_id, email or username; repeating an event with the same Idempotency-Key is safe. It needs an API key with the enforcement:support scope, which an admin with the violations:resolve permission can grant. Thanks to @fesevu (#291).

Channels and editors in warning templates

A template has two equal channels — Telegram and Email: the warning goes strictly through the checked ones, and at least one always stays on. The channels have separate texts; the Telegram / Email switch in the template changes the editor.

• Telegram — HTML with highlighting, formatting buttons and a preview styled as a message. The markup is checked as you type and on save: Telegram rejects the whole message because of one extra tag or a bare &. Special characters are fixed with one button.
• Email — the subject and the email's own HTML with a preview. Empty — the email is built from the Telegram text; the “Start from the Telegram text” button puts that layout into the editor.

More in Client warnings.

🔧 Improvements

• The “Warn” button in the web violation card — shows whether the customer was already warned, explains a refusal in words, ignores repeated clicks while sending, and sending checks that the violator is visible to the operator — thanks to @fesevu (#285)
• The email arrives even without the bot — if the Bedolaga bot did not deliver a warning (not connected, did not find the customer, lacks the required endpoint), the email goes out through the built-in mail server to the customer's address from the admin database; if the bot delivered only Telegram while the template asks for an email too, the admin sends it
• Faster on a bad link — the connection to the panel is kept for a minute instead of 5 seconds: on a server with packet loss, requests to the panel and bot button replies no longer wait for a new connection every time
• Documentation — Anti-abuse describes warning channels, the delayed action and the soft auto-block recipe; the API reference covers support events

🐛 Fixes

• fixed a bug (scheduled backups did not get into the backup log, and the missed-backup check believed there were none) — thanks to @latham5656 (#282)
• fixed a bug (reg.ru in the DNS manager did not connect — “Command domain/get_list not found”) — thanks to @Ivanomsk (#284)
• fixed a bug (a customer without Telegram got no warning even with a known email) — thanks to @fesevu (#286)
• fixed a bug (the “warn the customer on action” setting did not apply to automatic blocking and speed limiting) — thanks to @fesevu (#287)
• fixed a bug (clearing the duration of a chain step in the automation builder wiped the step's other settings)

⚠️ Important

• Take a database backup before upgrading. Migrations run on their own at first start, and rolling back to 5.0.0.1 is only possible by restoring from the backup.
• Warning after an automatic action. The “Violations: warn the customer on action” setting now applies not only to operator actions but also to automatic blocking and speed limiting by score. It is on by default: if customers should not be written to after an automatic action, turn it off.
• Template channels became strict. Previously Telegram was always sent, and “also by email” only added an email; now the warning goes only through the checked channels. On upgrade, templates have Telegram checked, and Email where “also by email” was on. A customer without Telegram gets a warning only if the template has Email checked.
• Bedolaga. Telegram warnings still require a bot with the changes from #3270, which has not been accepted upstream yet. Emails now go out without it — through the built-in mail server, if it is set up.

📦 Upgrade

docker compose pull
docker compose up -d

Node agents do not need updating. Details are in Upgrade.