Docs · Setup

Proxies: where to send traffic

A proxy is the server Routekeeper sends the traffic of your chosen apps through. This page covers how to add a proxy, check it and, if needed, replace it with another one.

All docs sections

Routekeeper has no servers of its own. It sends app traffic to the proxy you give it: your own server, a client of another program on this Mac, a work proxy or a proxy from a provider.

App → Routekeeper → proxy → site

Don’t have a proxy? Routekeeper can set one up on a rented server by itself: all it needs is the server’s IP and password. See Your own proxy server.

Which type to choose

Routekeeper works with three types of proxy. The type sets how Routekeeper talks to the server. Apps don’t notice the difference.

TypeDefault portWhen to choose itWhat to know
SOCKS51080A sing-box, Xray or Clash client on this Mac. A proxy from a provider with a line like socks5://….The connection to the proxy isn’t encrypted: the login, password and site names can be seen on the way.
HTTP8080A work proxy in the office. A proxy with a line like http://….The connection to the proxy isn’t encrypted. Only login-and-password sign-in.
HTTPS443Your own server, set up with our guide. A proxy with a line like https://….The connection to the proxy is encrypted with TLS. The Server field needs a domain name.

How to choose:

Routekeeper doesn’t support other protocols, such as Shadowsocks or VLESS, directly. If your server uses such a protocol, run its client on the Mac and connect Routekeeper to the client’s local port, as described below.

Details: how Routekeeper talks to each type of proxy
  • SOCKS5: as in RFC 1928, with login and password as in RFC 1929. Only the CONNECT command is used, so only TCP. Routekeeper doesn’t use UDP ASSOCIATE, so UDP doesn’t go through SOCKS5 even if the client supports it.
  • HTTP: for each connection, a tunnel is opened with the CONNECT method, including to port 80. The login and password are sent in the Proxy-Authorization: Basic header.
  • HTTPS: the same CONNECT inside TLS 1.2 or newer, ALPN http/1.1. The server certificate is checked against the macOS trusted root certificates and the name in the Server field. A self-signed certificate won’t pass the check.
  • Routekeeper allows 15 seconds to set up a tunnel (TCP, TLS and the handshake with the proxy), or 10 seconds during a check. Open tunnels are checked with TCP keepalive: after 30 seconds of silence, three probes 10 seconds apart. A tunnel whose server has gone away is closed after about a minute.

How to add a proxy

The quickest way is to paste a proxy line. If you don’t have a line, fill in the fields by hand.

  1. In the Routekeeper window, open the Proxy section (⌘4).
  2. Click + below the list of proxies or the + (Add Proxy) button in the toolbar, which shows only an icon. ⌥⌘N does the same from any section. Empty fields open on the right. The toolbar button also has a menu (the arrow next to the icon): Proxy by Address…, Paste from Clipboard and Your Own Server….
  3. Fill in the fields as shown in the table below. If you have a rented server but no proxy yet, choose Your Own Server… in the Add Proxy button’s menu instead: Routekeeper sets up a proxy on the server and adds it, see Your own proxy server.
  4. Click Check. You can check before you save: Routekeeper uses what’s in the fields. What the result means is explained in Checking.
  5. Click Add. The proxy appears in the list on the left, and Routekeeper checks it again right away.
  1. Paste Link opens a new proxy from a line on the clipboard, for example https://user:pass@nl.example.net:443. In the list, ⌘V does the same. The + button opens empty fields, − deletes the selected proxy.
  2. An HTTPS proxy needs a domain name in the Server field, not an IP address: the certificate is checked against it. The note under the fields appears only for the HTTPS type. The Server IP address field is optional: the “?” next to it explains that Routekeeper finds the address itself.
  3. DNS through proxy: the proxy gets the site’s name and looks up its address itself. On by default. The explanation is behind the “?”.
  4. Block UDP and QUIC: UDP from this proxy’s apps is blocked instead of going around the proxy. On by default. The explanation is behind the “?”.
  5. Check opens a connection through the proxy and shows the time, the IP address websites see, and the country code. You can check before saving.
  6. Copy Link copies the proxy line with its login and password, to send it to someone else. Save becomes available once a field is changed, and then Revert Changes appears next to it.
