# VPN with wireguard makes domain unreachable

**URL:** https://forum.yunohost.org/t/vpn-with-wireguard-makes-domain-unreachable/42201
**Category:** Support apps
**Tags:** wireguard\_client, english
**Created:** [May 5, 2026, 6:37am UTC](https://forum.yunohost.org/t/vpn-with-wireguard-makes-domain-unreachable/42201 "2026-05-05T06:37:26Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![artlog](https://forum.yunohost.org/user_avatar/forum.yunohost.org/artlog/32/12399_2.png) [@artlog](https://forum.yunohost.org/u/artlog)
#### Post date: [May 7, 2026, 6:47am UTC](https://forum.yunohost.org/t/vpn-with-wireguard-makes-domain-unreachable/42201/2 "2026-05-07T06:47:37Z")

</div>

HI @Daize

This whole topic is about using qbittorrent as a service with a VPN.

I would then first advice to see directly with bitorrent community [https://forum.qbittorrent.org](https://forum.qbittorrent.org) how to address such thing.

I don’t use qbittorrent so i won’t be able to give grounded by experience answers.

There is no easy thing as a VPN split per service.  
Wireguard is a kernel level feature so to control it this is through ip table and that’s not easy.  
Using allowedIPs defines destination network that will tunnel traffic.  
I guess that qtbittorent can contact any address, so there is no dedicated destination network for it. default is just ‘all’ ( 0.0.0.0/0 == all ).

Here we would like more a Source ip to be the selector of such traffic, that would be the ip address bound to qbittorrent.  
Even setting a dedicated address by service will require some setup, or even setting wireguard interface for this service.  
There is a topic related to this [Split Tunneling Wireguard Qbittorent](https://forum.yunohost.org/t/split-tunneling-wireguard-qbittorent/40772) but solution seems to not be working very well.

To go back to original quesiton, getting wireguard privacy with qbittorent was addressed using docker by this project [GitHub - tenseiken/docker-qbittorrent-wireguard: Docker container which runs qBittorrent-nox (headless) client while connecting to WireGuard. · GitHub](https://github.com/tenseiken/docker-qbittorrent-wireguard)

didn’t dig in whole details but for what i see

the Qbittorrent conf explicitly set wireguard interface as its address :

> Session\Interface=wg0

there is a bunch of ip table changes [docker-qbittorrent-wireguard/qbittorrent/iptables.sh at master · tenseiken/docker-qbittorrent-wireguard · GitHub](https://github.com/tenseiken/docker-qbittorrent-wireguard/blob/master/qbittorrent/iptables.sh)

there is some nat portforwarding specific script [docker-qbittorrent-wireguard/qbittorrent/portfwd.sh at master · tenseiken/docker-qbittorrent-wireguard · GitHub](https://github.com/tenseiken/docker-qbittorrent-wireguard/blob/master/qbittorrent/portfwd.sh)

There might be docker related code that is fully irrelevant here, but in any case, this is not an easy task.

---

_[View the full topic](https://forum.yunohost.org/t/vpn-with-wireguard-makes-domain-unreachable/42201)._