Back to all guides

Proxy servers

Add and test a proxy server

Understand how SOCKS5, HTTP, HTTPS, credentials, failure behavior, and latency tests map to the current app.

The Proxies page stores upstream servers. App rules on the Rules page decide which app uses which proxy.

01

Choose a proxy type

  • SOCKS5: treated by the current app as the proxy type that can support both TCP and UDP.
  • HTTP: used for TCP connections.
  • HTTPS: connects to an upstream HTTP proxy over TLS and is also TCP-only.
02

Enter server details

  1. 1

    Name

    Give it a name you will recognize, such as Office Proxy. It only shows inside Antify and has no effect on the connection.

  2. 2

    Server Address and Port

    Enter the listener address of a local proxy app or a remote proxy host. The port must be between 1 and 65535.

  3. 3

    Authentication

    Leave credentials empty when the proxy does not require them. Passwords are stored through macOS Keychain rather than as plain text in the proxy record.

Antify Proxies page with two configured proxies and latency test actions
03

Choose what happens on failure

Block is the default and more conservative behavior. If the proxy connection fails, affected connections stay blocked until the proxy recovers.

Direct allows a connection to bypass the proxy after failure. This reduces downtime, but traffic that was expected to use a proxy may connect directly. Choose it only when that boundary is acceptable.

04

Decide whether the proxy reaches private networks

The switch next to it is Can reach private networks, off by default. While it is off, connections to private addresses go direct and never reach the proxy. The switch belongs to the proxy, not to a rule: the fact that you wrote a rule does not mean this egress can reach a LAN.

With it on, the network this Mac is directly attached to still goes direct. Private address space holds two unrelated networks at once: the one this Mac is plugged into, and the one behind the proxy. Sending the first to a remote proxy either fails or quietly reaches a different device that happens to have the same address.

Turning it on reveals a Custom networks field. Once it is filled in, only the networks you listed go through the proxy and every other private address stays direct. The list no longer consults whether a network is one this Mac is on, because an explicit setting beats the automatic one. When the local and remote networks overlap, that is the only way out.

  • The field takes IP addresses and networks only, such as 10.2.2.0/24; hostnames and wildcards are rejected.
  • To reach every private network except the one this Mac is on, leave the field empty. That is the ordinary case and the automatic behavior.
  • A proxy record that is missing or disabled is treated as unable to reach private networks.
  • Block rules are unaffected by this switch: private addresses are still blocked.
05

Use latency tests

The gauge button checks one proxy. Test All checks every proxy in the list. Successful results show access latency, while error details help distinguish connection, handshake, and authentication failures.

Use the link button to set the test URL. Pick a stable HTTP or HTTPS endpoint that you are allowed to access and that represents your actual use case.

06

Edit and delete

Edit the address, port, or type and save; neither Antify nor the extension needs restarting. Deleting a proxy is blocked while an app rule or a Configuration default still uses it.

If deletion is blocked, remove those references in Rules or Configurations first.