binhex

I got bored of torrents with zero seed counts popping up so i have added filtering in my classifier.yml file, i decided to enhance the example clssifier too, if you are interested in filtering dead torrents then check out the following code section here, any questions let me know, it's working well for me.

going to add this to the faq, as ive seen this issue waaay too many times.

A quick heads up, there was missing configuration for Caddy meaning the generated Let's Encrypt cert was copied inside the container and thus did not persist, the latest image fixes this but it does require that you modify your existing Caddyfile, so please add the following line in the block at the top of the Caddyfile where the ports are defined: storage file_system /config/caddy/dataThis basically instructs Caddy to store all generated data in the /config bind mount and thus will persist, if you are unsure as to what it should look like see here

Isn't it!, and i finally had my dream turn into a reality, the ability to reverse proxy using free duckdns and let's encrypt using a simple configuration file, I creatd this primarily for me so that i can finally run Seerr securely for friends and family with zero cost without the need for tailscale/wireguard/openvpn shenanigans, love it!. The ONLY downside is Seerr does not currently support base url configuration, see open issue, but that is a Seerr issue not a Caddy issue.

Just to be clear what this image is - This image includes Caddy with the module duckdns built in, this allows you to have a completely free and secure website, no domain registration, no certs need purchasing, look at the /config/caddy/config/Caddyfile for examples of how to configure this.

Overview: Support for Docker image arch-caddy-duckdns in the binhex repo. Application: Caddy - https://caddyserver.com/ Docker Hub: https://hub.docker.com/r/binhex/arch-caddy-duckdns/ GitHub: https://github.com/binhex/arch-caddy-duckdns Documentation: https://github.com/binhex/documentation If you appreciate my work, then please consider buying me a beer For other Docker support threads and requests, news and Docker template support for the binhex repository please use the "General" thread here

missing root CA certs actually, nzbget used to maintain a root ca cert file, looks like that is missing now so switched over to another source.

Ive just done a clean install with the latest and i see no sign of an error in the web ui or the log, where are you seeing this error?. Spotted it in messages in the web ui, i've resolved the issue, please pull down at your convienience.

you need it if you need an incoming port (which you do for torrenting) to allow you to connect to the maximum number of peers, if you aren't torrenting then feel free to set it to no. if you do need an incoming port then you will need to download the correct wiregurd configuration for a p2p enabled endpoint - see proton's documentation.

add +pmp to your username.

Last lines inthe log file: [debug] Valid VPN gateway IP address from tunnel acquired '10.2.0.1' [info] ProtonVPN username 'U_NAME' does not contain the suffix '+pmp' and therefore is not enabled for port forwarding, skipping port forward assignment... [info] Script finished to assign incoming port So does your username for proton have a suffix of +pmp?

I will need to see a log to help further, please see the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/help.md#unraid-users

just tested it, both are set correctly for me, created a new container from CA, maybe your template is out of date, if it bothers you a lot then add from CA again and reconfigure with the same settings as your existing container. EDIT - Read your comment again, so you have just modified the overseerr template to point at seerr for the repository i assume, right?, if so then the easiest solution is install from CA, the more tricky solution is hacking the user template which is located on your USB key.

All references to the old names has been updated to reflect the template name changes, so you should be able to follow this step by step now.

ok so right now all 3 are in sync and set correctly to use port 8080, so if you fire up your browser should be able to access the web ui on port 8080, is this the case?, if not then something else is going on. To answer your question: The container used to simply be named as Container Port: 8080 it's now instead named Port: Web Interface:, see screenshot below, this is what you should delete IF you want to change the web ui port from the default of 8080: So if for example you want to change the port to 8999 you would delete the port above, re-add a config type port and set the host AND container ports to 8999 then change the value for Variable: WEBUI_PORT:to a value of 8999 and lastly if you want the web ui link to work when you left click the container icon then switch to advanced view (top right) and then edit the Web UI: to a value of http://[IP]:[PORT:8999] click apply at the bottom and fire up your web browser and go to http://[server ip]:8999 (or left click the container and select web ui).

attach your docker run command agian for the container, it sounds like you have changed some settings but i assume you have missed something, Q4 is still relevant:- https://github.com/binhex/documentation/blob/master/docker/faq/qbittorrentvpn.md

Just to be clear, you don't have to use ONLY my images, other images from other developers MAY also incude health checks, for instance gluetun does, by looks of your screenshot it appears linuxserver does not, which is a little surprising.

i see you have set the containers to monitor based on env var, so only containers that have the specified env var set, so for you that is key name 'MONITOR_ENABLED' and value 'true', so have you set that env var for prowlarr and gluetun containers?, also please do note healarr will only monitor containers that include health checks (all of the images i produce do), so looking at your screenshot only prowlarr and gluetun container have healthchecks so at best only these two will be rebooted dependant on the env var being set for the container (as previously mentioned) and the health being 'unhealthy'.

See Q5: https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

It's there now, please pull down at your convienience.

That doesnt look like corruption to me, that sounds like it's running a database migration, if however you interrupted that by restrting the container then you may well now have a corrupt database, follow Q4:- https://github.com/binhex/documentation/blob/master/docker/faq/plex.md

Ive just flagged it out of date on AUR, hopefully that will trigger the upstream package to be updated.

Sorry, nope, i only include latest releases to keep support down to a minimum.

Well if there was an update, which by the look of it there was, then the packs may not be compatible with the latest version, you have two options, roll back tothe previous verion and stick with that, or talk to the pack developer and get them to update it to be compatible with the latest version of minecraft (recommended action).

Indeed!, not sure how i missed that!, fixed in 3.0.1 (just pushed).