A sketch of the Proxy section of the Routekeeper window, with the “Amsterdam” proxy selected. Above the fields there is also a latency chart, not shown here. The data is made up.

On first launch, the same is on the welcome screen: the Add a proxy server step, with the Paste from Clipboard and Enter Manually… buttons.

FieldWhat to enter
NameAny name you’ll see in the route menu: “Amsterdam”, “Office”. If you leave the field empty, the server address becomes the name.
TypeSOCKS5, HTTP or HTTPS. How to choose: see above.
ServerA domain name like proxy.example.net or an IP address like 203.0.113.10; IPv6 works too. No https:// and no port. For HTTPS, only a domain name: the certificate is checked against it.
Server IP addressOptional; usually leave it empty. Routekeeper finds the server’s address itself, even when your network’s DNS won’t give it out. Enter an IP only if that doesn’t work either: for example, the proxy fails with “Couldn’t find the address of server”. The server wizard fills the field in by itself. For details, see How Routekeeper finds the server’s address.
PortThe proxy’s port, a number from 1 to 65535. If you leave the field empty, Routekeeper uses the default port for the type: 1080, 8080 or 443. The hint in the field shows which one.
LoginIf the proxy lets you in without a password, leave it empty.
PasswordSaved only together with a login.
DNS through proxyOn by default. Usually you don’t need to change it. What it does: see below.
Block UDP and QUICOn by default. Usually you don’t need to change it.

To change a proxy, select it in the list, edit the fields and click Save. Until you change something, Save is dimmed. After an edit, Revert Changes appears next to it and brings back the saved values. The Used in rules: N line below the Check button shows how many routes and rules go through this proxy.

Details: where the password is stored

The password is stored by the Routekeeper network extension in its settings file. Only the system (root) can read this file. The Routekeeper window doesn’t get the saved password: the Password field shows dots instead, and the extension itself runs the proxy check. The one exception is the Copy Link button: for it the extension hands over the password to put the link on the clipboard. If you don’t touch the field, the password stays the same when you save. If you clear Login, the password is deleted.

Paste a proxy line

Providers and the server install script give you a proxy as a single line. Routekeeper reads it by itself.

  1. Copy the proxy line (⌘C).
  2. Paste it into Routekeeper:
    • The Proxy section: click the list of proxies on the left and press ⌘V, click Paste Link below the list, or choose Paste from Clipboard in the Add Proxy button’s menu.
    • The welcome screen: at the Add a proxy server step, click Paste from Clipboard.
  3. A new proxy opens with the fields filled in. Check the type, server, port and login, click Check, then Add. Nothing is saved until you click Add.

Which lines Routekeeper understands:

LineTypeLogin and password
socks5://user:pass@203.0.113.10:1080SOCKS5user and pass
socks5h://203.0.113.10:1080, socks://203.0.113.10:1080SOCKS5none
http://proxy.corp.example:3128HTTPnone
https://user:pass@proxy.example.net:443HTTPSuser and pass
203.0.113.10:1080SOCKS5none
203.0.113.10:1080:user:passSOCKS5user and pass
user:pass@203.0.113.10:1080SOCKS5user and pass
socks5://[2001:db8::1]:1080SOCKS5, IPv6 address in square bracketsnone

If the clipboard doesn’t hold a proxy line, Routekeeper replies: “The clipboard has no proxy string. Expected something like socks5://user:pass@host:1080”. The Copy Address item in a proxy’s context menu copies only address:port, without the login and password. Copy Link copies the whole line.

Details: socks5 and socks5h

