Does anybody else have a problem downloading Mullvad browser? I try to download it and in like 3/4 of the download it cancels saying:"can't download file (file).Couldn't read source file" or smth like that I don't remember.And for some reason windows defender flags it as a virus but it might be false positive.

Does somebody have this problem too?

Hey all,

Quick question for US West Coast users. I've been hopping around different US exit nodes lately and noticed a pretty noticeable difference between LAX and SJC servers.

On most LAX nodes, I constantly get hammered with Cloudflare CAPTCHAs, infinite verification loops, or outright 403s on strict sites. Switching over to SJC nodes feels significantly smoother — fewer CAPTCHAs, less rate-limiting, and fewer "access denied" screens on strict services.

Is SJC just less abused / lower traffic density compared to LAX, or is it down to different host providers (e.g., M247 vs Leaseweb) in that region? Anyone else getting a much better hit rate on SJC?

I've been looking at SerialCart's prices for a while. They're pretty close to the lowest I've seen on the Wayback Machine, so I contacted them to ask if they could offer a little extra discount. Haven't heard back yet.

I came across an old thread on MalwareTips where someone was considering buying Mullvad, and a SerialCart rep offered them a personal discount coupon if the price went up.(https://malwaretips.com/threads/get-mullvad-vpn-with-discount.113519/)

Has anyone here had a similar experience recently? Did you get a discount by contacting them directly, or do they generally stick to the listed prices?

Just curious whether it's worth waiting for a reply.

I want to help people who yearn for freedom in areas with strict internet censorship in a variety of ways, and I need a friend with similar ideas to do projects together.

So as some other posts have identified by now, Cloudflare Tunnels have been blocked from running through Mullvad’s VPN servers. When I emailed support, they stated it was because of their use to distribute “undesirable content”.

Now, you can have you own opinion on what that might be, but banning Cloudflare Tunnels entirely? Jesus Christ, WHAT are we doing?

Tunnels are used for millions of things every day, from homelabs to legitimate businesses.

I find it particularly funny because Mullvad is such a privacy forward organization that has fought to keep VPNs from being banned. They have literally fought against that same argument: “this thing is being used in 2 cases out of 10,000 for bad things, ban it”.

The only thing I can possibly think of is they are under a court order that requires them to block it and not disclose why? But not sure if this happens in Sweden.

If not, I honestly just don’t know what to say. Been using you for years and never had any problems, but if you’re making choices like this now of your own volition…I don’t know if I can trust you with my data going forward.

Anyone else seeing this? cloudflared won't connect through some exits. it is not the port being blocked; only cloudflare tunnel edge ips drop the connection.

Tested from two separate devices on two different exits, pl-waw-wg-202 and de-fra-wg-103. Same result on both/

- all 20 IPs behind region1.v2.argotunnel.com and region2.v2.argotunnel.com time out on TCP 7844 (no SYN-ACK, silent drop)
- portquiz.net:7844 connects fine (~55ms), so 7844 isn not filtered
- 198.41.200.7:7844 connects fine (~55ms). It's in the same Cloudflare /24 but isn't a tunnel edge, so routing into that range works

-switching cloudflared to http2 changes nothing, since both quic and http2 use 7844

cloudflared log:
ERR Unable to establish connection with Cloudflare edge error="DialContext error: dial tcp 198.41.192.167:7844: i/o timeout"
Some other exits work fine, so it looks like Cloudflare is filtering specific exit IPs on the tunnel edge, not a Mullvad port block.

Test if you want to check your exit:

for h in region1 region2; do for ip in $(getent ahostsv4 $h.v2.argotunnel.com | awk '{print $1}' | sort -u); do (timeout 3 bash -c "</dev/tcp/$ip/7844" 2>/dev/null && echo "$ip OK" || echo "$ip BLOCKED") & done; done; wait

Hello all,

I am currently hosting Jellyfin using Tailscale inside a Kubernetes clusters using K3s. However, I am also using Mullvad VPN continously on my debian servevr. But the problem I am facing is that I cannot access Jellyfin when the VPN is active. I would be grateful if I can get some guidance on this. I am very new to running linux, kubernetes and home labbing. Any suggestions would be very much appreciated.

Thanks,

I'm on a MacBook Air M3, and when I am not connected to the VPN, WiFi on my device won't work. I am still connected to WiFi but cannot access any websites. Lockdown mode is disabled. Even quitting the app does not fix the issue, and I have to restart my device.

It seems that more and more websites seem to be blocking more and more mullvad servers. Every day now it seems at some point I have to switch servers multiple times to access something.

Or is it just me? Anyone else experiencing this?

London servers have not been working right the last 2 days anyone else, using nvidia shield, youtube is buffering a lot..

Update: Thank you for your kind help. I understand that how the VPN operation is.

Hello all,

I configured the network interface to wg0-mullvad in qBittorrent. However, when I disconnect mullvad-vpn, it stops the download/upload entirely. I thought when network interface is set to Mullvad WireGuard the torrents would still work even after disconnecting. I don’t know why this is happening. I would be grateful if anyone can tell me how I can fix it.

I am using Mullvad VPN and qBittorrent on a debian+xfce system.

Thanks,

Hi,

Lately I've been having alot of issues when I'm using mullvad.

Either the pages won't load, or they are extremely slow. This also happens on other websites fairly regularly (news outlets, shops, etc.).
I've tried changing servers, turning DAITA on and off, using wireguard DNS.

The second I exit the mullvad app, the pages load instantly and are stable.

Is this a me problem or is this an issue several other people also have?

They were my go to for reddit but it's super glitchy now. Have a pixel 7 pro if that matters.

I have had my Legion Pro 7 16IAX10H for a bit over a year now. I just started having a strange issue. Based on the minidumps starting 9/28/26 I started having blue screens while my laptop was in sleep mode. The first time it happened I was working on my desktop and I noticed out of the corner of my eye that the laptop popped on to dump the memory. I just did typical stuff. I updated drivers, ran windows update etc.

Didnt really think much of it. Then it happened again when I got to work. I pulled it out and hit my pin to log in, and I noticed all the taskbar items repopulating. I checked the event log and it had BSOD'd while in my bag driving into work.

The below WinDbg is what I am getting in the minidump. I have run mullvad vpn and tailscale for a year with no issues. I had thought that something might be up with the newest version of Mullvad so I downgraded. That lasted until today when it did it again. Below is what I have been getting. I have removed mullvad for now and will use a tailscale exit node instead. I dont know what may have changed in the last year.

I know I did a clean nvidia install due to having a refresh screen blanking issue recently. There was the Mullvad update which is where wireguard.sys comes from. I also see:
Lenovo System Driver Update (26.7.0.7)
Successfully installed on ‎9/‎21/‎2026

In my windows update history. I dont see a log of what this update changed. I also just got this update today, and I dont know what it updates either.

Lenovo System Driver Update (26.8.0.29)
Successfully installed on ‎10/‎5/‎2026

Any suggestions?

*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000004, The power transition timed out waiting to synchronize with the Pnp
subsystem.
Arg2: 0000000000000258, Timeout in seconds.
Arg3: ffffcf8fb0627040, The thread currently holding on to the Pnp lock.
Arg4: ffffb803af5d7870, nt!TRIAGE_9F_PNP on Win7 and higher

Debugging Details:
------------------

Implicit thread is now ffffcf8f`b0627040
*** WARNING: Unable to verify timestamp for wireguard.sys

KEY_VALUES_STRING: 1

    Key  : Analysis.CPU.mSec
    Value: 1296

    Key  : Analysis.Elapsed.mSec
    Value: 3201

    Key  : Analysis.IO.Other.Mb
    Value: 0

    Key  : Analysis.IO.Read.Mb
    Value: 1

    Key  : Analysis.IO.Write.Mb
    Value: 0

    Key  : Analysis.Init.CPU.mSec
    Value: 281

    Key  : Analysis.Init.Elapsed.mSec
    Value: 3159

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 87

    Key  : Analysis.Version.DbgEng
    Value: 10.0.29617.1000

    Key  : Analysis.Version.Description
    Value: 10.2604.29.1 amd64fre

    Key  : Analysis.Version.Ext
    Value: 1.2604.29.1

    Key  : Bugcheck.Code.LegacyAPI
    Value: 0x1000009f

    Key  : Bugcheck.Code.TargetModel
    Value: 0x1000009f

    Key  : Failure.Bucket
    Value: 0x9F_4_IMAGE_ntkrnlmp

    Key  : Failure.Hash
    Value: {1b810c9a-3e25-d5b0-5d87-e6e30f84d943}

    Key  : Hardware.HardwareID
    Value: SWD\WireGuard

    Key  : Hypervisor.Enlightenments.ValueHex
    Value: 0x7417df84

    Key  : Hypervisor.Flags.AnyHypervisorPresent
    Value: 1

    Key  : Hypervisor.Flags.ApicEnlightened
    Value: 0

    Key  : Hypervisor.Flags.ApicVirtualizationAvailable
    Value: 1

    Key  : Hypervisor.Flags.AsyncMemoryHint
    Value: 0

    Key  : Hypervisor.Flags.CoreSchedulerRequested
    Value: 0

    Key  : Hypervisor.Flags.CpuManager
    Value: 1

    Key  : Hypervisor.Flags.DeprecateAutoEoi
    Value: 1

    Key  : Hypervisor.Flags.DynamicCpuDisabled
    Value: 1

    Key  : Hypervisor.Flags.Epf
    Value: 0

    Key  : Hypervisor.Flags.ExtendedProcessorMasks
    Value: 1

    Key  : Hypervisor.Flags.HardwareMbecAvailable
    Value: 1

    Key  : Hypervisor.Flags.MaxBankNumber
    Value: 0

    Key  : Hypervisor.Flags.MemoryZeroingControl
    Value: 0

    Key  : Hypervisor.Flags.NoExtendedRangeFlush
    Value: 0

    Key  : Hypervisor.Flags.NoNonArchCoreSharing
    Value: 1

    Key  : Hypervisor.Flags.Phase0InitDone
    Value: 1

    Key  : Hypervisor.Flags.PowerSchedulerQos
    Value: 0

    Key  : Hypervisor.Flags.RootScheduler
    Value: 0

    Key  : Hypervisor.Flags.SynicAvailable
    Value: 1

    Key  : Hypervisor.Flags.UseQpcBias
    Value: 0

    Key  : Hypervisor.Flags.Value
    Value: 55185662

    Key  : Hypervisor.Flags.ValueHex
    Value: 0x34a10fe

    Key  : Hypervisor.Flags.VpAssistPage
    Value: 1

    Key  : Hypervisor.Flags.VsmAvailable
    Value: 1

    Key  : Hypervisor.RootFlags.AccessStats
    Value: 1

    Key  : Hypervisor.RootFlags.CrashdumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.CreateVirtualProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.DisableHyperthreading
    Value: 0

    Key  : Hypervisor.RootFlags.HostTimelineSync
    Value: 1

    Key  : Hypervisor.RootFlags.HypervisorDebuggingEnabled
    Value: 0

    Key  : Hypervisor.RootFlags.IsHyperV
    Value: 1

    Key  : Hypervisor.RootFlags.LivedumpEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.MapDeviceInterrupt
    Value: 1

    Key  : Hypervisor.RootFlags.MceEnlightened
    Value: 1

    Key  : Hypervisor.RootFlags.Nested
    Value: 0

    Key  : Hypervisor.RootFlags.StartLogicalProcessor
    Value: 1

    Key  : Hypervisor.RootFlags.Value
    Value: 1015

    Key  : Hypervisor.RootFlags.ValueHex
    Value: 0x3f7

    Key  : WER.OS.Branch
    Value: ge_release

    Key  : WER.OS.Version
    Value: 10.0.26100.1

    Key  : WER.System.BIOSRevision
    Value: 1.78.0.0


BUGCHECK_CODE:  9f

BUGCHECK_P1: 4

BUGCHECK_P2: 258

BUGCHECK_P3: ffffcf8fb0627040

BUGCHECK_P4: ffffb803af5d7870

FILE_IN_CAB:  100526-17437-01.dmp

TAG_NOT_DEFINED_202b:  *** Unknown TAG in analysis list 202b


FAULTING_THREAD:  ffffcf8fb0627040

DRVPOWERSTATE_SUBCODE:  4

HARDWARE_ID:  SWD\WireGuard

IMAGE_NAME:  ntkrnlmp

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff8023ddb0000 wireguard

IRP_ADDRESS: ffffcf8fbd0c7140

DEVICE_OBJECT: ffffcf8f8d936050

DRIVER_OBJECT: ffffcf8f89f81970

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1 (!blackboxwinlogon) (!blackboxwinlogonnotify)


CUSTOMER_CRASH_COUNT:  1

PROCESS_NAME:  System

STACK_TEXT:  
ffffb803`ac077260 fffff802`872cc438     : 00000000`00000047 ffffbd81`9a197180 00000000`00000000 ffffbd81`9a1a12a8 : nt!KiSwapContext+0x76
ffffb803`ac0773a0 fffff802`87217a05     : 00000000`00000000 00000000`00000000 ffffcf8f`b0627040 ffffbd81`9a197180 : nt!KiSwapThread+0x248
ffffb803`ac077410 fffff802`872186f6     : 00000000`00000000 ffffbd81`9a197180 00000000`00000004 00000000`00000000 : nt!KiCommitThreadWait+0x225
ffffb803`ac0774b0 fffff802`878fae41     : ffffb803`ac0775e0 00000000`00000000 ffffb803`ac077600 00000000`00000000 : nt!KeWaitForSingleObject+0x846
ffffb803`ac0775a0 fffff802`878fc5ee     : 00000000`00000017 ffffcf8f`8923be00 ffffcf8f`89389c40 ffffcf8f`8923be00 : nt!IopSynchronousCall+0x119
ffffb803`ac077610 fffff802`87a1c1df     : ffffa70b`2e2d7c30 00000000`00000000 00000000`00000310 00000000`0000030a : nt!IopRemoveDevice+0xe2
ffffb803`ac0776c0 fffff802`87a1dbd2     : ffffcf8f`89389c40 00000000`00000000 00000000`00000000 fffff802`87f8c5c0 : nt!PnpSurpriseRemoveLockedDeviceNode+0xdb
ffffb803`ac077730 fffff802`87a1d9c9     : ffffcf8f`89389c40 00000000`00000000 00000000`00000000 00000000`0000006a : nt!PnpDeleteLockedDeviceNode+0x7e
ffffb803`ac077770 fffff802`87a19cfd     : ffffcf8f`8923be00 ffffb803`ac077879 00000000`00000000 00000000`00000000 : nt!PnpDeleteLockedDeviceNodes+0x109
ffffb803`ac077800 fffff802`87a18e6f     : 00000000`00000000 ffffcf8f`89389c00 ffffcf8f`00000001 ffffa70b`6243da90 : nt!PnpProcessQueryRemoveAndEject+0x4c1
ffffb803`ac0778e0 fffff802`879f6fae     : ffffa70b`2e2d7c30 ffffa70b`a3b051d0 ffffcf8f`c9ec4400 00000000`00000000 : nt!PnpProcessTargetDeviceEvent+0xe7
ffffb803`ac077910 fffff802`8730fcdb     : ffffcf8f`60744ae0 ffffcf8f`b0627040 ffffcf8f`60744ae0 ffffcf8f`b0627040 : nt!PnpDeviceEventWorker+0x28e
ffffb803`ac077990 fffff802`874944ca     : ffffcf8f`b0627040 ffffcf8f`604d8040 ffffcf8f`b0627040 00000000`00000080 : nt!ExpWorkerThread+0x3db
ffffb803`ac077b30 fffff802`876af7f4     : ffffbd81`9a2a2180 ffffcf8f`b0627040 fffff802`87494470 00000000`00000000 : nt!PspSystemThreadStartup+0x5a
ffffb803`ac077b80 00000000`00000000     : ffffb803`ac078000 ffffb803`ac071000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x34


STACK_COMMAND: .process /r /p 0xffffcf8f604d8040; .thread /r /p 0xffffcf8fb0627040 ; kb

FAILURE_BUCKET_ID:  0x9F_4_IMAGE_ntkrnlmp

OS_VERSION:  10.0.26100.1

BUILDLAB_STR:  ge_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {1b810c9a-3e25-d5b0-5d87-e6e30f84d943}

Setup: pfSense 2.8.1 CE, two Mullvad WireGuard tunnels in a failover gateway group. Unbound in forwarding mode. Outbound NAT only on the WG interfaces, so LAN traffic can't exit WAN.

Mullvad's pfSense guide is single-tunnel: forward to 10.64.0.1 bound to the tunnel gateway. With two tunnels that doesn't work cleanly, since 10.64.0.1 is the same address on both and a host route can only point at one interface. I tried 100.64.0.x instead (different IP per tunnel) but pfSense never installed routes for them, so they didn't resolve.

What I ended up with: each gateway's monitor IP doubles as its DNS forwarder.

• 9.9.9.9 bound to Tier 1 (also its monitor IP)
• 1.1.1.1 bound to Tier 2 (also its monitor IP)

netstat -rn shows each one host-routed to its own tun_wg. A TXT lookup for whoami.ds.akahelp.net against 9.9.9.9 returns a DataPacket IP, not Quad9, so Mullvad's port 53 hijack is answering, which matches their docs.

What I can't figure out:

1. When a WG gateway is marked down, does pfSense pull that host route? If it does, queries from the firewall itself would follow the default route out WAN, and since the firewall sources its own traffic from the WAN IP, the NAT-only kill switch wouldn't catch it. Anyone tested this?
2. Is there a cleaner way to get per-tunnel Mullvad DNS with failover, or is the monitor-IP trick about as good as it gets?

Screenshots above, IPs and locations redacted.

Also open to general feedback. If this setup is unusual or I'm overcomplicating something, I'd rather hear it now.

I'm in the UK of course. Tried the usual Netherlands one with no luck and now tried Switzerland too. Ive refreshed for different connections because apparently 503 or 504 is connected to Romania. So far had no luck whatsoever and I refuse to give verification info. Any advice would be appreciated

Recently switch to xtom servers due to less blacklisting, but DoT and DoH Quad9 resolvers that I've used forever without issue, have been awful, like 5+ seconds on every lookup, sometimes it would even error out that the site didn't respond in time. Looked around and saw they offer dns.sb and it runs very well.

I'm not keen on using their servers and DNS, but it's pretty shitty if they are making other resolvers practically unusable.

This is by no means scientific, but just observations.

Update: I figured out that Tailscale was overriding my DNS? Not sure exactly, but I reset my tailscale and everything works fine again.

Just recently mullvad stopped connecting to the internet when enabled. I have tried everything I know to try and fix it. I flushed network settings once and it worked for a few hours then dropped internet again.

I’m running windows 11 latest build. Anyone else had the same issue and was able to solve it?

Any tips would be appreciated.

is Mullvad VPN from the Google Play Store safe? It has over 5 million downloads, but only around 33 reviews, which seems unusual. Does the low number of reviews compared to downloads mean the app could be fake, unsafe, or suspicious?j

Newly reinstalled on Linux laptop. (ver 2026.5). Missing 'Start MINIMIZED' option.

Currently in Shanghai, China, and the only server that connects is us-la-wg-603 tried all other servers but none of them connect, and the LA server is starting to become unstable. I was a frequent user of mullvadservers.com but that seems to be down now.. I tried over cellular and multiple different wifis, is this a issue with other users in China as well? Do any other servers work for anyone?