Incogniton Proxy Not Connecting: Causes and Fix Order

The three most common causes

Connection type or authentication does not match. The Add proxy form offers HTTPS or SOCKS5 as the connection type, and Incogniton's troubleshooting page says it must match what your provider issued, and so must the username-and-password or IP-authorization method.

The port is missing from the address field. The Proxy (ip:port) field needs the port in it; you can also paste a full ip:port:username:password string there and Incogniton fills the other fields.

The proxy itself is down or out of date. If it fails in an ordinary browser too, the fault is the IP or its lease, not Incogniton.

• Sources:
• Incogniton docs: Attach external proxy
• Incogniton docs: Proxy connection failed

Checks in order

1. Step 1: Address and port

   In Proxy Library, using + New proxy and then the Proxy (ip:port) field, enter host and port exactly as shown in My assets, one value per field (or in the single field the app uses). The usual slips are a typo in the host, an extra digit in the port, or host and port swapped. Paste from My assets instead of typing.

   Expected result The fields match My assets character for character.

2. Step 2: Protocol (HTTP or SOCKS5)

   Set Connection type to HTTPS or SOCKS5 to match the asset. Each IP in My assets is issued with one protocol: HTTP on port 2222, SOCKS5 on port 3333. In our test of 4 November 2026 a static ISP per-IP lease also worked over the other protocol on its own port with the same login, but a per-GB asset did not, so use the protocol the asset shows.

   Expected result Protocol and port point to the same service as the asset.

3. Step 3: Username and password

   Copy both in full. A space copied at the end, a missing special character or a login from another asset is enough to fail. If the failure is a 407 or a sign-in prompt rather than a plain connection error, the address is reachable and credentials are the thing to fix.

   Expected result The check no longer says the credentials were refused.

4. Step 4: Your own network and system proxy

   Turn off any VPN or other proxy on the computer and try again, and check that a firewall or antivirus is not blocking the port. Incogniton's documentation also says a profile launch that fails with a connection error shows a red cancel icon next to the profile.

   Expected result The same proxy works once nothing else is sitting between the computer and it.

5. Step 5: The IP itself

   Open My assets and check that the lease is still active and, on per-GB assets, that traffic is left. Then run the curl test below from the same computer. If curl also fails, the problem is the IP or its lease, not the app.

   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 outside Incogniton

Incogniton's documentation suggests testing the proxy in another tool, for example Firefox with FoxyProxy. curl does the same job: run it below from the same computer.

If it works outside Incogniton, the cause is in the profile settings. If it fails, check the IP and lease. The guide on checking where a proxy exits shows how to confirm the exit location.

• guide on checking where a proxy exits

• Sources:
• Incogniton docs: Proxy connection failed

Using a Proxy302 IP in Incogniton

A static ISP IP stays the same for the lease term, so one profile can keep one address. The first setup is on the Incogniton integration page; for a fix, the steps below are enough.

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

• Incogniton integration page

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 Incogniton 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

Incogniton proxy setup

Add a Proxy302 IP in Incogniton's Proxy Library: paste the connection string, click Check, assign it to profiles. With screenshots.

Proxies in antidetect browsers

Set up a proxy in AdsPower, BitBrowser, GoLogin, Kameleo, Hidemium or GenLogin: one IP per profile, where each field goes, and what a failed proxy check really means.

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.

Proxy Not Working or Slow: Six-Step Self-Check

When a proxy won't connect or is slow, check six things first: address, port and type, login and password, one proxy app only, the antidetect browser port, the exit IP.