Przejdź do treści

Tej strony nie ma jeszcze w Twoim języku. Czytasz tekst angielski.

Proxy

How to make sure all of a profile's traffic goes through the proxy

The proxy is set, but the site shows your home city? Check the profile in five minutes: ARMANOS shows the exit address and country right on the start page and points out where a gap may be.

Zespół ARMANOS7 minUpdated

In short

The green mark answers one question. The node is alive and passed a request.

Four places where traffic goes around. The rule entry, a typo in the address, calls, clock and language.

A check in five minutes. The start page, network diagnostics and a clock check.

What the green proxy check proves

You press Test, and a request goes through the proxy to an outside source that names the exit country. Four sources are queued, and the asking stops at the first that answers.

An answer means the host is alive, the password fitted and the country known.

What matters next is which connections go through the proxy: the rule entry in the browser decides that, not the colour of the dot.

  1. 1

    The host answers

    A request reached the proxy and came back.

  2. 2

    The country is named

    The exit address arrives from independent sources over a secure link.

  3. 3

    The rule sets the reach

    Which schemes the browser sends through is decided by the rule entry, not by the colour of the mark.

The line that sends https direct

The proxy address reaches the browser as one line of rule. Two wordings of that line exist, and the difference costs you all your real traffic.

A line like http=host:port means go through this proxy for http addresses only. Every https address then opens direct, from your home address, with no error shown.

Rule entryWhat results
http=host:portOnly http goes through the proxy, while https goes direct
http://host:portBoth http and https go through the proxy

One typo sends the profile direct

A space at the edge, a scheme inside the field, a login in the address, Cyrillic in the host name: the browser cannot parse such a string.

It does not report an error but goes direct, and the profile goes online from your real address.

That is why ARMANOS meets a bad address with a refusal at the launch button, before the first window opens. A profile that did not open costs less than a profile that opened with the wrong address.

  1. 1

    A space or a path inside

    The browser cannot read that line and applies no proxy.

  2. 2

    No connection kind chosen

    The address you typed would vanish whole, password included.

  3. 3

    The profile does not start

    A refusal at launch is safer than going online from your home address.

Exit through your own server takes the same road

A profile's proxy can be your own server over SSH, and the browser knows nothing about it. A tunnel is raised beside the profile, and the browser receives a plain socks5 on a local address.

ARMANOS checks an exit through your own server separately: if the tunnel did not come up, the profile does not start and does not go direct.

So the exit through your own server has two conditions instead of one: the host name and the port have to parse, and the tunnel has to be up before the window opens.

Miss either, and the profile does not start.

Video calls take their own route

Voice and video in a browser do not travel as ordinary requests. They open a direct connection between two machines, and it finds the shortest path by itself.

So a page with a call can read your home address while all other traffic goes through the proxy. It is closed by a browser setting that forbids a direct connection from going around the proxy.

What ARMANOS does for a clean exit

The profile start page shows the exit address and country: the ones a site sees.

A verdict stands beside them: it compares the exit address with your real one.

A bad address is met with a refusal at the launch button, and calls go through the proxy by default.

How ARMANOS closes the call

In the default WebRTC mode, for a profile with a proxy ARMANOS sets a rule for direct connections: no UDP without the proxy.

A call page sees only that your home address is absent among the candidates.

The rule follows the profile's WebRTC mode.

The "Real" mode does not set it, and an extension with the privacy permission may override it: the profile window names such an extension, and "Test fingerprint" measures with the profile's extensions.

Network diagnostics (Network > Run diagnostics, the WebRTC leak protection row) starts the engine your profiles open with, on a test profile behind a placeholder proxy, and asks for candidates from a STUN server on this computer's local network address: a request that reaches that server went past the proxy.

Candidates are parsed line by line, and an address ending in «.local» is not counted as a leak: the browser substitutes it for the home address on its own.

When the measurement fails, the row says so: «Could not be measured».

That answer and «No leak: the test request did not go past the proxy» are two different answers, and it does not pass off the first as the second.

On a leak the row says the request went straight from this computer, or names the addresses that went around the proxy.

Your home city comes from elsewhere

The clock, the languages and the fonts are read straight off the browser, not the request header. They are produced on your machine and never pass through a proxy.

For them to agree with the address, the exit country has to be learned first. The profile asks for it the way it will go later, over a secure connection.

What a platform reads from youWhere it comes from
The address in the request headerfrom the proxy
The time zone namefrom the profile, by the address country
The language listfrom the profile, by the address country
The direct call connectionfrom your machine, unless a rule closes it
The connection fields of a phonefrom the profile's engine

No verdict without your own real address

A profile opens the ARMANOS start page, and the exit address sits on it: the one the site will see. A verdict beside it compares that address with your real one.

Addresses that match mean the proxy dropped and work has to stop. When your own real address is unknown, no verdict appears: an invented all good is worse than a blank.

  1. 1

    The addresses differ

    The proxy works, and the site is not seeing you.

  2. 2

    The addresses match

    The proxy dropped, and the site sees the real you.

  3. 3

    Your own address is unknown

    No verdict: a guess here is worse than a blank.

Three connection fields mark a phone

Chrome on Android has three connection fields a desktop lacks. A platform reads them in one line, and a profile without them answers as a desktop.

They have to appear as three, and with values of their own. A host wifi and a host infinity there give a phone profile away as loudly as their absence.

Where the three connection fields come from

A phone profile derives the connection type from the delay using the browser's own thresholds: from 2010 ms it is slow-2g, from 1420 it is 2g, from 272 it is 3g, below that 4g.

The pair "4g at a 300 ms delay" never occurs in a real browser, and the profile never has it either.

The bandwidth ceiling comes from the same table the browser uses: 100 for LTE, and 11, 54 or 600 for Wi-Fi.

Two rules hold the three fields together: the ceiling is never below the reported speed, and the subtype matches its kind.

A desktop profile does not need these fields: a real desktop browser lacks them too.

How to check this yourself in minutes

Open the profile and read the exit address on its start page. Then open any outside page about your address: the country has to be the same.

Then check what travels outside ordinary requests: a call and the profile clock. One value out of line means the site sees the same gap.

  1. 1

    Compare two addresses

    The one on the profile's start page and one from outside.

  2. 2

    Check the direct connection

    A page with a call shows where that connection leaves.

  3. 3

    Line up clock and language

    Country by clock and language has to match the address.

Common questions

The proxy is green, but the site sees my city. Did the seller cheat?
Not necessarily: the seller's address may work as it should while the connection the browser runs its own way goes around it.
Why does https matter more than plain http here?
Almost all real traffic today goes over https, so a rule that covers only http covers a small part.
I typed an address with a space at the start. What happens?
The window trims spaces at the edges before saving. A typo inside the address is the danger: such a string cannot be parsed, and ARMANOS refuses to launch instead of going direct.
Do I have to switch calls off in a profile?
No, the direct connection keeps working, it is simply forbidden to leave around the proxy.
The start page showed no verdict. Is it broken?
No, a verdict appears only when both addresses are known, and without your own real one there is nothing to compare.
Can a profile sit on a SOCKS5 with a login and password?
Yes, the password is filled in along the way and never reaches the browser command line.

Check your proxy before the first sign-in

The free leak test shows which addresses your browser gives away outside the proxy.