Why Mullvad VPN isn’t connecting

Quick checks to rule out obvious causes

• Verify service status: Mullvad’s help center sometimes notes outages or maintenance. A quick check can save you time.
• Confirm account and server: Ensure you’ve generated a valid Mullvad account number and are attempting to connect to a reachable server.
• Restart basics: Restart the Mullvad app or service, and reboot the device. This clears transient state that can block connections.
• Check network type: If you’re on mobile data, try a different network (Wi‑Fi) to see if the issue is provider-related or network routing.
• Force a simple cipher if advised: Some mobile configurations recommend enabling AES-CBC ciphersuites in your device VPN settings.

Platform-specific troubleshooting: iOS and Android

IOS notes

• OpenVPN-based configurations may require specific cipher settings that the device or app version supports.
• If you see “cannot connect” on iOS, try Disconnect → Forget VPN, then re-add Mullvad with a fresh config file.
• Check iOS system VPN settings: Ensure the Mullvad app is allowed to install profiles and that any profile installation didn’t fail.

Android notes

• Android users sometimes need to enable or adjust ciphersuites (such as AES-CBC) in the OpenVPN settings or in the Mullvad app’s preferences.
• If a server isn’t reachable, switch to a different server or protocol (OpenVPN vs WireGuard) and test connectivity.
• Some carriers block or throttle VPN connections. Test on another network (e.g., home Wi‑Fi) to isolate the issue.

Certificate and config issues: expired or incompatible files

• Expired root certificates: Mullvad has published notices about expired certificates that could render the app unable to connect. If you recently updated and still see an issue, it might be caused by an incompatible old configuration file or an expired certificate on the client side.
• Incompatible app version: If you’re using an older Mullvad app, update to the latest version. An outdated app may not trust current certificates or could lack support for new server configurations.
• Re-import configuration: In some setups, removing the existing configuration and importing a fresh configuration from Mullvad’s website resolves issues caused by corrupted config data.
• Reinstall: If other steps fail, uninstall Mullvad completely and reinstall it to reset certificates, keys, and profiles.

Service and system-level checks

• Mullvad system service: If you see a message like “Mullvad system service can’t be contacted,” disable the service, delete the config folder, and restart your device, then re-enable and reconfigure Mullvad.
• Local network sharing: Some app settings require “Local network sharing” or similar features to be on. Turn these on if your device prompts you, and consider using the IP-based connection in some environments.
• DNS and resolvconf: Mullvad’s behavior can depend on resolvconf and DNS settings. If your VPN connects but you have no internet access, it may be related to DNS resolution or NetworkManager interactions on your OS.

Network and firewall influences

• Firewall rules: A firewall on your device or router can block VPN traffic. Ensure ports used by Mullvad (commonly UDP 1194 for OpenVPN, or specific WireGuard ports) aren’t blocked.
• Router VPN passthrough: Some routers require VPN passthrough enabled for UDP/TCP traffic. Check router settings if you’re on a home network.
• ISP and throttling: Some mobile or ISP networks may throttle or block VPN protocols. Testing on a different network helps determine if the issue is provider-side.

Protocol choice: WireGuard vs OpenVPN

• Protocol compatibility: Mullvad supports both WireGuard and OpenVPN. If one protocol fails to connect, try the other. WireGuard is generally faster and simpler, but some networks may fare better with OpenVPN.
• Configuration differences: OpenVPN requires configuration files or app profiles; WireGuard uses a different key/peer configuration. Switching protocols can bypass certain network restrictions.

A practical troubleshooting flow (step-by-step)

1. Check for outages or notices on Mullvad’s help center.
2. Update the Mullvad app to the latest version on your device.
3. Fully restart the device, then retry with a fresh config.
4. Try a different server or switch protocol (WireGuard ↔ OpenVPN).
5. On mobile, test on a different network (cellular vs Wi‑Fi).
6. If “system service can’t be contacted” appears, reset the Mullvad service and delete the local config folder, then reinstall.
7. Verify firewall and router settings to ensure VPN traffic is allowed.
8. If you still can’t connect, export logs from the Mullvad app and contact support with detailed steps and error messages.

A quick comparison: potential fixes by problem type

Common error messages and what they mean

• “Cannot connect” or “Failed to establish VPN tunnel”: Often protocol or certificate issue. Try updating app, re-importing config, or switching protocol.
• “Expired certificate” or “Incompatible certificate”: Update the app or re-download a fresh configuration. Check for notices about root certificates.
• “System service can’t be contacted”: The Mullvad system service on the device may be down or misconfigured. Reset the service and remove then re-add the config.
• “No internet after connect”: DNS resolution or resolvconf misconfiguration. Verify DNS settings or try a different DNS server while connected.

When to contact Mullvad support

• You’ve tried the standard fixes and still can’t connect across multiple devices or networks.
• You’re seeing certificate errors or notices about expired certificates.
• You encounter persistent “system service can’t be contacted” messages after attempting the recommended resets.
• You need help extracting logs or troubleshooting steps specific to your OS version.

Final section: recommendation In most cases, Mullvad connectivity problems resolve with a structured approach: update the app, refresh your configuration, try an alternative protocol, and test on a different network. If you’re seeing certificate-related failures or service contact errors, focus on re-importing fresh configs and resetting the Mullvad service. Keep an eye on Mullvad’s official troubleshooting pages for any announcements about root certificates or expiry issues. If all else fails, reaching out to Mullvad support with a concise report of what you’ve tried (device model, OS version, app version, network type, protocol used, and any error messages) will help them diagnose the problem more quickly.