In other programs, the h in socks5h:// means “the proxy looks up site names”. In Routekeeper, both prefixes give the same SOCKS5. Whether the proxy gets names is decided by the DNS through proxy toggle, and it’s on for a pasted proxy.

Share a proxy

To send a proxy to someone else or move it to another Mac, copy it as one link:

  1. Select the proxy in the list and click Copy Link below the fields. Or right-click the proxy in the list and choose Copy Link with Password.
  2. Paste the link into a message. It looks like this: https://login:password@proxy.example.net:443#Frankfurt.
  3. The recipient pastes it into Routekeeper: the type, server, port, login, password and name fill in on their own. Other apps usually understand such a line too and skip the name after #.

DNS through proxy and UDP blocking

Each proxy has two toggles: DNS through proxy and Block UDP and QUIC. Both are on by default, including for a pasted proxy. They apply to connections that go through this proxy.

DNS through proxy

When an app opens a site by name, Routekeeper gives the proxy the name, for example example.com, not the IP address your Mac found. The proxy looks up the site’s address itself, through its own DNS.

This way, the site opens at an address that suits the server’s location: big sites give out different addresses in different countries. And if your network’s DNS answered with a wrong address, the proxy still finds the right one.

This works only when the name is known. If an app connects to an IP address by itself, the proxy gets the IP. For more about connections without a name, see Rules.

When to turn it off. When the names you need are known only to the DNS of your local or work network, and the proxy is outside that network. For example, internal company sites that open only from the office network: a remote proxy won’t find them. With the toggle off, Routekeeper gives the proxy the address your Mac found. In all other cases, keep the toggle on.

Details: what your network’s DNS sees

A connection reaches Routekeeper when the app already knows the server’s address. If macOS itself looked up the name, its query went to your network’s DNS before Routekeeper saw the connection. The toggle decides which address the proxy opens the site at, but it doesn’t cancel that query. How DNS works in Routekeeper, and how a browser can look up names over a secure channel, is explained in How it works and DNS over HTTPS in the browser.

Site addresses through the proxy

DNS through proxy helps when an app connects to a site through the proxy by name. But many apps first ask your network’s DNS for the site’s address themselves. If the network doesn’t know the name or says it doesn’t exist, the app never connects, even though it goes through the proxy. This happens with a corporate VPN that knows only its own sites, or with an ISP that filters DNS.

For this, there’s a switch: Settings → Network → Look up site addresses through the proxy, on by default. With it, DNS queries of apps that go through a proxy are sent through that proxy to a public DNS (Cloudflare, or Google if it fails) instead of the network’s DNS. Other apps, and names the rules send direct, ask the network’s DNS as before.

When it won’t help. If macOS looks addresses up over encrypted DNS, for example a DNS over HTTPS profile is installed or the network offers encrypted DNS itself, there are no plain DNS queries, and the switch changes nothing. macOS also keeps a shared cache of answers: if another app that goes direct recently got “no such name” from the network, that answer can reach an app that goes through the proxy too. How DNS works is described in How it works.

Block UDP and QUIC

SOCKS5, HTTP and HTTPS proxies carry only TCP. UDP is a different kind of traffic: it’s used by QUIC in browsers, by voice and video calls, and by games. UDP can’t go through the proxy.

The toggle doesn’t block DNS queries (ports 53 and 853): without them, apps would stop working. Such queries go direct and are flagged in Leaks as DNS around the proxy.

When to turn it off. When it matters more that calls work than that they go through the proxy. For example, a messenger goes through the proxy, and its calls use UDP: with blocking, they won’t connect at all; without it, they go direct. The toggle applies to all apps on this proxy. To leave the others as they are, add the same server again under a different name, turn off blocking only for this copy, and choose the copy as the messenger’s route. Calls over UDP don’t work through a proxy in any case; see Limitations.

Details: when the toggle applies

