If you work with multiple accounts through Firefox or an anti-detect browser based on its engine, sooner or later you will encounter the popup window "Server moz-proxy at... requires a username and password." It appears at the most inconvenient moment — in the middle of farming Facebook Ads accounts or scraping Wildberries — and breaks automation. Let's figure out where this window comes from and how to get rid of it once and for all.
What is the moz-proxy window and why does it appear
"moz-proxy" is an internal service name that Firefox assigns to the proxy server when it cannot determine its real address or when the request goes through a system/profile proxy without an explicitly specified host in the dialog. Essentially, the browser is saying: "I sent a request through the proxy, the server responded with code 407 Proxy Authentication Required, but I have no saved credentials for this connection." Hence the popup window asking for a username and password.
For an ordinary user who visits a single site, this is a one-time inconvenience. But for an arbitrageur who runs 20-30 profiles through a proxy in Dolphin Anty, AdsPower, or regular Firefox with an IP-switching extension, this is a critical problem: the window blocks automated scripts, interferes with headless mode, and prevents launching profiles in batches without manual intervention.
It is important to understand: this is not a proxy server error and not a bug in Firefox. This is standard behavior of HTTP/HTTPS and SOCKS5 protocols — the server indeed requires authentication, but the browser does not know how to pass it automatically. This can be resolved either by providing the data in advance or by configuring the browser for an automatic response.
Main reasons for proxy authorization requests
Before removing the window, it's worth understanding why it appeared in the first place — this will save time on diagnostics:
- The proxy requires a username/password, but the data has not been provided. The most common reason is that only the host and port are specified in the network settings, without credentials.
- The password or IP binding has expired. Some proxy providers tie access to a specific IP rather than a username/password — when your external IP changes, the authorization fails.
- Extension conflicts. If a proxy-switching extension and system network settings are enabled simultaneously in Firefox, the browser may "confuse" the source of authorization.
- Corrupted Firefox profile. An old cookies.sqlite cache or a corrupted prefs.js file can sometimes prevent the browser from saving previously entered data.
- SOCKS5 instead of HTTP(S). SOCKS5 proxies with authentication are not always correctly supported by Firefox's built-in network settings without extensions — hence the repeated requests.
After identifying the cause, choose one of the methods below — often just one or two points are enough to make the window disappear for good.
Quick fix: username and password directly in the proxy address
The simplest way to get rid of the popup window is to provide the credentials directly in the proxy connection string. The format looks like this: http://login:password@host:port. If you are using a proxy management extension (like FoxyProxy or similar), insert the username and password in this format into the server address field.
For manual configuration through the system network settings in Firefox, this method does not always work directly in the browser's address bar, so for multi-accounting tasks, it is more convenient to use proxy manager extensions — they can store username-password pairs for each proxy separately and automatically insert them upon connection, bypassing the dialog window.
If you rent residential proxies, note that some providers grant access not by username-password, but by an IP whitelist. In this case, the moz-proxy window will not appear at all — simply add your current external IP in the proxy management panel, and authorization occurs without entering a password.
Configuration via about:config and network.proxy
For more flexible configuration, open the Firefox address bar and enter about:config. Confirm the transition to the advanced settings screen. Then follow these steps:
- In the search bar, type
network.proxy— a list of all proxy parameters will be displayed. - Check the parameter
network.proxy.type— for manual proxy configuration, the value should be1. - Find the parameter
signon.autologin.proxy(if available) and set the value totrue— Firefox will attempt to use saved credentials without prompting again. - Ensure that the credentials for the proxy are indeed saved in the Firefox password manager (Settings → Privacy & Security → Saved Logins) and are not marked as outdated.
After changing the parameters, restart the browser — the network.proxy settings are applied only after a complete restart, not just refreshing the tab. If the window continues to appear, the problem is likely not in the cache, but in the proxy server itself: it may reject a specific session due to the limit on simultaneous connections.
Extensions for automatic proxy authorization
For daily work with dozens of accounts, manual configuration through about:config is excessive. It is more convenient to use extensions that handle the transmission of the username and password:
- Proxy Auto Auth — a lightweight extension that intercepts the 407 request and automatically inserts saved credentials without showing the window to the user.
- FoxyProxy Standard — in addition to authorization, allows switching between multiple proxies with one click, which is convenient when testing ads from different regions.
- Proxy SwitchyOmega (port for Firefox) — stores proxy profiles with attached credentials and domain switching rules.
After installing any of these extensions, add the proxy data once in the extension settings — the browser will no longer ask for a password with each new connection. This is especially critical if you keep multiple Firefox windows open with different proxies for client SMM accounts: without auto-filling the password, authorization windows will accumulate and interfere with work.
How this is resolved in anti-detect browsers
If you use Dolphin Anty, AdsPower, GoLogin, Incogniton, Multilogin, or Octo Browser, the moz-proxy window problem occurs significantly less frequently — these tools are initially designed for multi-accounting and pass proxy credentials at the profile level, bypassing the browser's dialog windows.
The typical setup looks like this: when creating a new profile, you open the "Proxy" tab, select the type (HTTP, HTTPS, SOCKS5), insert the host, port, username, and password into the corresponding fields of the form — and save the profile. All this data is stored within the anti-detect browser profile and applied automatically at each launch, without a single popup window.
If the authorization window still appears in the anti-detect browser, the reason is usually one of two: either an extra whitespace was copied into the username and password fields, or the wrong protocol was selected (for example, HTTP was specified instead of SOCKS5 for a proxy that only supports SOCKS5). Check both points before contacting the proxy provider's support.
For farming Facebook Ads and TikTok Ads accounts, many arbitrageurs choose mobile proxies precisely because they require re-authorization less frequently when changing IP — rotation occurs within a single operator session, not on the side of a third-party server.
Comparison of methods to eliminate the window
Below is a summary table of methods to get rid of the moz-proxy window — choose based on the scale of the task.
| Method | Difficulty | Suitable for |
|---|---|---|
| Username:password in the proxy address | Low | One-time setup, 1-2 proxies |
| IP whitelist from the proxy provider | Low | Static working IP, office |
| about:config + password manager | Medium | Experienced Firefox users |
| Proxy Auto Auth / FoxyProxy extension | Medium | Multiple proxies, SMM agencies |
| Profile in an anti-detect browser | Low after setup | Multi-accounting, arbitrage, 10+ profiles |
Common mistakes when configuring proxies in Firefox
Even knowing the theory, many make similar mistakes that cause the moz-proxy window to return again and again:
- Copying the password with extra characters. When copying from an Excel table or notes, an invisible space or line break at the end of the password often gets attached — authorization fails without an obvious reason.
- Mixing system network settings and extensions. If manual network settings (Settings → General → Network Settings) and an active proxy extension are enabled simultaneously in Firefox, they start to conflict — disable one of the options.
- Ignoring the protocol type. A SOCKS5 proxy set up as HTTP technically "works," but authorization proceeds incorrectly, and the window will appear periodically.
- Using one proxy across dozens of tabs simultaneously. Some proxy plans limit the number of simultaneous connections — exceeding the limit can also trigger a repeated password request.
- Outdated DNS cache in Firefox itself. Sometimes a simple cache clearing via
about:networking#dnsand restarting the browser helps.
Prevention in multi-accounting
If you manage 10-50 client accounts on Instagram, TikTok, or handle Facebook Ads accounts, it is important to establish a system where the moz-proxy window does not appear at all, rather than eliminating it manually each time. The recommended approach:
- Use a separate anti-detect browser profile for each account with a proxy tied at the profile level, not at the browser level.
- Choose a proxy provider that supports IP whitelisting where you have a static working or server IP — this completely removes the need to enter a password.
- For tasks requiring high session stability (e.g., long account warming), use residential proxies with session binding, rather than changing IP with each request — this reduces the number of repeated authorization requests.
- For mass scraping of prices on Wildberries, Ozon, or Avito, where speed is more important than binding to a specific device, data center proxies are better suited — they maintain a stable connection with a large number of parallel requests.
- Regularly check the validity of the username and password with the proxy provider — many services automatically change the access password every 30 days for security reasons.
This system eliminates the need to "put out fires" every time the authorization window pops up and allows you to scale the number of accounts without manually monitoring each profile.
Conclusion
The window requesting a username and password for moz-proxy in Firefox is not a malfunction, but a standard response of the browser to the proxy server's authorization request. It can be removed in several ways: by providing credentials directly in the connection address, configuring parameters via about:config, installing an extension for automatic authorization, or switching to working through profiles in anti-detect browsers, where proxy data is tied to the profile and inserted without user involvement.
If you plan to engage in multi-accounting in Facebook Ads, TikTok Ads, or Instagram without constant authorization failures, it is advisable to immediately choose a proxy with IP whitelist support or stable session binding. For warming up and long-term work with accounts, we recommend trying residential proxies — they provide a high level of anonymity, stable sessions, and minimal risk of repeated authorization requests in Firefox and anti-detect browsers.