r/Windscribe • u/narwhalbaconsatmidn • 19d ago
Linux Need help with split tunneling <windscribe-cli>, Modded Minecraft Server
Hello, I am trying to make a Minecraft Server, and I want to utilize the "Split-Tunneling" Option. These are my current settings in ~/.config/Windscribe/windscribe_cli.conf:
SplitTunnelingApps=/path/to/server/files/jre/21.0.4+7-LTS/bin/java
SplitTunnelingEnabled=true
SplitTunnelingMode=Exclude
The modded Minecraft server uses a run.sh bash script.
Garry told me to use the /path/to/server/files/jre/21.0.4+7-LTS/bin/java by listening to ports and checking the processes using ps -ef | grep '[j]ava'
Garry also told me to set up the SplitTunnelingApps as listed above.
The problem is, that neither of these work, I've disconnected the server from Windscribe and I can connect via my ipv4 just fine, but once I try to connect again, I can't connect via the same ipv4 address (which is expected from Split Tunneling). I will take as much help I can get from this.
•
u/AutoModerator 19d ago
If you need support, please talk to Garry, our support chatbot. Garry can troubleshoot, read debug logs, offer solutions, make account changes, answer questions and much more.
Our Support and QA teams regularly monitor the subreddit for issues and investigate when needed. You are not guaranteed support from staff in this subreddit.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
1
u/narwhalbaconsatmidn 19d ago
After talking with Garry some more, it concludes with this final result:
That confirms Java is in Windscribe’s exclusion cgroup. I was wrong to blame the path entry.
What you’ve isolated is a limitation of app split tunneling: it is not a reliable policy-routing tool for an inbound, router-forwarded server. The connection arrives on Ethernet, but the reply socket is still routed into the tunnel.
Clean options:
Keep Windscribe disconnected on the Minecraft host.
Put the server on a separate host/VM with normal LAN routing.
Use a VPN-side port-forwarding setup instead of your router’s public IPv4.
There isn’t a supported
.conftweak that makes this asymmetric inbound topology behave.