This repository has been archived by the owner on Jul 16, 2023. It is now read-only.
Added a process running check #161
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Validates that the qbittorrent process is running during the health check loop. If it's not running, start it back up.
Leaving curl installed.
When leaving the ENABLE_SSL variable unset or set to something other than yes/no, true/false, 1/0, uses ignore mode, which makes no changes to qBittorrent.conf file for SSL. This is useful for when you are managing certificates manually.
Added SSL ignore mode functionality to the readme.
Disabling the find/chown line because it slows down start up considerably for me and isn't needed.
Dockerfile: Now downloads and extracts VueTorrent for optional use; leaves jq and natpmpc installed for port forwarding. README.md: Updated the features listing to include the qBittorrent PID watch, VueTorrent, and Proton VPN port forwarding; updated the sample docker run command to use tenseiken/qbittorrentvpn instead of dyonr/qbittorrentvpn; added info about new environment variables. qbittorrent/iptables.sh: Now calls new script file portfwd.sh to run indefinitely in the background. qbittorrent/portfwd.sh: New script that keeps a working Proton VPN port forward set up within the container. qbittorrent/start.sh: Added a section within the health check loop that ensures the listen port in qBittorrent matches up with the port being forwarded. It can change.
Added a line to log back out of the web UI API after each login. Prevents a bunch of orphaned login cookies from being valid longer than they need to be.
Redirecting output to /dev/null to suppress occasional error messages from curl.
Still getting errors from curl about the API login cookie being unset, so I've added some error handling around that.
Adding instructions for the Proton VPN port forward functionality.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Starting with qbittorrent 4.5.0, I've been having a recurring problem where the process runs for a few days at most, then dies. The container keeps on running, so I have to catch it myself and manually restart the container. For my own sanity, I added a check in the network health check loop that determines if the process is running, and if not, uses the init file to start it back up again. Some relevant logging: