Split-tunneling vpn runelite

Trustars

Dears,

While using vpn and having added runelite to the split-tunneling my runelite client won't even open. When you click the icon to start the application it completly does nothing at all.

When i turn off the vpn my game loads as intended.
This means no issue with the game itself

I've also already added the "-Djava.net.preferIPv4Stack=true" code to the config file.

And also activated IPV4 in the configuration

Alexandru_BD

Hi,

This is a tricky one. I think it's most likely a VPN routing or process-exclusion problem during launch. My theory is that the excluded app is not the only process involved. RuneLite uses a launcher and separate client/JVM behavior, and its own docs show distinct launcher/client logging and launcher arguments, which is consistent with a multi-stage startup rather than one simple executable. So, if anything was missed, for example a shortcut, config file target, or only one stage of the launcher chain, the traffic may still be caught by the VPN.

A few likely causes:

• The executable added to Split Tunneling may not be the actual process handling the connection
• RuneLite may spawn a secondary Java/client process that is still going through the VPN
• DNS or gateway routing may still be affecting startup even though split tunneling is enabled

Things to try:

• Remove the current split-tunneling rule and add the actual RuneLite .exe from its install folder again, not a shortcut. Like you may have noticed, the VPN only accepts real .exe / .com executables for this feature.
• If RuneLite is launched through another launcher or Java process, add that executable too if available.
• Test with a different VPN server, ideally your own country / nearest region.
• Change Windows DNS to a public resolver temporarily and retest.
• If it still fails, try Bitdefender’s Windows workaround of adding your router IP as the default gateway for the VPN adapter.

Check RuneLite logs in %userprofile%.runelite\logs and look at launcher.log / client.log for errors like bootstrap fetch failures, timeouts, or connect exceptions.

Regards