The toggle is checked for a UDP connection that, by the rules, should go through this proxy: by the app’s route, by a service or by a rule. Connections to ports 53 and 853 are let through directly and flagged “DNS around the proxy”, unless a separate rule has already blocked them. The rest of the UDP is blocked or, with the toggle off, let through directly and flagged. The toggle doesn’t affect UDP from apps that don’t go through the proxy. For example, a browser’s QUIC without a site name follows the browser’s own route; see Rules by site name.

Checking

The Check button opens a connection through the proxy to the ipinfo.io service and asks which IP address it sees. If ipinfo.io doesn’t answer or refuses, as it does for addresses of some hosting providers, Routekeeper asks Cloudflare, then ipify. After a couple of seconds, the result appears next to the button, for example:

Working · 640 ms · IP 203.0.113.10 (NL)

In the list of proxies on the left, each proxy has a colored dot and a short line: green means it works (SOCKS5 · 640 ms · NL), red means unreachable, blue means checking…, gray means not checked.

You don’t need to click Check every time. Routekeeper checks proxies by itself: after you save; when you open the Proxy section, if a proxy hasn’t been checked yet; and, for the main proxy, when you open the menu of the menu bar icon and after the network changes. While the main proxy isn’t answering, it’s rechecked once a minute. To check all proxies at once, use the Check All button in the toolbar.

Latency history

Above the settings of the selected proxy is a latency chart for the last hour, day, 7 or 30 days. Routekeeper records the time of every connection through the proxy and of every check. It doesn’t make separate measurements or spend extra traffic, so there’s no data for the time when nothing went through the proxy, and the line breaks there.

Hover over the chart to see the time, the latency and how many connections there were at that moment. Below the chart is the summary for the period: Typical, Spread, the share of connections that were Error-Free, and the number of Connections.

The history is kept for 30 days. If you change the proxy’s server, port or type, the history starts over: it’s a different server now. Changing the login or password doesn’t reset it.

Error messages

If the check fails, a message appears instead of the result. Monitor shows the same messages for connections that couldn’t be made through the proxy.

MessageWhat it meansWhat to do
The proxy didn’t answer in timeThe proxy didn’t answer within 10 seconds during a check, or within 15 seconds for an app’s connection. In that time, an app’s connection makes up to three attempts: if the previous one stalls, a new one starts after 1.5 and after 4 seconds.Check the server and port. Make sure the server is running and the port isn’t closed by a firewall on it.
Couldn’t connect to the proxy: …macOS couldn’t connect to the server. After the colon is the reason from macOS. Connection refused means nothing is running on this port.Check Server and Port. Check that the Mac is online.
Couldn’t connect to the proxy: TLS: the proxy’s certificate failed validationHTTPS: the server’s certificate doesn’t fit.The Server field must contain the domain name the certificate was issued for, not the IP. The certificate must not be expired or self-signed.
Couldn’t connect to the proxy: TLS: TLS error (number)An encrypted connection couldn’t be set up.Most often, the HTTPS type is selected, but the server doesn’t use TLS on this port. Try HTTP or SOCKS5.
The proxy closed the connectionThe server dropped the connection in the middle of the handshake.Often it’s the wrong proxy type, for example HTTP instead of SOCKS5, or the wrong port.
Proxy protocol error: …The server didn’t answer the way a proxy of the selected type does.Check Type and Port. If the text after the colon is “couldn’t read the IP check service’s reply”, none of the check services gave an answer Routekeeper could read. Check again later.
Server … not found: DNS has no such nameThe name in the Server field doesn’t exist: both the network’s DNS and DNS over HTTPS said so.Check Server for a typo or an expired domain. For a DuckDNS domain, check that it wasn’t deleted.
Couldn’t find the address of server …: this network’s DNS doesn’t resolve it, and DNS over HTTPS is unreachableYour network’s DNS won’t give out the server’s address, DNS over HTTPS is unreachable from this network, and there’s no remembered address.Enter the Server IP address in the proxy card, see below.
SOCKS5: the proxy requires a login and passwordNo login is set.Enter the login and password.
SOCKS5: wrong login or passwordThe proxy didn’t accept the login or password.Copy them again, without spaces at the start or end.
SOCKS5: the proxy accepted no authentication methodThe proxy accepted neither sign-in without a password nor sign-in with a login and password.If no login is set, set one. If one is set, the proxy requires a sign-in method that Routekeeper doesn’t support.
SOCKS5: connection not allowed by the proxy’s rules, SOCKS5: host unreachable and other replies after “SOCKS5:”Sign-in worked, but the proxy didn’t open a connection to the check service.The proxy may forbid some addresses or ports. The check goes to port 80.
HTTP: the proxy requires authentication (407)There’s no login or password, they’re wrong, or the proxy requires Windows sign-in (NTLM, Kerberos).Check the login and password. Routekeeper supports only login-and-password sign-in; see Work proxy.
The HTTP proxy answered 403 Forbidden, and other codesThe proxy refused the connection.Office proxies often allow tunnels only to port 443, while the check goes to port 80. In that case, HTTPS sites will work even though the check fails.
No connection to the network extensionThe network extension runs the check, and it isn’t answering.See Reinstalling and stopping the extension.

