Open PacketShepard opened 5 years ago
Anyone there?
Hi BourbonZawa,
I made a fork to fix the issue. It's under PacketShepard/docker-qBittorrentVPN. However, the main trick to get around this issue -- after resolving DNS -- is to remove persist-tun from your openvpn configuration. You'll also want to make sure you add cap_add: - NET_ADMIN to your docker-compose / docker cmd as well. There's one other root change needed on synology, but that should get it.
PS
On Fri, Mar 5, 2021 at 10:23 AM BourbonZawa notifications@github.com wrote:
I am currently having the same issue, same synology 918+ as well. Did you ever resolve this? I could use a little insight into how you did.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MarkusMcNugen/docker-qBittorrentvpn/issues/19#issuecomment-791487629, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAHGHEXNCH4HGQWCZXN76BTTCDZN5ANCNFSM4G7ZJ6TA .
Thank you PacketShepard
Hi Markus,
I'm seeing an issue where OpenVPN connects and works fine for days or weeks with qBittorrent, but one OpenVPN reset fails indefinitely from connection loss. It appears that the iptables rules set after the first OpenVPN run are blocking DNS to the configured servers. On OpenVPN service restart, this causes name resolution for the remote VPN to fail continuously. See the logs below.
Can you add an outbound rule in iptables for UDP/53 using the configured DNS servers under the NAME_SERVERS variable? Or just open UDP/53 outbound to any so this won't fail?
qBittorrentvpn_1 | Tue March 18 10:50:16 2016 Connection reset, restarting [0] qBittorrentvpn_1 | Tue March 18 10:50:16 2016 SIGUSR1[soft,connection-reset] received, process restarting qBittorrentvpn_1 | Tue March 18 10:50:16 2016 Restart pause, 5 second(s) qBittorrentvpn_1 | Tue March 18 10:50:41 2016 RESOLVE: Cannot resolve host address: vpn.example.com: Temporary failure in name resolution qBittorrentvpn_1 | Tue March 18 10:51:01 2016 RESOLVE: Cannot resolve host address: vpn.example.com: Temporary failure in name resolution qBittorrentvpn_1 | Tue March 18 10:51:26 2016 RESOLVE: Cannot resolve host address: vpn.example.com: Temporary failure in name resolution qBittorrentvpn_1 | Tue March 18 10:51:51 2016 RESOLVE: Cannot resolve host address: vpn.example.com: Temporary failure in name resolution qBittorrentvpn_1 | Tue March 18 10:52:16 2016 RESOLVE: Cannot resolve host address: vpn.example.com: Temporary failure in name resolution qBittorrentvpn_1 | Tue March 18 10:52:41 2016 RESOLVE: Cannot resolve host address: vpn.example.com: Temporary failure in name resolution qBittorrentvpn_1 | Tue March 18 10:53:06 2016 RESOLVE: Cannot resolve host address: vpn.example.com: Temporary failure in name resolution qBittorrentvpn_1 | Tue March 18 10:53:31 2016 RESOLVE: Cannot resolve host address: vpn.example.com: Temporary failure in name resolution
Thank you for your help and putting this great container together.