just tried clicking "down" and "stop" under the "Files
It's down, Pull, up
just tried clicking "down" and "stop" under the "Files
It's down, Pull, up
Select the file in the files tab.
Press the down button.
Press the Up button.
That's it but assumes you are using the latest tag.
Also, force reload the page or you will probably see the old cached version of the Help | About page.
It's down, Pull, up
Whoa... where's this headed...
Alles anzeigenSelect the file in the files tab.
Press the down button.
Press the Up button.
That's it but assumes you are using the latest tag.
Also, force reload the page or you will probably see the old cached version of the Help | About page.
Hmm. I did that, see this video:
This is my yaml file:
---
services:
qbittorrentvpn:
image: gderf/qbittorrentvpn:latest
container_name: qbt
cap_add:
- NET_ADMIN
environment:
#- VPN_ENABLED=yes
- VPN_ENABLED=no
#- VPN_TYPE=wireguard
- ENABLE_SSL=no
- PUID=${PUID}
- PGID=${PGID}
- TZ=${TZ}
- LAN_NETWORK=192.168.1.0/24
- NAME_SERVERS=8.8.8.8,8.8.4.4
- UMASK=022
- HEALTH_CHECK_HOST=one.one.one.one
- HEALTH_CHECK_INTERVAL=30
- HEALTH_CHECK_SILENT=1
- HEALTH_CHECK_AMOUNT=10
- RESTART_CONTAINER=yes
ports:
- 8080:8080/tcp
- 8999:8999/tcp
- 8999:8999/udp
volumes:
- ${APPDATA}/qbittorrentvpn:/config
- ${DATA}/Qbittorrentdownloads:/downloads
- ${DATA}/Films:/films
- ${DATA}/Tv-series:/tv-series
restart: unless-stopped
Alles anzeigen
Any idea what's missing?
(I understand the above comments that Pull is **not** to be used?)
From your video:
Down properly stops and deletes the container.
Up properly creates and starts the container.
The container log shows that the container is running and properly showing "[INFO] HEALTH_CHECK_AMOUNT is set to 10"
It won't hurt to Pull but shouldn't be needed when a container is deleted and recreated.
Have you cleared your browser cache or force reloaded the Qbittorrent page? If you have not done this you will be looking at a cached Help About screen showing the old version.
Have you cleared your browser cache or force reloaded the Qbittorrent page?
I did CTRL + F5. That's the "shock" you see. I assume that's what you meant with "force reloaded"?
I also tried using an incognito window, which (if I understand correctly) also works without cache?
root@NASLG2:~# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
lscr.io/linuxserver/nextcloud latest abad8a2438d8 4 weeks ago 910MB
ghcr.io/linuxserver/mariadb latest d9ee0c6e2188 4 weeks ago 333MB
linuxserver/swag latest 59a8f03c63a0 4 weeks ago 406MB
cloudflare/cloudflared latest b3df0030c73a 5 weeks ago 58.2MB
lscr.io/linuxserver/qbittorrent latest 6f9b60c3b2be 5 weeks ago 200MB
ghcr.io/linuxserver/swag latest ce9b4e61b6e7 5 weeks ago 405MB
lscr.io/linuxserver/plex latest 57586efd63e6 6 weeks ago 360MB
gderf/qbittorrentvpn latest 0eeb97811859 2 months ago 611MB
oznu/cloudflare-ddns latest a2e30a1da73e 3 years ago 36.3MB
Alles anzeigen
I see there are a few in there that aren't in use anymore, it seems? Also, it states "2 months ago" for your container, but that's maybe not unusual?
That is not the latest image. Pull it.
That is not the latest image. Pull it.
That worked.
It also didn't delete my admin password (which was what I was afraid of), so I guess there's no downside to pulling it again...?
If you set a user and password they will not be disturbed when upgrading the container or pulling the image. However, if you delete the configuration file qbittorrent.conf you will lose all the settings including the user and password.
The "speedtest" in this image is basically trash. I've been putting together a small vpn speed tester container thingy and I have been using this as the main program for about 200 samples... it's bad. I'm not implying I know of something better than this tool supplied by http://www.speedtest.net, because I don't. If anyone knows a good way to speed test, please post it.
Here's 3 results about 60 seconds apart.
It's EXTREMELY dependent upon the random speed test server you get. You can specify a server but, how do you now which is fastest to begin to pick? You'd think you'd simply pick a reference server and use that but, you get the same random results :-/.
Here's the rest of the info for those 3 results.
{
"servers": {
"102.130.49.233": {
"type": "result",
"timestamp": "2024-04-03T00:44:15Z",
"ping": {
"jitter": 0.782,
"latency": 262.296,
"low": 261.316,
"high": 262.91
},
"download": {
"bandwidth": 60901352,
"bytes": 761400128,
"elapsed": 15003,
"latency": {
"iqm": 391.978,
"low": 262.261,
"high": 520.569,
"jitter": 80.719
}
},
"upload": {
"bandwidth": 16897421,
"bytes": 172015509,
"elapsed": 11609,
"latency": {
"iqm": 391.27,
"low": 261.463,
"high": 524.432,
"jitter": 80.927
}
},
"packetLoss": 0,
"isp": "Cogent Communications",
"interface": {
"internalIp": "10.66.174.199",
"name": "za-jnb-wg-002",
"macAddr": "00:00:00:00:00:00",
"isVpn": false,
"externalIp": "154.47.30.152"
},
"server": {
"id": 23423,
"host": "za-jnb01.speed.misaka.one",
"port": 8080,
"name": "Misaka Network, Inc.",
"location": "Johannesburg",
"country": "South Africa",
"ip": "102.130.49.233"
},
"result": {
"id": "11e2ba5a-92b6-4e1f-bb40-0d0e4399081c",
"url": "https://www.speedtest.net/result/c/11e2ba5a-92b6-4e1f-bb40-0d0e4399081c",
"persisted": true
},
"filename": "./vpn_speed/confs_wireguard//za-jnb-wg-002.conf",
"epoch": 1712105055
},
"169.1.1.25": {
"type": "result",
"timestamp": "2024-04-03T00:46:28Z",
"ping": {
"jitter": 0.79,
"latency": 262.347,
"low": 261.499,
"high": 263.093
},
"download": {
"bandwidth": 32007990,
"bytes": 325670184,
"elapsed": 15012,
"latency": {
"iqm": 390.765,
"low": 261.424,
"high": 520.981,
"jitter": 81.104
}
},
"upload": {
"bandwidth": 20838909,
"bytes": 196168613,
"elapsed": 10909,
"latency": {
"iqm": 393.568,
"low": 262.641,
"high": 527.624,
"jitter": 81.277
}
},
"packetLoss": 0,
"isp": "Cogent Communications",
"interface": {
"internalIp": "10.66.174.199",
"name": "za-jnb-wg-002",
"macAddr": "00:00:00:00:00:00",
"isVpn": false,
"externalIp": "154.47.30.152"
},
"server": {
"id": 12286,
"host": "spdtest-teraco.afrihost.com",
"port": 8080,
"name": "Afrihost",
"location": "Johannesburg",
"country": "South Africa",
"ip": "169.1.1.25"
},
"result": {
"id": "f51bbdbd-4bd7-481c-b84f-304f12c8d046",
"url": "https://www.speedtest.net/result/c/f51bbdbd-4bd7-481c-b84f-304f12c8d046",
"persisted": true
},
"filename": "./vpn_speed/confs_wireguard//za-jnb-wg-002.conf",
"epoch": 1712105188
},
"41.79.23.8": {
"type": "result",
"timestamp": "2024-04-03T00:48:16Z",
"ping": {
"jitter": 0.744,
"latency": 262.963,
"low": 262.339,
"high": 263.42
},
"download": {
"bandwidth": 107492198,
"bytes": 1222545887,
"elapsed": 15015,
"latency": {
"iqm": 405.358,
"low": 261.301,
"high": 913.157,
"jitter": 81.351
}
},
"upload": {
"bandwidth": 24721530,
"bytes": 201014202,
"elapsed": 9703,
"latency": {
"iqm": 391.878,
"low": 262.812,
"high": 533.718,
"jitter": 80.948
}
},
"packetLoss": 0.3333333333333333,
"isp": "Cogent Communications",
"interface": {
"internalIp": "10.66.174.199",
"name": "za-jnb-wg-002",
"macAddr": "00:00:00:00:00:00",
"isVpn": false,
"externalIp": "154.47.30.152"
},
"server": {
"id": 23339,
"host": "zatjnb01-ookla1.syrex.co.za",
"port": 8080,
"name": "Syrex",
"location": "Johannesburg",
"country": "South Africa",
"ip": "41.79.23.8"
},
"result": {
"id": "5bd210fe-9ad6-4370-807a-115e375f718e",
"url": "https://www.speedtest.net/result/c/5bd210fe-9ad6-4370-807a-115e375f718e",
"persisted": true
},
"filename": "./vpn_speed/confs_wireguard//za-jnb-wg-002.conf",
"epoch": 1712105296
}
}
}
Alles anzeigen
Here are my results, about 180 seconds apart to the same server Odido - Amsterdam (id: 52365):
Download: 336.05 Mbps
Download: 352.48 Mbps
Download: 354.49 Mbps
Here are the links to the full results:
Result URL: https://www.speedtest.net/resu…8d-4ac4-b914-23982879724e
Result URL: https://www.speedtest.net/resu…5b-413d-90bd-d412175fb84c
Result URL: https://www.speedtest.net/resu…fc-4721-84b4-b654b815269e
The results seem uniform to me and until something better comes along, I'll continue to use it because it's better than nothing.
From what I understand, the connection is established with the server that gave the shortest ping if you don’t specify a server. Shortest ping does not always mean fastest server it is just the first to reply.
Any testing for consistency should be done to the same server not random ones, and the servers themselves are independent and not run by speedtest so you can’t really blame them for inconsistent server speeds.
Can't seem to keep this open, Just coming back to OMV after been in hospital for ages. Did a fresh install of OMV7 as was on 6. I can't keep the page open. after about 5 seconds "qbittorent client is not reachable" can't seem to do anything.
Might be a DNS problem, post the container log: sudo docker logs qbittorrent
Can't seem to keep this open, Just coming back to OMV after been in hospital for ages. Did a fresh install of OMV7 as was on 6. I can't keep the page open. after about 5 seconds "qbittorent client is not reachable" can't seem to do anything.
Qbittorrent will not fully load if there is no working VPN connection. The answer is in the container log.
Qbittorrent will not fully load if there is no working VPN connection. The answer is in the container log.
When messing with the image, in a random case I found that if the DNS is bad the health check fails since it defaults to DEFAULT_HOST="one.one.one.one". That and a couple of other things made me add "8.8..8.8" to it, ie. DEFAULT_HOST="one.one.one.one,8.8.8.8", although I had to add the CSV parse option as well.
The health check was very paranoid, changing that definitely helps avoid loosing a little downloaded data. I'm not sure how to fix the data loss caused by the restart yet, maybe send SIGABRT. I did change the default disk cache size to 0 and set the saver interval to 1 as it should help, but I'm not sure if that helped (never went back to check).
You can see that the modification I made helped keep it up. In the 11:00 hour you can see that it was 1 fail from restarting... like I've stated before, my VPN connection is spotty. Technically, yesterday was the 1st time that the qbittorrent never had to be restarted on this particular machine with the crappy VPN!!! (the SIGTERM is the machine powering off).
2024-04-09 11:03:16.145013 [WARNING] Failed to ping one.one.one.one. Failures is 0 of 3.
2024-04-09 11:03:29.219690 [WARNING] Failed to ping 8.8.8.8. Failures is 0 of 3.
2024-04-09 11:03:29.240738 [INFO] 1 of 3 have occurred.
2024-04-09 11:04:07.306622 [WARNING] Failed to ping one.one.one.one. Failures is 1 of 3.
2024-04-09 11:04:20.346416 [WARNING] Failed to ping 8.8.8.8. Failures is 1 of 3.
2024-04-09 11:04:20.370601 [INFO] 2 of 3 have occurred.
2024-04-09 11:04:58.446983 [WARNING] Failed to ping one.one.one.one. Failures is 2 of 3.
2024-04-09 11:56:28.288988 [WARNING] Failed to ping one.one.one.one. Failures is 0 of 3.
2024-04-09 12:17:08.021396 [WARNING] Failed to ping one.one.one.one. Failures is 0 of 3.
2024-04-09 19:09:21.751251 [WARNING] Failed to ping one.one.one.one. Failures is 0 of 3.
2024-04-09 19:09:34.816760 [WARNING] Failed to ping 8.8.8.8. Failures is 0 of 3.
2024-04-09 19:09:34.846847 [INFO] 1 of 3 have occurred.
2024-04-09 19:58:15.825921 [INFO] Received SIGTERM, stopping...
Alles anzeigen
Does anyone use the SSL option in this qbittorrentvpn container? If so, why?
Does anyone use the SSL option in this qbittorrentvpn container? If so, why?
Not me.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!