vopono icon indicating copy to clipboard operation
vopono copied to clipboard

i can't connet multiple programs with daemon

Open NextWork123 opened this issue 1 month ago • 1 comments

Hello, i'm trying to use the vopono daemon but i don't have so much luck. I want to put under vpn my qbittorrent session and amule but qbittorrent i can't access to my webui and amule seem not working. As command i'm using that: /usr/bin/vopono -v exec -k -f 8080 -f 4711--allow-host-access --custom /home/next/vpn/vpn-proton.conf --protocol wireguard --custom-port-forwarding protonvpn /usr/bin/qbittorrent-nox what i'm missing? i put too --allow-host-access but seem not working

Best Regards, NextWorks

NextWork123 avatar Nov 10 '25 23:11 NextWork123

This should work okay with just -o to open the port to be accessible from the host. I just tested it with ProtonVPN and a fileserver and it worked for me.

However, note that since you will likely need two different ProtonVPN port forwardings (one for torrents, one for amule - for their P2P protoctols) - you should force the applications to run in different vopono namespaces so you get two different connections with different ports (e.g. use different country configs).

E.g. for qbittorrent:

/usr/bin/vopono -v exec --custom /home/next/vpn/vpn-proton.conf --protocol wireguard --custom-port-forwarding protonvpn -o 8080 /usr/bin/qbittorrent-nox

With the above you can now access the webserver at http://10.200.1.2:8080 - adding -f 8080 forwards that to the host so you can access it at http://localhost:8080 - but it's not really necessary (unless amule and qbittorrent need to communicate with eachother). --allow-host-access is used for the other way around, when you are hosting a service on the host that you want the network namespace to access.

Critically you must note down the forwarded port that ProtonVPN gives you - it's at the start of the vopono output, e.g.:

2025-11-15T11:28:11.234Z DEBUG vopono > Connected to daemon, forwarding command.
Port Forwarding on port 60000

And that is the port you need to specify as the open port to use for the actual P2P connections.

In theory amule should be the same

/usr/bin/vopono -v exec --custom /home/next/vpn/vpn-proton2.conf --protocol wireguard --custom-port-forwarding protonvpn -o 4711 /usr/bin/amule

But you will need to use another config file to get a different port forwarding so you can get two ports from ProtonVPN. Also note if it is the second namespace then it will be accessible at http://10.200.2.2:4711

Note if amule does not allow you to specify the port for P2P connections then you can work-around it with a local proxy, see the Plex example here for how to do this: https://github.com/jamesmcm/vopono/blob/master/USERGUIDE.md#plex---port-forwarding.

Also remember when using the daemon, you can read the logs with journalctl:

$ sudo journalctl -b | rg vopono
Nov 15 11:25:26 spaceship vopono[832]:  2025-11-15T10:25:26.378Z INFO  vopono > Starting vopono in daemon mode.
Nov 15 11:25:26 spaceship vopono[832]:  2025-11-15T10:25:26.378Z INFO  vopono::daemon > Daemon listening on /run/vopono.sock
...

jamesmcm avatar Nov 15 '25 11:11 jamesmcm