Procedure for application
1
Save the draft.
Check blocks, connections, node assignments, and route parameters. Saving the canvas doesn’t, by itself, unfold the configuration.
2
Click "Apply Changes"
The panel compiles the draft and opens the dialogue of the plan. Eliminate compilation errors and criticisms of the linker.
3
Check the impact
Examine the affected nodes, Remnawave resources, pools, DNS and the required subscription settings. Only confirm the changes shown.
4
Apply the plan viewed
The panel will check the plan against the revision. If the route or dependency has changed, you need to assemble and review the new plan.
5
Check the result.
Wait for the result, check the active version and run a health check, and a partial result requires diagnosis, even if the version has already been used.
What can stop the application
- Topology errors, conflicting ports, incompatible parameters, and liner criticisms.
- Changing the draft or semantic snapshot of the pool after viewing the plan.
- Need to prepare services, GeoAssets or other dependencies on affected nodes.
- Confirmation-requiring change to the Remnawave JSON subscription setting for balancing mode.
- The dialogue shows problem domains and a separate confirmation for intentional application before DNS is ready.
Infrastructure checks prior to change
It’s not just the graph fields that are checked before application. Depending on the configuration, the plan may stop because of a port that is occupied by someone else’s process, a missing TLS certificate, an unsuitable REALITY target, an unworkable SelfSteal origin, agent limitations, Remnawave or firewall. An alien listener at the desired port does not automatically stop for Flow. Disassemble the owner and select a free port or prepare a compatible scheme. The missing certificate cannot be replaced by a fictitious successful status. After application, the availability of the path through the firewall and running runtime are confirmed separately. Failure to check may leave a partial result and require recovery. For the external proxy and WARP, the specific route branch is taken into account: checking the adjacent branch does not prove that the output used is working.Enforcement
The switch is available in the dialog.Application is forced. It requires explicit risk acceptance and allows you to continue if the listeners, firewall or REALITY target are unconfirmed.No communication with the agent does not become a confirmation of serviceability: traffic may not earn until the node is restored and re-used. Configuration errors, an occupied port conflict, unusable mandatory TLS materials, and an outdated plan continue to block application.The coercive regime does not cancel the audit audit or turn an arbitrary error into a success. Once launched, check the missed checks report, Remnawave status and nodes, then the client connection. If you fail, restore the dependencies and apply a fresh plan, or use the rollback described below. This is a separate confirmation from application to DNS readiness.How to read the state
The error of a new attempt does not necessarily mean that the previous route has stopped, and the reverse is that “Applied” status does not guarantee a healthy route. If used incompletely, check the report of the actions actually performed and the state of the nodes.
The checks and analytics of the running Flow rely on the image used, and the blocks added only to the draft do not become verified sections of the live route.
Versions and pools
The application creates an immutable, applied version. In the Version tab, you can see the draft, the versions used, and the available import or rollback pictures. To roll back, you need a saved image: the Flow story does not replace the backup copy of. Used Flow saves a snapshot of used pools. Saving a new pool lineup, route, or policy updates the directory; running Flow stays on the same shot until explicit application. After changing the pool, reassemble the plan of each affected Flow or use the available managed application procedure with influence viewing.Rollback
There are several different operations:
Select the inactive manual rollback version in the Version tab, confirm the recovery, check the canvas and reapply. Until the application is started, uploading the image to the draft does not change the infrastructure.
