跳至主要內容

本頁面暫無您所用語言的版本,您正在閱讀英文原文。

Knowledge base

Proxy test failed

The test goes out through the same connection a profile would use and asks where it came out. This line means no answer came back, and the words after the colon name what stopped it.

The words after the colon

The proxy gave no answer in 12 seconds: nothing came back, neither an answer nor a refusal. The proxy is down, the port is wrong, or the seller's side is silent.

The proxy refused the connection: the address or the port is wrong, or nothing listens there. Check the address and the port.

The proxy address was not found: the name of the proxy does not exist. Check the address.

The proxy did not accept the login, or its traffic has run out: sellers answer both the same way. Check the login, the password and the balance with the seller.

The proxy did not let the app reach any address service: a provider that closes the IP checking sites answers this way, and so does a proxy that does not let this computer in. Set the time zone by hand, or read the article about your provider.

The proxy works, but none of the address services named its country: they answered with a refusal or a limit. Check again in a minute.

The app could not start its own bridge for a proxy with a password: close the profiles that use the same proxy and test again.

A launch refuses with the same words, and the proxy cell of the profile row shows the same reason as a short label next to a red dot.

Check the address, the port and the type

Copy the address and the port again from the seller's page: one wrong digit is enough to get no answer.

The type matters as much. A SOCKS5 proxy saved as HTTP answers nothing, and the other way round.

Check the login and the password

A wrong login or password is refused by the seller. Some sellers check the address of your computer instead of a password: add it to the allowed list in the seller's panel.

When the proxy itself is down

A paid period that ended, spent traffic or a port outside the range the seller gave you all look the same from here. The seller's panel shows which one it is.

A proxy through your own server

For a proxy through SSH the line names the SSH reason. Check the key, the user name and that the server lets this computer in.

What this does not do

  • It does not repair the proxy. A dead address stays dead until the seller or you fix it.
  • It does not keep testing. The answer is the state at the moment you pressed the button.

Where this is decided

The line and its link are held by stands you can run.

The test goes out the way a profile would, through the bridge for a proxy with a password
apps/desktop/src/main/main.js · apps/desktop/test/proxy-auth-bridge.js
Each reason is read from the real Chromium error code or from the bridge, not guessed
apps/desktop/test/причины-прокси-без-моста-живьём.js · apps/desktop/test/exit-geo.js
The line about a failed test carries How to fix, and it leads here
apps/desktop/src/manager/help-links.js · apps/desktop/test/как-исправить-ведёт-на-статью-сбоя.js

Questions

The proxy works in another browser. Why does the test fail here?
Compare the type and the port first: another browser may guess the type for you. Then check whether the seller allows the address of this computer.
Does a failed test change the profile?
No. The profile keeps its proxy, and the proxy list keeps the reason and the time of the last try.

Still stuck

Support answers with the cause, not with a checklist.