SwitchyOmega Proxy Login Popup and 407: Causes and Fix

The three most common causes

Credentials were never saved in the profile. The 2.x line of the extension supports HTTP and HTTPS proxy authentication with a username and password; if nothing is saved, or Apply changes was skipped, the proxy keeps asking.

The proxy is SOCKS5 with a password. SwitchyOmega's FAQ says SOCKS authentication is not implemented in Chrome and so cannot be done in the extension.

The extension is not the one you think. The original author says it is no longer maintained and that Chrome disabled it because it is not Manifest V3; many people now use a fork such as ZeroOmega, whose menus can differ from the steps here.

• Sources:
• SwitchyOmega on Mozilla Add-ons
• SwitchyOmega wiki: FAQ
• SwitchyOmega issue 2513: Manifest V3
• Oxylabs: SwitchyOmega integration (third-party guide)

Checks in order

1. Step 1: Is the right profile active?

   Open the SwitchyOmega menu and confirm the proxy profile you edited is the one selected, not Direct or System Proxy. After any edit, click Apply changes; edits that are not applied do nothing.

   Expected result Browsing now goes through the profile you edited.

2. Step 2: Protocol

   For a browser, use an HTTP asset (port 2222 on proxy.proxy302.com). Chrome does not implement SOCKS password login, and SwitchyOmega's own FAQ says it cannot be done in SwitchyOmega, so a SOCKS5 asset with a password will not work here.

   Expected result The profile's protocol matches an HTTP asset.

3. Step 3: Save the credentials in the profile

   In the proxy profile, click the lock icon at the right of the server row, enter Username and Password under Proxy Authentication, click Save changes, then Apply changes. Without saved credentials the proxy keeps asking, so the browser keeps showing a sign-in window.

   Expected result The sign-in window stops appearing.

4. Step 4: Copy the values exactly

   Paste host, port, username and password from My assets. A trailing space, a missing special character or the login of another asset keeps returning 407, which means the proxy asked for credentials and did not accept the ones it got.

   Expected result The page loads instead of asking again.

5. Step 5: The IP itself

   Check in My assets that the lease is active, then run the curl test below with the same values. If curl fails too, the problem is the IP or its lease, not SwitchyOmega.

   Expected result curl returns JSON with an exit IP.

Symptom, check and action

Test the proxy outside the app with curl: example

# HTTP asset (port 2222)
curl -x http://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json

# SOCKS5 asset (port 3333; socks5h also resolves DNS through the proxy)
curl -x socks5h://LOGIN:PASSWORD@HOST:PORT https://ipinfo.io/json

Example only: replace the placeholder values with your own. Use the line that matches the asset protocol.

Test the same proxy with curl

Run the curl test below with the same host, port, username and password. If it returns JSON with an exit IP, the IP and credentials are fine and the fault is in the extension setup. If it returns 407, the credentials are wrong or the asset has changed.

For a full explanation of the 407 code and other causes, see the 407 guide.

• 407 guide

• Sources:
• SwitchyOmega wiki: FAQ

Using a Proxy302 IP in a browser extension

For a browser, a static ISP asset with the HTTP protocol gives you a fixed address and works with a saved username and password. For the full install and profile setup, see the guide on the Chrome proxy setup; this page only covers the error.

From mainland China, start Fast Connect from the Tools & checks page first and keep it open while you use the proxy.

• guide on the Chrome proxy setup

How to do it with Proxy302: steps

1. Step 1

   Open My assets in the console and click the IP. Note the protocol (HTTP or SOCKS5) and copy host, port, username and password.

2. Step 2

   Enter the four values in the SwitchyOmega proxy profile and choose the same protocol. Do not type them by hand if you can paste.

3. Step 3

   Run the curl test above from the same computer. If curl returns JSON with an exit IP, the IP works and the fault is in the app settings or the app network.

4. Step 4

   If curl fails too, check that the lease is still active, then open a Support ticket with the order number: a failed IP or proxy is fixed by reissuing it.

Prices and limits

Static ISP per-IP leases run 1, 3, 7, 30, 60 or 90 days, from US$0.50 for 1 day to US$7.99 for 30 days. There is no free trial; the smallest purchase is one IP for one day.

• Sources:
• Proxy302 product facts and price list

FAQ

Read next

407 Proxy Authentication Required

HTTP 407 Proxy Authentication Required comes from the proxy server, not from the website you are trying to reach.

Chrome proxy setup

Set a proxy in Google Chrome: system settings, the --proxy-server flag, why SOCKS5 with a login does not work, extensions and a check.

Proxy302 Chrome extension

Install the Proxy302 browser extension in Chrome, Edge or 360 Browser, send a proxy from My assets with one click and check your exit IP. HTTP proxies only.

Fix ERR_PROXY_CONNECTION_FAILED

The ERR_PROXY_CONNECTION_FAILED error appears in Chrome and Edge when the browser cannot establish a connection with a proxy server.