Repository navigation
Mavi VPN 1.0.1 — CLI reliability and connection fixes
Mavi VPN 1.0.1 improves CLI error reporting, Android connection defaults, and connection lifecycle cleanup across platforms.
What's changed
- CLI error reporting: Linux and Windows
start,stop, andrepairnow return a nonzero exit code when the daemon/service rejects a request, IPC communication fails, or the response does not match the command. Errors retain their diagnostic details and are written to stderr. - Windows scripting: Explicit CLI commands exit without the final "Press Enter" prompt. Unknown commands also return a nonzero exit code. The interactive launch keeps its exit prompt.
- Android default port: New configurations and service start requests without a port now use 10443, matching the Docker Compose default. Previously saved ports are preserved; update an existing profile manually if it still has the old default.
- Android session lifecycle: Stop/restart handling prevents stale workers from changing the replacement session's state or retaining native session handles.
- Windows connections: QUIC attempts to an unresponsive address time out individually, leaving time to try another resolved address within the session deadline. Service lifecycle checks also account for active tasks during shutdown.
- Windows DNS cleanup: Service and uninstaller cleanup remove DNS policies identified as belonging to Mavi VPN, preserving unrelated policies that happen to use the same DNS servers.
- Linux package upgrades: Package removal hooks preserve the daemon during upgrades and stop/disable it only during removal.
- Server IPv6 configuration:
VPN_DISABLE_IPV6=trueexplicitly disables IPv6 tunnel setup and assignments. Windows rejects incomplete IPv6 tunnel configuration instead of silently falling back. - Transport dependencies: Updated branch-tracked
h2,quinn, andh3fork revisions since 1.0.0.
Upgrade notes
Windows requires complete IPv6 tunnel settings from the server. Keep VPN_DISABLE_IPV6=false and configure IPv6 networking and forwarding before connecting Windows clients.
CLI exit codes report failures observed by the command. Linux start acknowledges an asynchronous start request; Linux and Windows stop acknowledge a shutdown request. Check status for the subsequent tunnel state. Windows start retains its existing wait for tunnel readiness. Network repair remains best-effort cleanup inside the daemon/service; a successful IPC reply does not verify every route or DNS operation.
Android's version code increases to 3. Existing saved endpoints are not rewritten.
Full changelog: Changes since 1.0.0.