Why Mullvad VPN isn’t connecting

Common causes of Mullvad not connecting

• Outdated app or configuration: An expired root certificate or old configuration files can block startup.
• Network or device limits: Some networks block VPN traffic, or local security software interferes.
• Server or service issues: Mullvad’s servers or the system service on your device may be unavailable.
• Incorrect settings: Forced ciphers, DNS handling, or local network sharing options can prevent a connection.
• Provider blocks or throttling: Some mobile networks throttle or block VPN protocols.

Check your app version and configurations

If Mullvad won’t connect, start with your software versions and files. Upgrading often resolves the problem quickly.

• Update the Mullvad app on your device:
• iOS/Android: update from the App Store or Google Play.
• Desktop (Windows/macOS/Linux): download the latest client from Mullvad’s site.
• Reinstall if updates don’t help:
• Uninstall the app, reboot the device, then reinstall.
• On some systems, you may need to remove a Mullvad config folder or reset system service bindings after uninstall.
• Verify the root certificate:
• Mullvad has referenced replacing expired root certificates. If you see a certificate error, you may be using an old configuration file. Fetch a fresh config from Mullvad and re-import.

When you might need to force a cipher change

Some devices or networks require a specific TLS/SSL cipher. Mullvad help pages suggest enabling Force AES-CBC ciphersuites on your device if your connection fails. How you do this depends on the platform:

• Android (OpenVPN): Look for cipher settings in your VPN profile and select AES-128-CBC or AES-256-CBC if available.
• iOS: Check the app’s VPN protocol settings. If you can’t choose ciphers manually, ensure you’re on a recent app version that supports alternatives.
• Desktop: In the Mullvad client or your OpenVPN profile, choose a CBC cipher if the default isn’t working.

Check network conditions and device-specific settings

Sometimes the issue isn’t Mullvad but the network or device configuration.

• Try a different network:
• Switch from mobile data to Wi-Fi or a different Wi-Fi network.
• If you’re on a corporate or campus network, VPN traffic may be restricted. Ask the admin or try a different network.
• Local firewall or security software:
• Temporarily disable antivirus/firewall to test. If the VPN connects, add Mullvad as an allowed program or exception.
• Local network sharing and IP routing:
• Mullvad app settings may include a “Local network sharing” option. Turn it on if you need LAN resources to route through VPN.
• If your network uses heavy DNS filtering, consider allowing Mullvad’s DNS or using a trusted DNS provider in the app settings.
• Resolve DNS issues:
• Mullvad can behave differently if DNS resolution is blocked or misconfigured. Try using Mullvad’s DNS or switch to a known good DNS resolver (e.g., 1.1.1.1, 8.8.8.8) and reconnect.

Server selection and service status checks

Sometimes the problem is not your setup but availability or routing.

• Try connecting to a different Mullvad server:
• Pick a server in a nearby country to reduce latency and avoid potential regional blocks.
• Check Mullvad service status:
• Mullvad’s blog and help center sometimes publish notices about certificate rollovers or server maintenance. If there’s a known outage or maintenance window, wait and retry later.
• Clean up old sessions:
• On desktop, terminate any existing Mullvad processes and restart the app. On mobile, force stop the app and reopen.
• Reimport configuration:
• If you’re using a manual config file, ensure it matches the latest one from Mullvad. An expired config or mismatched root certificate can prevent connection.

Platform-specific troubleshooting

Different devices require different tweaks. Here are targeted checks for popular platforms.

• Windows/macOS (desktop)

• Ensure the Mullvad service is running and that the VPN client has the necessary permissions (admin rights on Windows, system extensions on macOS when applicable).

• If you see “Mullvad system service can’t be contacted,” remove the Mullvad config folder, disable the service, reboot, then reinstall. Turbo VPN extension for Edge

• Verify that NetworkManager or equivalent services aren’t blocking VPN tunnels. In some setups, you may need to adjust network routing.

• iOS

• Confirm you’re using a compatible iOS version and the latest Mullvad app.

• If forced to use a specific cipher, ensure the app supports it. Some iOS configurations require minimal changes, others need an update.

• If you’re on cellular data, try a known-good Wi-Fi network to rule out carrier blocks. Is Proton VPN slow

• Android

• OpenVPN-based connections may require enabling specific ciphers (AES-CBC) or changing protocol options in the profile.

• Some carriers throttle VPN traffic. If switching networks doesn’t help, test on another SIM or Wi-Fi.

• Linux

• Mullvad on Linux may rely on NetworkManager or OpenVPN/Tunnelblick-like configurations. If you encounter “Connected to Mullvadvpn but no internet,” it can be tied to DNS or resolvconf behavior. How to whitelist websites on NordVPN

• Ensure your resolver configuration matches Mullvad’s expectations or use a compatible static DNS setup.

• Routers

• If you’re running Mullvad on a router, ensure the router firmware supports the VPN protocol you’re using and that port forwarding isn’t blocked by the ISP.

• Restart the router after applying configuration changes and verify the VPN tunnel status from the router’s admin interface.

Quick reference table: common fixes by symptom

When to contact Mullvad support or consult the community

If you’ve exhausted typical steps and Mullvad still won’t connect, gather these details to speed up help:

• Device type and OS version
• Mullvad app version or client version
• VPN protocol and cipher settings used
• Server you attempted to connect to and the outage status if any
• Screenshots or exact error messages (e.g., certificate errors, handshake failures)
• Any recent changes: certificate rollovers, OS updates, or network changes

Ask questions on Mullvad’s help center or community forums:

• Mullvad help center: Open the Mullvad app settings, then click on Preferences and turn on "Local network sharing". In some cases you have to use the IP address to connect instead.
• Reddit discussions about “Mullvad not connecting” can offer real-world fixes and workarounds, such as provider-level blocks or device-specific quirks.
• Recent blog posts can indicate known issues, such as certificate replacements or service maintenance.

Quick diagnostic path you can follow (step-by-step)

• Step 1: Update Mullvad app/client to the latest version on your device.
• Step 2: Reinstall if update doesn’t fix the issue. Re-import fresh configuration if needed.
• Step 3: Check for certificate-related errors and ensure you’re not using an expired root certificate.
• Step 4: Try a different server and note whether the issue is server-specific.
• Step 5: Test on another network (cellular vs Wi-Fi) to rule out provider-level blocks.
• Step 6: Verify DNS settings and try Mullvad DNS if available. Adjust local network sharing if required.
• Step 7: Review device security software and firewall rules. Temporarily disable to test.
• Step 8: If problems persist, collect details and contact Mullvad support or consult the community with a clear description of your setup and steps you’ve tried.

Final recommendation Most Mullvad not connecting issues boil down to outdated configurations, certificate problems, or network-level blocks. Start with updating or reinstalling the client and reimporting a fresh configuration. If the problem remains, systematically test different networks and servers, then check cipher and DNS settings. When in doubt, Mullvad’s help center and community discussions are excellent resources for device-specific quirks and recent changes. If you can, share your exact error messages and the steps you’ve tried when you reach out for support to get a faster resolution.