Вашою мовою цієї сторінки поки немає. Ви читаєте англійський текст.
Knowledge base
Choose a WebRTC mode
Where the setting is
Open the profile editor: the WebRTC mode block sits under Location, before Port scan protection. All five modes are on view, and the line under them says what this profile shows on its engine.
A new mode applies from the next launch. A profile that is open now keeps the mode it was started with, and the window says so. Pressing Launch again on an open profile is not a new launch: its new window keeps that mode too.
If ARMANOS closed unexpectedly while the profile stayed open, the restarted app picks that browser up and tells from the way it was started whether sites see your address in WebRTC.
The fingerprint card names the mode the profile runs with now. If another mode was chosen while it is open, the card adds it with the words "from the next launch".
The side panel of a profile has the same choice under Port scan protection, with the same line under it. A template, an import file, the local API and the AI assistant set the mode for a new profile.
The five modes
Proxy address is the default for new profiles and for every profile made before the setting existed.
- 1
Proxy address
Sites see the address of this profile's proxy, and this computer's address stays hidden. A profile without a proxy behaves as a plain Chrome.
- 2
My address
Sites see the address you enter. It should be the proxy's address: sites can notice a different one.
- 3
Real
Sites see this computer's real address, as in a plain Chrome. Choose it only for a profile without a proxy.
- 4
No UDP
WebRTC goes only through the proxy, over TCP. Sites see none of your addresses, and some calls will not connect.
- 5
Off
No WebRTC connections at all. Video calls, screen sharing and some chats will not work.
Until ARMANOS Browser is updated
Today My address, Off, and Proxy address on a profile with a proxy work as No UDP. Sites see none of your addresses in WebRTC, and their list of candidates stays empty.
A call through the site's own server over TCP can still connect through the proxy. The line under the mode says this, and it goes away once the engine learns to show the proxy's address.
On the built-in engine
The built-in engine cannot show a chosen address and cannot switch WebRTC off completely. There Proxy address, My address and Off always work as No UDP, and the window says this under the mode.
A built-in profile without a proxy also shows no address in Proxy address, as it always did. Pick Real for the look of a plain Chrome.
Which mode to pick
Keep Proxy address for a profile with a proxy. Real is honest for a profile without one, on a VPN or a mobile connection.
Pick No UDP when calls do not matter and no address should show at all. Off breaks calls, and a browser that refuses every call is rare in itself.
Check it on your computer
For a profile with a proxy, Test fingerprint in the fingerprint window measures WebRTC with this profile's own launch line, mode and extensions from the library. A profile without a proxy has nothing for WebRTC to go around, and the line says it was not checked. With an extension that can change WebRTC the line is yellow, even when nothing went past the proxy: the extension's own settings inside the profile are not part of the check.
Network > Run diagnostics measures the engine your profiles open with, on a test profile in Proxy address.
On a Mac the first check can stop at a system prompt about the local network. Allow ARMANOS under Local Network, in the Privacy & Security part of System Settings, then run the check again.
Read a check on another site
A WebRTC test page lists candidates by type. Three rows tell you most of it.
- 1
host
A name that ends in local is normal: Chrome hides the address of your own network behind it.
- 2
srflx
The public address a server saw. It should be the proxy's address, never yours.
- 3
An empty list
WebRTC is in No UDP or Off, or works as No UDP until the engine update.
An extension can override the mode
An extension with the privacy permission can switch WebRTC back to your real address: its setting outranks the rule the engine starts with. The profile window names such an extension under the mode.
Test fingerprint measures with the profile's extensions from the library and names the ones installed inside the profile.
What this does not do
- It does not show the proxy's address in WebRTC yet: until the ARMANOS Browser update the protected modes show no address at all.
- It does not block extensions that change WebRTC. It names them, in the profile window and in Test fingerprint.
- Test fingerprint does not see the own settings of extensions: those installed inside a profile do not take part, and those from the library start fresh. With such an extension the result is yellow and names it.
- A server you built yourself before the update does not keep the mode: then it stays on this computer only. With our server it travels through the account to your other computers and colleagues.
Where this is decided
The weightiest claims and the stand that holds each one.
- The launch line by mode on the built ARMANOS Browser with a STUN server on this computer: no request past the proxy in Proxy address, My address, No UDP and Off; Real, and Proxy address on a profile without a proxy, behave as a plain Chrome
- apps/desktop/src/lib/webrtc-профиля.js · apps/desktop/test/webrtc-строка-запуска-живьём.js
- Every window of a built-in engine profile keeps its mode, a window opened past the launch included
- apps/desktop/test/webrtc-встроенный-живьём.js
- An open profile keeps the mode it was started with: a new window after Launch pressed again sends nothing past the proxy, and the card and the profile window name the new mode for the next launch
- apps/desktop/test/webrtc-открытый-держит-режим-запуска.js
- A profile picked up after ARMANOS closed unexpectedly: the card and the profile window name the mode its browser was started with, checked against what a site sees in a new tab of that browser
- apps/desktop/test/webrtc-подхваченный-держит-режим-живьём.js
- The profile window and the fingerprint card speak by mode and engine, in English and Russian
- apps/desktop/test/webrtc-в-окне.js
- An extension with the privacy permission reopens the leak; Test fingerprint names it and never shows such a profile green
- apps/desktop/test/webrtc-расширение-живьём.js
- The side panel and the AI assistant set the same mode, and the panel says what it does on this engine
- apps/desktop/test/webrtc-в-панели.js · apps/desktop/test/webrtc-через-mcp.js
- Set or taken off on one computer, the mode reaches the other one and a colleague with access; a server without it keeps the mode on the machine
- apps/desktop/test/webrtc-переключатель-с-сервером-живьём.js · apps/desktop/test/webrtc-поле-местное-нынешний-сервер.js
Questions
- Why is the candidate list empty on a profile with a proxy?
- Until the ARMANOS Browser update, Proxy address works as No UDP: nothing leaves past the proxy, so the list stays empty.
- Can I change the mode of an open profile?
- Yes. The new mode applies at the next launch, and the window says so while the profile is open.
- Does the mode change the fingerprint?
- The derived fingerprint stays the same: the mode is a profile setting, and profiles made before it open as the same machine, in Proxy address. What WebRTC shows a site does follow the mode, as the list above says.
Try it on your own profiles
The free plan gives two profiles, with no time limit and no card.