Other Routekeeper messages and what to do about them are in Troubleshooting.

How Routekeeper finds the server’s address

If the Server field holds a name, Routekeeper has to find the server’s address. Some networks won’t give it out: a corporate VPN doesn’t know outside names, an ISP filters DNS. So Routekeeper asks for the address over DNS over HTTPS at Cloudflare, Google, AdGuard and Control D, reaching them by IP, so the network’s DNS isn’t needed for this. The address it finds is remembered: the next connection starts at once, and a fresh address is looked up in the background. If DNS over HTTPS is unreachable too, Routekeeper asks the network’s DNS, as before.

If none of this works on your network, enter the Server IP address. An HTTPS proxy’s certificate is still checked against the name in the Server field, so leave the name as it is.

A proxy on your own server

A proxy that Routekeeper set up with the Your Own Server… wizard gets a Server block at the bottom of its card. Routekeeper logs in to the server with its own key from the keychain, does one thing and logs out.

  1. Whether Caddy with the proxy is running on the server. If it says stopped, click Reinstall.
  2. How many addresses fail2ban is currently blocking for guessing the SSH password.
  3. Check Server logs in to the server and refreshes these rows. Routekeeper also does this itself when the card opens, if the last check is more than six hours old.
  4. Runs the installation again with the same domain. If this version of Routekeeper has a newer setup, the button says Update Server, and the row An update for the server setup is available appears above. The proxy’s login and password don’t change.
  5. In the menu: Change Proxy Password…, Turn Off Password Logins to the Server…, Save SSH Key…, Remove Proxy from the Server… and Forget Server….
A diagram of the bottom of the card of a proxy that Routekeeper set up on a server. The data is made up.
ButtonWhat it does
Check ServerFinds out whether the proxy is running on the server, when the certificate expires and how many addresses fail2ban is blocking. Caddy renews the certificate itself, a month before it expires.
Reinstall or Update ServerRuns the installation again with the same domain. This fixes a stopped proxy and brings Caddy and the settings up to the version in this Routekeeper. The login and password don’t change.
More → Change Proxy Password…Creates a new login and password on the server and saves them in this proxy right away. Routes and rules stay on it. If this proxy is set up anywhere else, the old password stops working there.
More → Turn Off Password Logins to the Server…The server starts accepting only keys for SSH. See Password logins to the server.
More → Save SSH Key…Saves the private key Routekeeper logs in to the server with to a file. With it you can log in to the server from Terminal: ssh -i file root@IP.
More → Remove Proxy from the Server…Removes Caddy, the certificate, the login and the password on the server. The server and everything else on it stay. In the dialog you choose whether to delete the proxy in Routekeeper too.
More → Forget Server…Routekeeper deletes its key for this server and stops managing it. The proxy keeps working on the server and in Routekeeper; the Server block disappears.

