Перейти до вмісту

Вашою мовою цієї сторінки поки немає. Ви читаєте англійський текст.

Knowledge base

The seller answered, but the new address could not be checked yet

Nothing is broken here. The command went through and the seller accepted it, and what is missing is the confirmation: the app asked the proxy for its address afterwards and got no answer, which is what a modem in the middle of reconnecting looks like.

This is a state and not a failure

The line is careful on purpose. Saying the address changed without measuring it would be a claim we cannot back up, and saying it did not change would be a different claim we also cannot back up.

Wait a little and check the entry again. Most of the time it answers with a new address.

Nothing in the library was changed

The address the app knew is kept rather than erased, and the entry is not marked dead. A record is updated only when a check actually answers.

How the check is timed

The app measures the address before the command, sends the command, waits four seconds and asks again.

Four seconds suits most modems and not all of them, and the line above is what an unlucky one produces.

The modem is still reconnecting

A mobile proxy drops its connection to take a new address, and the tower decides when it comes back. Ten to thirty seconds is ordinary.

The seller limits how often

Many sellers accept the link but act on it no more than once every few minutes. The answer is still a success and the address simply stays the one you had.

When the check does answer in that case the app says the address is unchanged, which is a different line from this one.

The proxy stopped answering

If the entry keeps failing its check long after the rotation, the proxy itself is down and the rotation is beside the point. Check it from the library and the result names the reason.

Collecting the evidence

Press Check on the entry a minute later and keep both results: the one that could not confirm and the one after it. Two readings separate a slow modem from a dead proxy.

Write from the Support screen. Your rotation link is cut out of the report that travels with the message, so send only what you are comfortable sending.

What this article does not cover

  • A proxy with no rotation link. There is no button for it and the app says why.
  • Rotation on a timer. That runs against open profiles and reports on its own.
  • A seller that answers with an error page. That refusal carries the status and the first words of the answer.

Where this is decided

Each claim above is one place in the code and one stand.

A rotation reports three distinct answers rather than folding them into two
apps/desktop/test/proxy-rotation.js
Rotation on a timer runs the real code against real arguments
apps/desktop/test/ротация-адреса-исполняется.js
The rotation link is cut out of the report before it leaves the computer
apps/desktop/test/problem-report.js
A refusal carries its reason rather than dropping quietly
apps/web/test/отказ-не-молчит.js

Questions

Did the modem actually take a new address?
Most likely. The seller accepted the command, and only the confirmation is missing.
Should I press it again straight away?
Better not. A second command inside the interval the seller keeps usually does nothing, and some sellers count it against your quota.
Is my rotation link ever sent anywhere?
No. It stays on this computer, and it is cut out of the report that goes with a support message.

Still stuck

Support reads the report that travels with your message and answers with the cause, not with a checklist.