Table of contents

The team at MobileProxy.space has updated their signature Mobile Proxy Manager browser extension to version 3.1. This release continues the focus on stability, security, and user-friendliness: dozens of fixes, new interface languages, and a revamped visual indicator for the active proxy.

Ten Interface Languages

Alongside the already supported English, Russian, Spanish, Turkish, Polish, Chinese, and Thai, French, German, and Brazilian Portuguese have been added. Now the extension is fully localized in ten languages, and switching between them happens instantly through the menu at the top. Each locale loads separately, so the bundle size hasn’t increased.

Genuine Protection Against IP Leaks via WebRTC

Previously, the Disable WebRTC checkbox in the settings was merely saved in the storage but never applied: your real IP could still be visible through STUN servers, even with the proxy active. In version 3.1, this protection finally works properly. The extension requests privacy permission and controls WebRTC policy via chrome.privacy.network: check the box and the browser stops using non-proxied UDP and multiple routes, preventing real IP leaks. Unchecking the box resets the settings back to the browser's default behavior.

Cleaning Up Phantom Privacy Settings

Options that were saved in the database but never applied have been removed from this section: timezone spoofing, browser language, geolocation, and browser fingerprinting blocking. These features require content script injections, are unstable on modern websites, and were not implemented in this version. The fields have been removed from the interface, and the storage schema is automatically cleaned up during the v3 migration when first launched after the update.

IP Switching Without Endless Loading

The most annoying issue from previous versions: after clicking the IP switch button, the spinner kept spinning until the popup closed, while the server rotation completed in just a few seconds. The root of the problem was that the rotation request went through the proxy, which dropped the connection during IP switching. In version 3.1, the rotation host has been added to the proxy's bypass list, the request goes directly with a short timeout of 12 seconds, and the timeout response is treated as partial success with automatic proxy data refresh and loader reset.

Updated Settings Page UI

The Cancel and Save buttons at the bottom of the form are now the same width and positioned right next to each other — previously, due to an unfortunate breakpoint at the width of the popup, they stretched across the entire width and stacked vertically. Hovering over the cancel button no longer turns it into an unreadable white rectangle: the background is contrasting, and the text remains dark.

Neat Active Proxy Indicator

The text badge 'ON,' which partially obscured the logo on the extension icon, has been replaced with a small green dot outlined in white in the upper right corner. The logo is fully visible and recognizable, while the active status can be read from any distance. The logo in the popup header no longer shakes when hovered over.

Automatic Synchronization Between Windows

If multiple popup windows are open or the state changes from the background script, changes are now automatically reflected in all UI instances. The proxy list subscribes to chrome.storage.local events and, with a debounced delay of 150 milliseconds, re-reads the fresh state from the database. Manual refresh is not needed.

Internal Improvements

A test runner, Vitest, has been added along with 26 unit tests for the proxy import parser, host and port validators, atomic ID generator, and toast queue. A versioning system for the storage schema has been introduced, with a migration mechanism — future updates will be able to safely change the data structure without losing user settings. A structural overhaul of the codebase has also been carried out: composables for proxying, repositories for the data layer, modules for the service worker, and separate section components for the settings page.

How to Update

In Chrome and Firefox, the update will automatically arrive from the official stores within a few hours of publication. Upon first launch after the update, your browser will ask you to confirm the new privacy permission — this is required for WebRTC leak protection to function. If you don't confirm immediately, the protection simply won’t activate until the next agreement. All other functions operate without additional confirmations.

Detailed descriptions of features, screenshots, and direct installation links are available on the Mobile Proxy Manager extension page on mobileproxy.space. The extension is also published in the Chrome Web Store and Firefox Add-ons.