A laptop displays a colorful Firefox browser home page with search, app shortcuts, and security controls.
Firefox 160 has an odd bug: it can blame a VPN you aren't using. Some users on the new release see a "Couldn't connect to VPN" error page during ordinary connection drops, even though Firefox's built-in VPN is switched off. Mozilla's product manager for the feature says engineers think the error page is pointing at the wrong cause. The planned fix is in Firefox 162, not the next point release.

Here's what is confirmed, what isn't, and what Windows users can do in the meantime.

A laptop displays a colorful Firefox browser home page with search, app shortcuts, and security controls. What users are seeing​

The first report came from a Windows 11 user on Firefox 160.0 in Reddit's Firefox community. YouTube creator BrenTech then drew more attention to it. According to PiunikaWeb, the user noted that Steam and other browsers worked fine, while Firefox kept flashing the VPN error with the toolbar toggle completely off.

Other reports add more detail:

  • The Polish site ITHardware says that when the user tries to switch the VPN on manually, the browser says the computer has no internet connection, while other browsers and apps, including Steam, work without any problems.
  • Indonesian outlet WinPoin, also citing the Reddit thread, says restarting Firefox can clear the notice for a while, but the error comes back after the browser has been in use for some time.
  • Other commenters said waiting a few seconds or restarting the browser cleared it. Nobody has tested these workarounds properly, and they don't always work.

In short, the network is usually fine. Firefox gets a normal connection hiccup and labels it as a VPN failure.

Section summary: Firefox 160 users, including at least one on Windows 11, see a VPN error page while the built-in VPN is off and other apps stay online.

What Mozilla has said​

When PiunikaWeb went back to the thread, it found a reply from a Mozilla employee who is the product manager for the built-in VPN. The product manager said "our engineers think the error page may be blaming the VPN for connection problems that aren't coming from it, which fits what you're describing."

On the fix, the team plans on "shipping a change in Firefox 162 that we think will fix it." Brazilian outlet TecStudio notes that Mozilla plans to include a change in Firefox 162 to correct the warning but has not given a specific date for the update.

Two caveats matter here:

  1. The product manager said "we think." That is a working theory and a planned change, not a confirmed root cause.
  2. Nothing shows that every report in the thread has the same cause. Some users could also have proxies, extensions or system VPNs involved.

The diagnostic details Mozilla asked for​

Until the fix ships, the product manager asked affected users to reply with diagnostic information. If you see the bug, collecting this before a bug report or forum post is a good idea:

  • Operating system and Firefox version (for example, Windows 11 and Firefox 160.0).
  • Proxy setup: whether Firefox uses a proxy set in Firefox's own settings, in Windows system settings or by an extension.
  • The VPN toolbar button's state while the error page is on screen: off, on, or site excluded/included. The product manager also asked for a cropped screenshot of the button and its open panel.
  • Five preference values (true or false), found by typing about:config in the address bar, accepting the warning and searching for each one:
    • browser.ipProtection.userEnabled
    • browser.ipProtection.features.siteInclusions
    • browser.ipProtection.autoRestoreEnabled
    • browser.ipProtection.autoStartEnabled
    • browser.ipProtection.autoStartPrivateEnabled

The product manager said these values contain no personal details. Mozilla asked people to read these settings, not change them. This is evidence gathering, not a fix.

A workaround, with a warning​

Some outlets have described a stronger option: turning the built-in VPN off completely. The Iranian site Technoc describes it as a suggested temporary solution that has not yet been tested. It involves opening about:config and setting browser.ipProtection.enabled to false, which disables the VPN feature entirely.

Mozilla did not suggest this. Nobody has shown that it stops the false error, and it removes a feature you might want later. If you try it:

  1. Note the original value first.
  2. Change one setting at a time.
  3. Set it back to true if nothing improves, or once Firefox 162 arrives.

IT admins should be careful about pushing this to managed machines on the strength of a few forum posts.

Don't confuse this with other VPN error fixes​

There are several Firefox VPN error fixes in Mozilla's records, and they are easy to mix up. Two public Bugzilla entries look related but are not this bug:

Bugzilla entryWhat it addressesStatus
Bug 2091550Shows a generic error instead of a "VPN unavailable in your region" messageVerified on Nightly 162 and Beta 161.0b2; also approved for the 160 release branch
Bug 2022484"Couldn't connect to VPN" shown when the VPN is turned off during its "Connecting" stateFixed and verified in Firefox 150
The bug in this storyVPN error shown during ordinary connection drops while the VPN is offFix planned for Firefox 162, per Mozilla's product manager

According to the Bugzilla record, bug 2091550 followed public backlash over region-unavailability messages. Its risk note says it changes which error appears without changing how errors are detected. Its test involved a proxy pretending to be in China. That is a different case from a Windows 11 PC on a home connection that briefly drops out.

Bug 2022484 matches this story's error text, but its trigger was clicking the VPN off mid-connection, and it was closed back in Firefox 150. So a "Couldn't connect to VPN" bug was already fixed eight months ago, and a different trigger has now produced the same message.

Section summary: Mozilla has three separate VPN error-message problems on record. Only the planned Firefox 162 change is aimed at this one.

Timing and context​

Mozilla's release notes show Firefox 160.0 reached the Release channel on November 10, 2026. Those notes list Picture-in-Picture speed controls, a Mini Window feature, and changes to Metal-based WebGL on macOS. They don't mention this VPN error, and Mozilla hasn't published a finding that 160 introduced it. The link to 160 comes from users' version reports.

The built-in VPN is fairly new. ITHardware reports it appeared in Firefox version 149 and offers a free data allowance, with paid plans available after it runs out. PiunikaWeb also points out the bad timing: the bug appeared days after Mozilla made the free VPN unlimited through January for holiday travelers. A browser that wrongly blames a feature you've never used is a poor first impression for that feature.

Is your privacy at risk?​

PiunikaWeb argues that since Firefox is only mislabeling normal connection hiccups, your privacy is not actually at risk. That is probably true if Mozilla's theory is right and the VPN really was off. But the public discussion doesn't show whether protection was active during any of these incidents, or whether outside VPNs, proxies or extensions were involved. "Probably fine" is a fair reading. "Proven safe" goes too far.

What to do on Windows​

  1. Check whether you're actually offline. If Edge, Chrome, Steam or other apps load fine, the VPN error is probably wrong.
  2. Check the VPN button in the toolbar. If it says off, the error message alone doesn't prove the VPN caused anything.
  3. Check for proxies. Look in Windows Settings > Network & internet > Proxy, in Firefox's connection settings, and in any proxy extensions.
  4. Reload or restart Firefox. Some users say this helps for a while.
  5. Report it. Use the diagnostic list above and send it to Mozilla.
  6. Watch for Firefox 162. That's the release where Mozilla expects to fix this.

Bottom line​

Mozilla has accepted that Firefox 160 can show the wrong error, with the built-in VPN taking the blame for ordinary network drops. The fix is planned, not shipped. Until Firefox 162 arrives, trust your other apps more than the error page, and send Mozilla the diagnostics it asked for.

 

References

  1. Mozilla acknowledges bug causing Firefox to blame disabled VPN for connection drops - PiunikaWeb PiunikaWeb 2026-11-19T07:08:19+00:00
  2. 2022484 - “Couldn’t connect to VPN” error displayed if VPN is turned off while in Connecting state bugzilla.mozilla.org
  3. 2091550 - Use generic error for VPN_UNAVAILABLE bugzilla.mozilla.org