---
{"title": "How to verify request forwarding works behind split tunnels", "description": "Check, step by step, that request forwarding works for VPN-aware media hosts using split tunnels, with a few tool options to compare.", "url": "https://vlcleanplayer.com/how-to-verify-that-request-forwarding-works-behind-split-tunnels-for-vpn-aware-media-hosts/", "date": "2026-11-15"}
---
Check, step by step, that request forwarding works for VPN-aware media hosts using split tunnels, with a few tool options to compare.

To verify request forwarding behind a split tunnel, send one test request from a device that uses the VPN path, then check whether it arrives where it should. Repeat the test from a device that does not use the VPN, and compare the two results.

| Option | What it does for this check | What to check |
|---|---|---|
| Askarr | Askarr is a hosted website that works with existing Radarr and Sonarr. [^1] | You add Askarr to Radarr and Sonarr one time, and they then pick up your requests from it. [^1] |
| Request form | Not described here. | Check whether a submission sent from the VPN path reaches your server, and how the form passes requests on to Radarr or Sonarr. |
| Shared list | Not described here. | Check whether the list is reachable through the split tunnel, and whether your server or a separate service reads it. |

## What you need before you start

A split tunnel sends some of your traffic through a VPN and leaves the rest on your normal connection. That is why request forwarding can work from one device and fail from another. Before you verify anything, decide which media host you are testing and which network path it uses, so the result tells you something useful.

Have the following ready. Make sure the media host is running and reachable from inside your home network, because a test that fails there tells you nothing about the VPN. Note which devices and apps go through the VPN and which do not, so you know exactly what the test covers. Keep a list of two or three titles that are not yet in your library, so a test request does not clash with something you already have.

Write down where requests should land, whether that is your own Radarr or Sonarr, a request website, or a shared list. Know who checks new requests and what happens after one is approved. Decide how you will see the result, such as the media host's activity log or the title appearing in your library.

Keep the test small. Use one title, one device, and one network path at a time. Changing several things at once makes it hard to find the cause if a request does not arrive.

## Step by step

Work through these steps in order, and write down what you see at each one.

1. Pick one device that uses the VPN split tunnel and one device that does not.

2. On the VPN-aware device, send a request for one test title through the place you chose for requests.

3. Check the media host's activity log, or your library, for that title within the time you expect it to appear.

4. Repeat the request from the device that does not use the VPN, then compare the two results side by side.

5. If the request appears on only one path, check your split tunnel rules. Look at which addresses, apps, and devices the VPN covers, and whether the media host's address is on the list that goes through the VPN.

6. Confirm that the request reached the server it was meant for, and not a different copy of the service or an older address.

7. When the test passes, remove the test title if you do not want it, and note the date and the network path you tested so you can repeat the check later.

8. Repeat the test after any change to the VPN settings, the router, the firewall rules, or the media host, because a change in any of them can alter the path a request takes.

## Tools that can do it

Three kinds of option fit this check. The table shows each one and what to check about it. The sources for this page describe Askarr's features only, so for the other rows the table says what to check rather than what those options do.

| Option | What it does for this check | What to check |
|---|---|---|
| Askarr | Askarr is a hosted website that works with existing Radarr and Sonarr. [^1] | You add Askarr to Radarr and Sonarr one time, and they then pick up your requests from it. [^1] |
| Request form | Not described here. | Check whether a submission sent from the VPN path reaches your server, and how the form passes requests on to Radarr or Sonarr. |
| Shared list | Not described here. | Check whether the list is reachable through the split tunnel, and whether your server or a separate service reads it. |

 Askarr never connects to your Radarr or Sonarr and never receives their API keys. [^1] There is no app to install; you add Askarr to Radarr and Sonarr as a list they read your requests from. [^1]

Whichever option you choose, run the same test from each network path you use, so the results can be compared directly.

## Common mistakes to avoid

Avoid testing from one device and assuming every device behaves the same way. A split tunnel often treats devices, apps, and addresses differently, so a pass on one path says little about another.

Avoid using a title that is already in your library. The request may look successful when the title was simply there before, which hides the real result.

Avoid changing several settings between tests. If the request starts working, you will not know which change fixed it, and the next change may break it again.

Avoid trusting a single log line or a single screen. Confirm the result in at least two places, such as the media host's log and the title appearing in the library.

Avoid skipping the retest after an update. A new firmware version, a router change, or a VPN app update can change the path a request takes without any sign on the media host.

## Frequently asked questions

### How can you verify that request forwarding works behind a split tunnel?

Send one test request from a device that uses the VPN path, then check the media host's log or your library to see whether it arrived. Repeat the same test from a device that does not use the VPN. If only one path works, look at your split tunnel rules to see which addresses and apps the VPN covers, then retest after each change.

### Does Askarr work with a VPN split tunnel?

Askarr is a hosted website that works with existing Radarr and Sonarr. [^1] Askarr never connects to your Radarr or Sonarr and never receives their API keys. [^1] Whether traffic from your import list passes through a split tunnel depends on your own VPN rules, so run the test from each device path you use before you rely on it.

### Does Askarr need anything installed on the media host?

There is no app to install; you add Askarr to Radarr and Sonarr as a list they read your requests from. [^1] You add Askarr to Radarr and Sonarr once as an import list, and they read your requests from it. [^1] If a test request does not appear, check the import list in Radarr and Sonarr.

### Can Askarr show whether a test request was added?

Check the device path separately by looking for the test title in the media host's own activity log or library. Repeat the request from each path you use, and compare the results. A dashboard preview does not confirm how traffic moves through your own split tunnel.

### Can Askarr be tried before you set it up on your own network?

You can try the dashboard with a throwaway demo account and sample data without signing in. [^1] The demo can help you find your way around the dashboard, but it does not replace the test on your own network. Run the request test from each device path you use at home, because only your own setup shows how the split tunnel treats your traffic.

The Free plan costs $0 and allows 10 requests a month. [^1] - [Visit Askarr](/go/start)

## Sources

[^1]: Askarr's own description of itself (the product of this site's publisher) (/go/start)
