Docs · Reference

Limitations: what won’t work

An honest list of what Routekeeper can’t do, or can do only with caveats. For each item: what you’ll notice, why it happens and what you can do.

All docs sections

Here is the short version, with details on each item below.

LimitationIn short
UDP, calls and gamesOnly TCP goes through the proxy. UDP from an app on the proxy is blocked or goes direct.
Domain rulesThey work only when the app gives the site’s name. Connections to a bare IP follow the app’s route.
Browser profilesAll profiles of one browser follow the same route.
Extension restartFor a couple of seconds, new connections may go direct.
Other VPNs and extensionsRoutekeeper doesn’t know about them and doesn’t check for conflicts.
Work HTTP proxyOnly Basic authentication: no NTLM, Kerberos or PAC.
Proxy typesOnly SOCKS5, HTTP and HTTPS. Other protocols work through a local client.

UDP: calls, voice and games

What you’ll notice.

Why. The proxies Routekeeper works with (SOCKS5, HTTP and HTTPS) carry only TCP. UDP from an app whose route goes through a proxy never gets into the proxy:

Calls and games usually need UDP. Browsers see that QUIC is closed and switch to TCP by themselves. The service card (ⓘ in the Apps section) warns about this, for example: “Calls use UDP and don’t work through a proxy”.

What you can do.

Details: UDP and DNS for an app on the proxy
  • Routekeeper doesn’t use UDP relaying through SOCKS5 (UDP ASSOCIATE).
  • DNS queries over UDP (ports 53 and 853) from an app on the proxy aren’t blocked. They go direct and are flagged as DNS around the proxy. You can block them with a rule. How this works is explained in DNS: how apps find a site’s address.
  • For TCP connections through the proxy, the proxy itself finds the site’s address by its name if DNS through proxy is on (it’s on by default).
  • With Settings → Network → Look up site addresses through the proxy, UDP DNS queries to port 53 of an app on the proxy go through the proxy, except local names. For details, see Site addresses through the proxy.

Domain rules need a site name

What you’ll notice. A rule like *.example.com → Through Proxy, or a service rule, doesn’t catch all the traffic. Some connections follow the app’s route, for example going direct. In the monitor, such connections have a bare IP in the Host column, and the Decision field shows the app’s route, not your rule.

Why. Domain and service rules compare the site name that the app gives when it connects. Connections to a bare IP have no name, and neither do most UDP and QUIC connections. Some apps look up addresses themselves and connect only by IP. Without a name, the rule doesn’t apply, and the connection follows the app’s route. The exception is services whose lists include subnets: they also match by IP.

What you can do.

For more, see Rules by site name.

Two profiles of one browser

What you’ll notice. You want the “Work” profile to go through one proxy and “Personal” through another. Both go the same way.

Why. Routekeeper recognizes apps by their code signature and processes. All profiles of one browser are one app with the same processes, and a profile isn’t visible at the network level.

What you can do.

Details: beta versions of browsers

Chrome Beta, Dev and Canary are separate apps with their own signatures, and you can give each its own route. But if Include Child Processes is on for Chrome, Chrome’s route covers them too: their signing IDs start with Chrome’s signing ID, and the developer is the same. To make a beta version go its own way, add it to Apps with its own route. A rule for the exact app takes priority over a rule for child processes. Beta versions of Edge work the same way.

Pause when the extension restarts

What you’ll notice. After the extension updates (starting with version 0.5.0, it updates by itself right after the app does), after you click Reinstall, or if macOS restarted the extension, connections through the proxy break off, and apps connect again. For a couple of seconds, new connections may go direct, around the proxy. They don’t appear in the monitor.

Why. Routekeeper makes its decisions inside the network extension. While the extension restarts, nobody checks connections, and macOS lets them through as usual. When you update the extension from the banner, Routekeeper warns about this in the confirmation dialog.

What you can do.

Details: when connections don’t go direct

If Routekeeper’s filter is already working, but the part that sends traffic through the proxy isn’t yet (for example, right after the Mac starts up), connections meant for the proxy are blocked instead of going direct. The app gets an error and tries again. This behavior is called fail-closed.

The Routekeeper On switch and Stop… let everything go direct on purpose. How the ways to turn Routekeeper off differ is described on the Updates and removal page.

Other VPNs and network extensions

Routekeeper doesn’t check whether the Mac has other VPNs, proxy clients or firewalls, and doesn’t warn you about them. What happens alongside them follows from how Routekeeper works:

What you’ll notice when there’s a conflict. An app doesn’t go where the monitor says. Sites see an unexpected IP. Apps on the proxy lose the network when another VPN connects or disconnects. The proxy check fails.

Why. Several programs that intercept connections can work at the same time: a proxy client in TUN or “system proxy” mode, another firewall, another app router. Routekeeper doesn’t control the order in which they see a connection.

What you can do.

Work HTTP proxy: Basic only

What you’ll notice. Check shows HTTP: the proxy requires authentication (407), even though the login and password are correct. Or a browser works through the work proxy (it was set up automatically), but Routekeeper doesn’t. Or connections to ports other than 443 get an error like “The HTTP proxy answered 403 …”.

Why.

What you can do.

Details: SOCKS5 authentication

SOCKS5 works without a password or with a login and password (the username/password method). The login is 1 to 255 bytes, and the password is up to 255 bytes. Other SOCKS5 authentication methods aren’t supported: the check will show SOCKS5: the proxy accepted no authentication method.

Only SOCKS5, HTTP and HTTPS

What you’ll notice. You can’t add a link to a VLESS, Shadowsocks, WireGuard or similar server to Routekeeper.

Why. Routekeeper talks to proxies only over SOCKS5, HTTP CONNECT and HTTPS (CONNECT inside TLS). Chains of several proxies aren’t supported either.

What you can do. Run a client for that protocol on the Mac (sing-box, Xray, Clash and others) with a local SOCKS5 port, and add it to Routekeeper. For details, see the recipe On top of sing-box, Xray or Clash. If you don’t have a server of your own, you can set one up with the Your own proxy server guide.

Other things worth knowing

Checked against the Routekeeper code (version 0.2.1 and the one after it) on October 4, 2026.