#Qbittorrent stalled 2018 update
#Qbittorrent stalled 2018 manual
#Qbittorrent stalled 2018 download
#Qbittorrent stalled 2018 torrent

It automatically restarts and all torrents that have downloaded media that was not stalled does an auto recheck. I don't think the docker is to blame due to if you use the exit qbittorrent button in the menus it shutdowns the program from inside the docker.

#Qbittorrent stalled 2018 torrent

This release still has the problem with automatic torrent management.

#Qbittorrent stalled 2018 update

I am running that right now as it is the most recent update listed on the qbittorrent website. If the update you are talking about is 4.1.5. Without automatic torrent management it kind of defeats the entire purpose of using qbittorrent for me at least. Though it could just be down to the massive refactoring the webui is going through right now. I'm thinking it has something to do with the way the docker shuts down I think it's an unclean exit which qbittorrent isn't handling gracefully. Well an update just came through let's hope it solves this issue. Update after messing around with settings You lose filing torrents by label but the docker behaves as how it was before the updates.

#Qbittorrent stalled 2018 manual

If you set default torrent management to manual you can restart the docker just fine. I am sure this is a qbittorrent problem and not a binhex docker issue. The docker is now unusable as I cannot stop my array or power down the server without a massive torrent recheck. Set all locations to the incomplete folder. Once the move is stopped, unpause the docker. The only way to stop the move is to pause the docker, then move all move files from the appdata/binhex-qbittorrentvpn/qBittorrent back into the incomplete folder. I was able to reproduce this after updating to the release with auto save management. I'm assuming that qbit is just killed when you restart the docker. I think this might be down to qbittorrent not handling improper shutdown very gracefully. And automatic torrent management is being disabled. So I'm running into the issue that everytime I restart the docker my savepaths for all of my torrents resets to /config/qbittorrent. Sat Dec 29 12:05:19 2018 UDP link remote: :443įrom the above snipet i would guess the endpoint you are connecting to doesnt exist, or is having issues, or is blocked in some manner on your lan (firewall?). Sat Dec 29 12:05:19 2018 TCP/UDP: Preserving recently used remote address: :443 Sat Dec 29 12:05:19 2018 NOTE: the current -script-security setting may allow this configuration to call user-defined scripts Sat Dec 29 12:05:14 2018 WARNING: file 'nf' is group or others accessible Sat Dec 29 12:05:14 2018 WARNING: -keysize is DEPRECATED and will be removed in OpenVPN 2.6 Sat Dec 29 12:05:14 2018 SIGHUP received, process restarting Sat Dec 29 12:05:14 2018 Inactivity timeout (-ping-restart), restarting

After the initial startup, this just loops endlessly every couple minutes. I will try to build it from source with debug enable.Updated the container, and when I restarted it, QB isn't running any more.

#Qbittorrent stalled 2018 download

(N) T19:16:45 - 'my.torrent' added to download list. (N) T19:16:45 - Download first and last piece first: Off, torrent: 'my.torrent' Reason: The remote host name was not found (invalid hostname) (W) T19:16:23 - Couldn't download GeoIP database file. (I) T19:16:23 - qBittorrent is successfully listening on interface 0.0.0.0 port: UDP/8999 (I) T19:16:23 - qBittorrent is successfully listening on interface 0.0.0.0 port: TCP/8999 (I) T19:16:23 - qBittorrent is successfully listening on interface :: port: TCP/8999

(I) T19:16:23 - Local Peer Discovery support (I) T19:16:23 - qBittorrent is trying to listen on any interface port: 8999 (W) T19:14:33 - Couldn't load GeoIP database. (I) T19:14:33 - Local Peer Discovery support (I) T19:14:32 - qBittorrent is trying to listen on any interface port: 8999