Esta página aún no está en su idioma. Está leyendo el texto en inglés.
Knowledge base
No profile could be launched
Read the rest of the line
The message carries a reason after the full stop. That reason is the actual cause, and the four below are what it usually says.
If the line ends without a reason, start with the open limit: it is the only cause that refuses before anything is tried.
The open limit came first
The app counts how many profiles are open and refuses to open one more past the computed ceiling. The number comes from the memory on this machine, not from a fixed twelve.
Close a window and try again. The refusal names the count it stopped at.
This is a refusal to open another, not a closing of the ones already open
The engine was not found
A profile opens in the ARMANOS Browser engine. If the app cannot find it, nothing launches and the reason says so.
Open the engine settings and point the app at the file. The app refuses a file it cannot execute rather than saving it and failing later.
The proxy did not answer
A profile with a dead proxy does not open, and that is deliberate: opening it would send your real address to the site while the window claimed it was proxied.
Check the proxy from the library. The check runs the same road a launch runs, so a check that passes means a launch will too.
A fresh address was asked for and failed
If the profile is set to rotate before every launch, a failed rotation stops the launch. The message says the profile was NOT opened.
That is the point: you asked for a new address exactly when the old one cannot be used.
Nothing above helped
Reproduce the failure, then collect the evidence rather than describing it. The app writes its log next to the profile data, and the support screen opens that folder for you.
Send the log with the exact time and the profile name. A message that says only «it does not work» costs you a day.
What this article does not cover
- A single profile that will not start. The message there is different and so is the cause.
- A profile that opens and then closes. That is the engine crashing, not the launch refusing.
- A platform refusing your login. Nothing in the launch path touches that.
Where this is decided
Each cause above is one place in the code and one stand.
- The bulk launch reports how many opened, and zero is reported as a failure
- apps/desktop/test/очередь-запуска.js
- The open limit is computed from memory, not fixed
- apps/desktop/test/предел-открытых.js
- A launch with a dead proxy does not open the window
- apps/desktop/test/прокси-с-паролем-живьём.js
- A refusal carries its reason rather than dropping quietly
- apps/web/test/отказ-не-молчит.js
Questions
- Does the bulk launch stop at the first failure?
- No. It tries every profile in the selection and reports how many opened. This message means the number was zero.
- Why is the open limit not a fixed number?
- Because a machine with 8 GB and a machine with 64 GB are not the same machine. The ceiling is computed from the memory actually present.
- Can I raise the limit?
- You can, and the app warns rather than forbids. Twelve browsers on 8 GB will make the machine unusable long before the platform notices anything.
Still stuck
Support reads the log you attach and answers with the cause, not with a checklist.