Cette page n’existe pas encore dans votre langue. Vous lisez le texte anglais.
Knowledge base
Could not get a fresh IP, so the profile was NOT opened
The moment the address changes
A profile can ask for a new exit address every time it opens. The switch is in the profile window, named Get a fresh IP before each launch.
It is offered only for a proxy taken from the library, and only when that entry carries the seller's change link. There is nothing to walk for a proxy typed by hand.
Why nothing was opened
The new address was asked for because the old one cannot be used again. Opening the profile on it anyway would be the quiet wrong answer, so the launch stops instead.
All of this happens before any browser starts, so no window was opened. If session sync is on, the session may already have arrived from the shared folder, because that step comes earlier in the launch.
The profile is not left busy
The words after the colon
Silence from the seller for twenty seconds is reported as silence. An answer that is not a success comes through with its status and the first words of what was said.
A change link that tries to send the request to a different host is refused rather than followed. An entry whose link is no longer saved says that too.
Different from an unconfirmed change
There is a second line about changing an address, and it says the seller answered but the new address could not be checked yet. That one is not a failure, and a profile set to change before launch opens anyway.
Where else this refusal appears
A bulk launch counts that profile as failed and moves on to the next one. It is not the case where the queue waits for room, because here there is nothing to wait for.
A flow run marks the profile failed and puts this same line into the log of the run. A launch ordered from outside the app travels the same road and gets the same answer.
Collecting the evidence
Open the proxy library and press Change IP on that entry by hand. The answer there is longer and names the address before and after, which is what separates a silent seller from a slow modem.
Write from the Support screen. The report that travels with it carries versions, settings and the app's own recent notices, and nothing from the proxy library, so your change link is not in it.
What this article does not cover
- A change on a clock while the profile is open. An open window is not closed when that one fails.
- A promise that the address will be different. A seller that accepts the command and hands back the address you had counts as a success, and the profile opens.
- A proxy that has simply stopped answering. The change link is walked directly rather than through the proxy, so a dead proxy is a separate matter.
- The switch on a hand-typed proxy. There is no seller link behind it, and it does not turn on.
Where this is decided
Each line below names a place in the code, and four of them a stand that runs it.
- A launch stops when the fresh address could not be obtained, instead of opening on the old one
- apps/desktop/test/proxy-rotation.js
- The claim on the profile is handed back after a change that failed
- apps/desktop/test/proxy-rotation.js
- A change on a clock touches only open profiles and is not retried every minute
- apps/desktop/test/ротация-адреса-исполняется.js
- A bulk report does not pass a real refusal off as a queue that ran out of room
- apps/desktop/test/очередь-запуска.js
- The session arrives from the shared folder before the profile asks for a new address
- apps/desktop/src/main/main.js (code only, no stand for this)
Questions
- Did the profile open on the old address?
- No. The refusal comes before the browser starts, so no window was opened on the old address.
- Is the profile busy now because of this?
- No. The claim on it is handed back before the message appears.
- Will the clock and language follow the new address?
- After a change that went through, the remembered exit country is forgotten and both are worked out again from what the proxy shows.
- Can it open first and change the address after?
- No, and that is the point of the switch. The browser reads its exit at the moment it starts, and a swap after that is visible to the site as a swap in mid session.
Still stuck
Support reads the report that travels with your message and answers with the cause, not with a checklist.