FAQ

Why does MintFlow need to restart VPN after every configuration change?

MintFlow profiles are not interpreted directly by the running VPN tunnel.

When you activate a profile, MintFlow compiles the text profile into an internal runtime database. That compiled database is what the packet tunnel, DNS server, routing engine, L3 VPN interfaces, L4 proxies, and HTTP engine load while the VPN is running.

Because the running tunnel keeps this compiled runtime state in memory, changing the profile text or app settings does not automatically replace all active routes, DNS policies, proxy chains, VPN peers, and HTTP engine rules in the live tunnel. Restarting VPN is the explicit handoff point: MintFlow stops the old runtime, compiles the current profile again, and starts the tunnel with a consistent database snapshot.

This avoids partially applied configurations, stale routes, stale DNS policy, and mismatches between the UI profile and the runtime networking stack.