If the block shows an error, the What to do about it link under it leads to the right part of Your own proxy server.

With password logins to the server off, Routekeeper’s key may be the only one the server accepts. Forget Server… and deleting the proxy delete this key from the keychain, so save it first: More → Save SSH Key….

Several proxies

You can add as many proxies as you like. Each app, service and rule chooses its own: the route menu has a Through Proxy section with all proxies by name. For example, the browser goes through “Amsterdam”, and the work messenger through “Office”. How to choose a route is described in An app’s route.

If two proxies have the same name, the menu adds the type and port to them. It’s clearer to give them different names.

The main proxy

The main proxy is the one that most enabled routes and rules go through. If there are none, the first proxy in the list is the main one. The main proxy:

A number like “+1” next to it in the sidebar means that some rules go through other proxies.

Deleting a proxy

Select the proxy in the list and click − below the list, or press Delete. You can also right-click the proxy and choose Delete…. Routekeeper asks you to confirm and tells you how many rules go through this proxy. Deleting can’t be undone: ⌘Z won’t bring the proxy back, and its login and password are deleted with it.

Routes and rules that went through the deleted proxy are turned off.

If the Your Own Server… wizard set up the proxy, the dialog has two buttons: Delete, Also from the Server removes the proxy from the server and then deletes it in Routekeeper; Delete Only from Routekeeper leaves the proxy running on the server, and Routekeeper forgets the server and its key.

A turned-off rule has no effect. Apps that went through the deleted proxy will follow the other rules and the mode. In Proxy Only mode, this means they go direct, with your real IP, and these connections won’t show up in Leaks. So first move the routes to another proxy, and only then delete.

Switching to another proxy

When a proxy stops working, or you’re moving to another server, you can move routes all at once, without changing each app. You need at least two proxies for this.

WhereWhat is moved
Overview → Routes → the ⋯ button in the proxy’s row → Move Routes ToOnly this proxy’s routes and rules.
Overview → the row of a proxy that isn’t answering → Move to “…”Only this proxy’s routes and rules. Routekeeper suggests a proxy that answered at the last check.
The panel at the bottom of the sidebar → the Proxy row → Move all apps toAll enabled routes and rules that go through any proxy.
The menu of the menu bar icon → Proxy for all appsThe same as in the sidebar. The list appears in the menu only when there are two or more proxies.
  1. Choose the proxy to move to.
  2. Routekeeper asks: Move to “…”? The question says what will move and from where. If the rules went through different proxies, Routekeeper warns that this split will be lost. It also warns you if the chosen proxy didn’t answer at the last check. Click Move. In the menu of the menu bar icon, the question appears right in the menu.
  3. After the move, a line like “5 rules moved” and an Undo button appear for 10 seconds. The button returns the moved rules to their previous proxies. Later, ⌘Z in the Routekeeper window does the same.

Only enabled routes and rules with the Through Proxy action are moved. Direct, Block and turned-off rules stay as they were. Connections that are already open stay on the previous proxy until the app reconnects.

If the proxy is down

By default, connections that should go through the proxy are dropped when the proxy fails. The app shows an error or “no network”, but connections don’t go direct, and your real IP isn’t revealed.

What you’ll see:

What to do: move the routes to another proxy, as described above, or wait. The main proxy is rechecked once a minute. As soon as the server answers, new connections go through it again.

If it matters more to you that apps work than that they go through the proxy, turn on Settings → Network → If the proxy is down, go direct. It’s off by default. With this setting, a connection that couldn’t go through the proxy goes direct: sites see your real IP. Monitor shows these connections as direct, and they won’t show up in Leaks. A ready-made scenario is in the recipe The proxy stopped answering.

