Closed tiritibambix closed 2 years ago
Trigus42
commented
2 years ago What do you mean exactly by "it stopped working"? Are you not able to access the web UI, is it constantly restarting, ..?
Can you please provide the full log and your compose file or the docker command you used?
tiritibambix
commented
2 years ago Thank you for your answer.
I can access webui, but I got the error message "qBittorrent client is not reachable" after a few seconds. It won't download any torrent and gets frozen. It used to work very well.
The log I provided is the full log.
Here's my compose file
version: "3.3"
services:
qbittorrentvpn:
image: trigus42/qbittorrentvpn
container_name: qbittorrentvpn
privileged: true
environment:
- PUID=998
- PGID=100
- VPN_ENABLED=yes
- LAN_NETWORK=192.168.0.0/24
- NAME_SERVERS=1.1.1.1,1.0.0.1
ports:
- 8991:8080
volumes:
- /srv/.../QBittorentVPN/config:/config
- /srv/.../QBittorentVPN/downloads:/downloads
restart: unless-stoppedThis probably means that the container is constantly restarting. A full log should look like this:
Trigus42
commented
2 years ago You seem to be using a fairly recent image, but please try docker-compose pull to ensure that you use the newest one (the commits I just pushed should have nothing to do with your problem though).
tiritibambix
commented
2 years ago I tried qbt4.3.9-20211229. Still "qBittorrent client is not reachable".
Here's the full log. Sorry for the missunderstanding.
Trigus42
commented
2 years ago Unfortunately, I can't spot the problem in the log. I tried your compose file and it worked for me.
Did you try to recreate the container by running docker-compose down -v and docker-compose up -d?
Please set the environment variable DEBUG=yes, recreate the container and post the log.
The only things that come to my head, which could be causing this issue, are your VPN config, your VPN provider's servers or an unstable internet connection.
tiritibambix
commented
2 years ago I had to move earlier today. I'll have to report back tomorrow.
Thanks for your suggestions
Trigus42
commented
2 years ago Maybe the health check fails in spite of your connection actually working. I created an image with the health check disabled: trigus42/qbittorrentvpn:health_check_disabled.
To check if your connection is working, then run docker exec -it qbittorrent ping 8.8.8.8.
tiritibambix
commented
2 years ago Sorry for the late answer, had a complicated day x)
So, I took some time to run some tests and it appears that my internet connection as well as my VPN config / provider's servers are fine. I installed and ran TransmissionsOpenVPN and successfully connected and downloaded.
I also tried to run trigus42/qbittorrentvpn:latest on another machine and I have the same problem. I also tried to run earlier images (up to qbt4.3.7) with no luck.
Here are the logs right after a "qBittorrent client is not reachable":
Then, I read your answer.
I tried running trigus42/qbittorrentvpn:health_check_disabled. It does not ping.
Here are the logs:
That puzzles me. I can't remember doing anything to break it.
Trigus42
commented
2 years ago I also tried to run earlier images (up to qbt4.3.7) with no luck.
That's the next thing I would have suspected as I recently made some changes on the firewall, but then this shouldn't be the cause of your issue.
I've created another image trigus42/qbittorrentvpn:firewall_disabled with the firewall and health check disabled.
If this doesn't work, then there isn't much left that could cause your issue. Maybe you can bash into the container (docker exec -it qbittorrent bash) and try investigating the problem yourself.
If none if this works, maybe you should switch to OpenVPN.
Edit: With most VPN providers you can renew your credentials. If you want to, you can upload your Wireguard config here for me to try it but that's entirely on you.
tiritibambix
commented
2 years ago Thank you.
I tried trigus42/qbittorrentvpn:firewall_disabled but it doesn't ping either.
I tried swithing to openvpn, but I got an error:
[ERROR] VPN_PORT not found in /config/openvpn/openvpn.ovpn, exiting...
I wrote to my vpn provider to get that information.
In the meantime, as I'm curious, I uploaded my Wireguard config to your NC.
PS.: totally different subject, but what plugin do you use in NC to enable public drop of files like this ?
Trigus42
commented
2 years ago It's definitely your VPN config. I've tried it with your config (with the firewall disabled) and it didn't work, while with my config it works flawlessly. This is what happened when I tried to ping 1.1.1.1 with your config enabled:
bash-5.1# tcpdump -n
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
12:46:39.711754 IP 172.19.0.2.44641 > 195.154.222.168.51820: UDP, length 148
12:46:44.030716 IP 172.19.0.1.138 > 172.19.255.255.138: UDP, length 213
12:46:44.030737 IP 172.19.0.1.138 > 172.19.255.255.138: UDP, length 203
12:46:44.833770 IP 172.19.0.2.44641 > 195.154.222.168.51820: UDP, length 148
12:46:49.953888 IP 172.19.0.2.44641 > 195.154.222.168.51820: UDP, length 148
12:46:55.073908 IP 172.19.0.2.44641 > 195.154.222.168.51820: UDP, length 148
^C
6 packets captured
6 packets received by filter
0 packets dropped by kernel
bash-5.1# tcpdump -n -i wg1
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on wg1, link-type RAW (Raw IP), snapshot length 262144 bytes
12:51:05.907619 IP 10.102.69.0 > 1.1.1.1: ICMP echo request, id 9965, seq 1, length 64
12:51:06.913363 IP 10.102.69.0 > 1.1.1.1: ICMP echo request, id 9965, seq 2, length 64
12:51:07.937781 IP 10.102.69.0 > 1.1.1.1: ICMP echo request, id 9965, seq 3, length 64
12:51:08.961371 IP 10.102.69.0 > 1.1.1.1: ICMP echo request, id 9965, seq 4, length 64
^C
4 packets captured
4 packets received by filter
0 packets dropped by kernelThis is what it looks like on my host OS:
[root@PC ~]# tcpdump -n host 195.154.222.168
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on wlp37s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
13:56:32.737636 IP 192.168.178.32.44641 > 195.154.222.168.51820: UDP, length 148
13:56:37.858155 IP 192.168.178.32.44641 > 195.154.222.168.51820: UDP, length 148
13:56:42.977495 IP 192.168.178.32.44641 > 195.154.222.168.51820: UDP, length 148
13:56:48.097938 IP 192.168.178.32.44641 > 195.154.222.168.51820: UDP, length 148
^C
4 packets captured
4 packets received by filter
0 packets dropped by kernelSo the packets are actually leaving the container.
It seems like your VPN provider's server just doesn't respond.
That's what you have to select when sharing a folder in Nextcloud: https://user-images.githubusercontent.com/59501676/147824715-c3a4c69f-9732-468e-b4ad-efe19ef45e63.png)
Trigus42
commented
2 years ago I tried swithing to openvpn, but I got an error: [ERROR] VPN_PORT not found in /config/openvpn/openvpn.ovpn, exiting...
There should be a remote line in your OpenVPN config like this:
remote vpnserver.com 443
The script tries to extract the port (443)
tiritibambix
commented
2 years ago I gave up on openvpn because there is no port specified in the original config, and 443 doesn't work. I reset my wiregard config (...AGAIN xD) and now it looks like it's working......
I'll report back in a couple of days to confirm it is working and close this issue. In the meantime, thank you very very much for your patience and help.
Have a wonderful new year's eve :)
And thank you for that :
That's what you have to select when sharing a folder in Nextcloud: https://user-images.githubusercontent.com/59501676/147824715-c3a4c69f-9732-468e-b4ad-efe19ef45e63.png)
addiebarron
commented
2 years ago Hi all, I'm having the same issue as described above, more details & logs in this (possibly related?) issue: #12
Trigus42
commented
2 years ago I'll report back in a couple of days to confirm it is working and close this issue. In the meantime, thank you very very much for your patience and help.
Seems like it's working. If not, feel free to reopen the issue
tiritibambix
commented
2 years ago I'm sorry, I didn't take the time to follow up. Apparently, my VPN provider may be facing random failures. Rarely but sometimes. This one time I contacted you was a huge one. No notice on their part.
Anyway, it's working great now. Thanks again for your time, patience and work :)
PS: for anyone interested, I use vpnunlimited set to Paris
Hello.
I've been using your image for a couple of months and I love it :)
But suddenly it stopped working. I can't remember doing anything to mess things up.
Here's my log. Any help would be greatly appreciated.