Mozilla VPN SOCKS Proxy not working with Multi-account Containers

[bdlmf-git]

Describe the bug
Mozilla VPN is supposed to automatically configure a SOCKS proxy that can be used on containers to bypass VPN using socks://localhost:3182 under advanced proxy settings in the Multi-account Container extension. This doesn't work as expected, and containers configured that way result in a "proxy server refusing connections".

VPN version:
2.31.1 (2.31.1~rc20250923174620-static1)

Affected Platforms:
Linux Mint 22.2 Cinnamon

Prerequisites:
<Optional: Any special steps taken not related to the app to trigger the bug>

Steps to reproduce:
Attempt to have a container bypass Mozilla VPN using Multi-account Container extension advanced proxy settings with "socks://localhost:3182"

Expected result:
Any traffic from configured containers should bypass Mozilla VPN

Actual result:
No traffic is allowed as proxy does not seem to be configured/running.

Additional notes:
<Optional: Any Screenshots, Videos, Logs>

┆Issue is synchronized with this Jira Bug

[strseb]

Where did you get that address? Just so to make sure that all docs are correct, because fwiw i don't remember using localhost:3182

You can find the address on how we configure it in the vpn-extension here:
https://github.com/mozilla-extensions/mozilla-vpn-extension/blob/main/src/background/proxyHandler/proxyHandler.js#L43-L51

[bdlmf-git]

Where did you get that address? Just so to make sure that all docs are correct, because fwiw i don't remember using localhost:3182

You can find the address on how we configure it in the vpn-extension here: https://github.com/mozilla-extensions/mozilla-vpn-extension/blob/main/src/background/proxyHandler/proxyHandler.js#L43-L51

Hello, and thanks for taking the time to reply. The extension configuration using localhost:3182 was found here:
https://support.mozilla.org/en-US/kb/use-multi-account-containers-mozilla-vpn

[strseb]

Thanks for flagging! I'm actually not quite sure how that port got there.

I probably should just directly uplift that from the extension to mac, because i doubt Mac would support socks://file://... 🤔