Details: what a failure looks like to the app

Routekeeper accepts the app’s connection right away and connects to the proxy at the same time. This way, browsers don’t open extra backup connections. If the proxy fails or doesn’t answer within 15 seconds, the app’s connection is dropped. With the “go direct” setting, Routekeeper connects to the site’s address itself at that moment. UDP blocking doesn’t depend on the proxy’s state.

Local client: sing-box, Xray, Clash

If you already use a client such as sing-box, Xray, Clash or a program based on them, Routekeeper can send chosen apps into it. The client still keeps the connection to your server over its own protocol, and Routekeeper decides which apps go into the client.

App → Routekeeper → SOCKS5 127.0.0.1 → client → your server → site
  1. In the client’s settings, find the local proxy port. It may be called SOCKS port, mixed port or inbound, for example 1080 or 7890.
  2. In the client, turn off the system proxy (System Proxy, Set as system proxy) and TUN mode (TUN mode, Enhanced mode, VPN mode). With the system proxy, apps go to the client by themselves, and Routekeeper no longer controls them. TUN captures all of the Mac’s traffic, like a VPN, and gets in Routekeeper’s way; see Limitations.
  3. In Routekeeper, add a proxy: Type SOCKS5, Server 127.0.0.1, Port the client’s port. You usually don’t need a login and password. You can copy and paste the line socks5://127.0.0.1:7890 with your own port in it.
  4. Leave both toggles on. With DNS through proxy, the client gets site names and looks up addresses according to its own settings.
  5. Click Check. The IP in the result should be your server’s address, not your home one.
  6. Choose the apps that will go through the client: Apps and services.

Don’t send the client itself through the proxy. Its connection to the server would come back to it, making a loop, and everything on this proxy would stop working. If you have the rule “Any App · any address → Through Proxy”, add the client to Apps with the Direct route: a rule for a specific app wins over a rule for any app; see Which rule wins.

In Ask and Block All modes, the client must be explicitly allowed to connect to the server. Add it to Apps with the Direct route, or answer Allow with the Forever duration in the prompt. Otherwise, the client’s connection to the server will be blocked or will wait for an answer, and all apps on this proxy will be left without a network. In Proxy Only and Silent modes with default settings, you don’t need to do anything. More about modes: Firewall modes.

If the client is off or has frozen, apps on this proxy are left without a network, and they don’t go direct. A ready step-by-step setup is in the recipe On top of sing-box, Xray or Clash.

Details: localhost, UDP and the client’s HTTP port
  • Connections to the address and port of any proxy in the list always go direct; rules don’t apply to them. Connections to 127.0.0.1 and ::1 are covered by built-in rules; see The list of rules.
  • Through SOCKS5, Routekeeper passes only TCP, even if the client supports UDP. So the Block UDP and QUIC toggle is needed here too.
  • If the client offers only an HTTP port, choose the HTTP type. A mixed port accepts both SOCKS5 and HTTP.

Work proxy

In an office, the IT department usually gives you the proxy: an address, a port (often 3128 or 8080) and maybe a login and password.

  1. Add a proxy: Name “Office”, Type HTTP, Server and Port from the IT department, Login and Password if needed. Choose the HTTPS type only if the IT department said the proxy accepts TLS.
  2. Click Check. If the answer is “The HTTP proxy answered 403 …”, read the item about port 80 below.
  3. Decide what will go through the work proxy:
    • whole apps, for example a work messenger: the “Office” route in Apps. Such a route leaves addresses on your local network and VPN subnets direct;
    • company addresses from any app: the rule “Any App · *.corp.example → Through Proxy ‘Office’” in Rules. For internal networks, add a rule with a subnet, for example 10.0.0.0/8. Such a rule wins over an app’s route: the browser goes through your usual proxy, and company sites through the office one.

Limitations:

A ready-made scenario is in the recipe Work proxy for internal addresses.

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