Portal cannot sign in
Check that the control plane URL is configured and uses HTTPS when the site is HTTPS. Mixed content will block cookie auth in browsers.
Support
RavenVPN is designed for one-click protection, but the internet is messy. Use this guide to fix the most common setup issues and generate a clean support snapshot when you need help.
Fast path
RecommendedQuick fixes that match the current architecture.
Check that the control plane URL is configured and uses HTTPS when the site is HTTPS. Mixed content will block cookie auth in browsers.
The desktop app must be open and polling for approval. After you approve the code, return to RavenVPN Desktop to finish provisioning.
Verify WireGuard is installed, then check the tunnel status and endpoint candidate list. If the handshake fails, try another region.
Kill switch is designed to block traffic when the tunnel is down. If you use advanced AllowedIPs overrides the semantics may change.
Invite-based onboarding and centralized policy.
If you received an invite token/link, sign in first and then open Portal > Teams to accept it.
In Teams mode, routing policy is managed at the organization level and distributed to all member devices when they refresh config.
For zero-trust overlay deployments, define private_routes CIDR allowlists and then sync AllowedIPs so member devices route only private access traffic through RavenVPN.
Overlay mode requires at least one connector edge running inside your private network. Clients will automatically prefer connectors when AllowedIPs is not full tunnel.
Teams checkout requires an organization name and creates an organization owned by the buyer account. Use the billing portal for upgrades and invoices.
When you contact support, include a sanitized snapshot instead of screenshots.
Open Status diagnostics and use the Copy support bundle button. It excludes tokens and focuses on configuration and connectivity.
In RavenVPN Desktop, export a diagnostics bundle from the Diagnostics view. It writes a sanitized JSON file to Downloads for sharing.
Your email (or customer ID), the region you selected, and the approximate time of failure. Do not send secrets or raw tokens over chat.
Keep the fastest path nearby.