3 hours ago, WiffleballTony said:

I'm having issues accessing the WebGUI for DulugeVPN. When I try and load the page, it gives me "this site can't be reached" Connection refused. It doesn't matter if I disable or enable the VPN. The gui won't load. 

Checking the logs, everything seems to be connecting. Someone please help! Thank you in advance! 

supervisord.log 47.73 kB · 2 downloads docker run.txt 1.53 kB · 0 downloads

from the first sentence, in the first post in the first thread of this:-
 

Quote

Important - This thread is NOT for support of Docker images, it is a place to request new images, raise issues with any templates or for me to post general news. For support for a particular image go to the UNRAID Web UI/Docker, left click the container and select 'Support' and then post there.

Hi @binhex Love your work and hope you're doing well!

 

If you are. still taking recommendations please consider Lingarr

https://hub.docker.com/r/lingarr/lingarr

 

Thanks in advance!

Hi @binhex,

 

May I request the 'serpbear' image?

 

https://docs.serpbear.com/deployment/running-locally-with-docker

 

Thank you!

Hi!

 

Few days ago I updated the binhex-rclone docker. Afterwards it seems like rclone can`t find rclone.conf anymore.

I checked the docker config and found out the path to RCLONE_CONFIG_PATH seemed wrong. I changed it to the correct path but the result was the same. (for some reason i forgot the path that was set originally......)

Any idea what might gone wrong?

Hello everyone,

I've been having issues with binhex-sabnzbdvpn lately. From my testing, it seems that other dockers, like Sonarr and Radarr, which are on the same network, can no longer connect to SABnzbd.

 

I initially tried disabling Privoxy, but that didn’t resolve the problem. I then uninstalled binhex-sabnzbdvpn and instead installed Privoxy and SABnzbd as standalone services. With this setup, Sonarr and Radarr can easily connect to SABnzbd, which points to an issue with the VPN portion of the binhex-sabnzbdvpn package.

My LAN_NETWORK is correctly defined to cover my network, and I even simplified it to /16 since I have several VLANs. This setup worked fine in the past, but now the issue persists even when I roll back to older versions of binhex-sabnzbdvpn.

 

If anyone has any insights, I’d appreciate it!

 

For reference, I'm running Unraid versions 6.12.13 and 7.0.0-beta.4, both showing the same behavior. All dockers, including Sonarr, Radarr, and SABnzbd, are on a dedicated interface for dockers

Edited November 4, 20241 yr by ximian

I'm curious if development will renew on the binhex rtorrent project:

https://github.com/binhex/arch-rtorrentvpn

 

It seems like there is some life starting again on the rakshasa rtorrent project:

https://github.com/rakshasa/rtorrent

is there some one who can help me with this issue i have.

 

Hey Binhex, would it be possible to make a docker container for QobuzDownloaderX-MOD?

Hi binhex,

Thank you for your excellent work on the arch-qbittorrentvpn image - it’s been incredibly helpful!

I’d like to suggest an idea that seems like a natural extension of your work: arch-kubovpn, a Docker container for running the Kubo (IPFS) daemon through a VPN. Like qBittorrent, Kubo includes a built-in web UI, which makes it easier to manage, and it feels like a good fit for a containerized VPN setup.

I hope you’ll consider it!

48 minutes ago, nathanriley said:

Hi binhex,

Thank you for your excellent work on the arch-qbittorrentvpn image - it’s been incredibly helpful!

I’d like to suggest an idea that seems like a natural extension of your work: arch-kubovpn, a Docker container for running the Kubo (IPFS) daemon through a VPN. Like qBittorrent, Kubo includes a built-in web UI, which makes it easier to manage, and it feels like a good fit for a containerized VPN setup.

I hope you’ll consider it!

my question to you would be, does this require an incoming port assignment?, if not then please see Q24 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

14 minutes ago, binhex said:

my question to you would be, does this require an incoming port assignment?, if not then please see Q24 from the following link:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Kubo works best with an incoming port, similar to qBittorrent. While it can function without one, having a port open allows the node to fully participate in the IPFS network which improves peer discovery, DHT functionality, and overall performance (especially for hosting content). Without it, the node needs to rely on relays, which limits efficiency.

binhex-official-windows question. I'm trying to add my shares to windows as native drives, is that possible? If so how can I do it or do something similar?

On 2/12/2025 at 10:19 AM, downloadedskill said:

binhex-official-windows question. I'm trying to add my shares to windows as native drives, is that possible? If so how can I do it or do something similar?

@binhex Any thoughts on this one?

Container request: ThreadFin (an M3U proxy for Kernel/Plex/Jellyfin/Emby based on xTeVe)

 

https://hub.docker.com/r/fyb3roptik/threadfin

 

https://github.com/Threadfin/Threadfin

 

There is an existing unraid template, but having a M3U proxy under the "binhex" brand would be nice to have.

 

In my current configuration, it’s network is tied to your qbt-vpn container, but I’m not entirely sure whether it’s secure for the app to auto-bind its web UI to the WAN WireGuard IP.
 

I just experienced an odd behavior with a couple of the containers (jellyfin, Lidarr) whereupon they randomly  broke last night and orphaned. The odd part about this is I don't have the option to just reinstall from the existing installed data, it only allows for a fresh install. Has anyone else experienced this?

I have now implemented sub version tagging for all images going forward (no retro version tags), this means if you are sensitive to version changes for any application you can now restrict this by specifying the version you want in a more exact manner. The tags generated are as follows:-

<major version>

<major version>.<minor version>

<full version>

'latest'

 

So for example a version of 'v1.45.0' would generate the following tags:-

v1
v1.45
v1.45.0
latest

So if you wanted to only use v1, then you could specify '<repo name>:v1' or if you wanted to use the current major-minor version then '<repo name>:v1.45'

Do keep in mind sub version tags will only be generated for applications that comply to semver, that is 3 (or more) octets in the version, not all application developers do this.

Now included in FAQ, see Q11:- https://github.com/binhex/documentation/blob/master/docker/faq/general.md

I have correctly configure prowlarr to connect to sonarr radarr redarr and sabnzb. The only issue is deluge vpn. when trying to its giving me a http request time out im able to use it with nord vpn correctly configured no problem but trying to connect to any arr is a bit of a problem here is some error logs from within prowlar

 

[Error] Deluge: Unable to test connection 

[v1.35.1.5034] System.Net.WebException: Http request timed out
   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponseAsync(HttpRequest request, CookieContainer cookies) in ./Prowlarr.Common/Http/Dispatchers/ManagedHttpDispatcher.cs:line 170
   at NzbDrone.Common.Http.HttpClient.ExecuteRequestAsync(HttpRequest request, CookieContainer cookieContainer) in ./Prowlarr.Common/Http/HttpClient.cs:line 171
   at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 70
   at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 137
   at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.AuthenticateClient(JsonRpcRequestBuilder requestBuilder, DelugeSettings settings, Boolean reauthenticate) in ./Prowlarr.Core/Download/Clients/Deluge/DelugeProxy.cs:line 307
   at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.BuildRequest(DelugeSettings settings) in ./Prowlarr.Core/Download/Clients/Deluge/DelugeProxy.cs:line 214
   at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.ProcessRequest[TResult](DelugeSettings settings, String method, Object[] arguments) in ./Prowlarr.Core/Download/Clients/Deluge/DelugeProxy.cs:line 221
   at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.GetVersion(DelugeSettings settings) in ./Prowlarr.Core/Download/Clients/Deluge/DelugeProxy.cs:line 54
   at NzbDrone.Core.Download.Clients.Deluge.Deluge.TestConnection() in ./Prowlarr.Core/Download/Clients/Deluge/Deluge.cs:line 105

[Warn] ProwlarrErrorPipeline: Invalid request Validation failed: 
 -- : Unknown exception: Http request timed out 
[Info] ReleaseSearchService: Searching indexer(s): [Anime Time] for Term: [], Offset: 0, Limit: 100, Categories: [7000] 
[Info] ReleaseSearchService: Searching indexer(s): [The Pirate Bay] for Term: [], Offset: 0, Limit: 100, Categories: [2000, 2020, 2040, 2060, 2030, 2045] 
[Info] ReleaseSearchService: Searching indexer(s): [YourBittorrent] for Term: [], Offset: 0, Limit: 100, Categories: [2000] 
[Error] Deluge: Unable to test connection 

[v1.35.1.5034] System.Net.WebException: Http request timed out
   at NzbDrone.Common.Http.Dispatchers.ManagedHttpDispatcher.GetResponseAsync(HttpRequest request, CookieContainer cookies) in ./Prowlarr.Common/Http/Dispatchers/ManagedHttpDispatcher.cs:line 170
   at NzbDrone.Common.Http.HttpClient.ExecuteRequestAsync(HttpRequest request, CookieContainer cookieContainer) in ./Prowlarr.Common/Http/HttpClient.cs:line 171
   at NzbDrone.Common.Http.HttpClient.ExecuteAsync(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 70
   at NzbDrone.Common.Http.HttpClient.Execute(HttpRequest request) in ./Prowlarr.Common/Http/HttpClient.cs:line 137
   at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.AuthenticateClient(JsonRpcRequestBuilder requestBuilder, DelugeSettings settings, Boolean reauthenticate) in ./Prowlarr.Core/Download/Clients/Deluge/DelugeProxy.cs:line 307
   at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.BuildRequest(DelugeSettings settings) in ./Prowlarr.Core/Download/Clients/Deluge/DelugeProxy.cs:line 214
   at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.ProcessRequest[TResult](DelugeSettings settings, String method, Object[] arguments) in ./Prowlarr.Core/Download/Clients/Deluge/DelugeProxy.cs:line 221
   at NzbDrone.Core.Download.Clients.Deluge.DelugeProxy.GetVersion(DelugeSettings settings) in ./Prowlarr.Core/Download/Clients/Deluge/DelugeProxy.cs:line 54
   at NzbDrone.Core.Download.Clients.Deluge.Deluge.TestConnection() in ./Prowlarr.Core/Download/Clients/Deluge/Deluge.cs:line 105

[Warn] ProwlarrErrorPipeline: Invalid request Validation failed: 
 -- : Unknown exception: Http request timed out 
 

Hi all,

I'm using the delugeVPN container and successfully routing my arr's via it.

But it got me wondering. With Tailscale now baked into unraid, is there a way to configure the VPN in this container as my exit node?

Just a thought...

Roy

Trying to get PiHole working. Developer on the PiHole forum listed several issues with the Unraid application (out of date or incorrect variables), but couldn't elaborate more. Can anyone help clarify what needs to be done to fix?

Thanks!

6 hours ago, Anti-Matt-er said:

Trying to get PiHole working.

Missing the most important part, what's actually not working/the error you get?

I think those weird variables come from Unraid itself doing some jiggery to save port settings when you change to a network type that doesn't support port mapping... its not part of the binhex template.
The variables aren't really a problem, but it is a symptom that you might not be using the correct network type.

On 5/28/2026 at 1:10 AM, Kilrah said:

Missing the most important part, what's actually not working/the error you get?

First issue is frequent inability to connect to the PiHole dashboard from my iPhone. During this time I can still connect from two different Windows PCs. I am always able to connect to the NAS server via its IP. Note that this is an intermittent fault. Sometimes I'm able to connect from the iPhone. Unsure if this is related, but I can never see the PiHole server in the Unifi (router) dashboard under it's own IP. I can always see the NAS server.

Next issue is the intermittent failure to load web pages. Looking into the query log I see a large number of failures to get a response from the upstream server. I'm also seeing a few connection errors. This happens on multiple devices (basically all) and prevents me from accessing these sites.

I think I'm being told that I need to switch to MACVLAN from IPVLAN on the PiHole forums. If that is confirmed then I will try again this weekend. I wanted to post here as they also said that the container configuration was old/invalid.

Query log error (this happens to most client devices):

Query Status: Forwarded to 192.168.1.1#53

Reply: No reply received

Issue log error (this pops up occasionally):

CONNECTION_ERROR	Connection error (192.168.1.1#53): TCP connection failed (Operation in progress)

On 5/28/2026 at 5:13 AM, tjb_altf4 said:

I think those weird variables come from Unraid itself doing some jiggery to save port settings when you change to a network type that doesn't support port mapping... its not part of the binhex template.
The variables aren't really a problem, but it is a symptom that you might not be using the correct network type.

I had it setup as a custom bridged network with fixed IP. As I mentioned in the post above, I had used the IPVLAN for docker as I read on another post that it was required. I can switch to MACVLAN and try again this weekend, if that's what's recommended.

Tried MACVLAN and now it won't run. Still have the save variable errors too.

Any support to update the container with the recommendations from the PiHole dev? Any other changes I should make my my settings?

docker run
  -d
  --name='binhex-official-pihole'
  --net='br0'
  --ip='192.168.1.5'
  --pids-limit 2048
  -e TZ="America/Los_Angeles"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="PoopyServer"
  -e HOST_CONTAINERNAME="binhex-official-pihole"
  -e 'TCP_PORT_80'='8155'
  -e 'TCP_PORT_53'='53'
  -e 'UDP_PORT_53'='53'
  -e 'UDP_PORT_67'='67'
  -e 'DNSMASQ_LISTENING'='all'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:80]/admin'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/templates/main/unraid/binhex/images/official-pihole-icon.png'
  -v '/mnt/user/appdata/official-pihole/pihole':'/etc/pihole':'rw'
  -v '/mnt/user/appdata/official-pihole/pihole/dnsmasq':'/etc/dnsmasq.d':'rw'
  --cap-add NET_ADMIN 'pihole/pihole'
cfa1725acb41e03622699321593681a6080788da9f20ec5f9b3032b5c9d3943b
docker: Error response from daemon: failed to set up container networking: failed to create the macvlan port: device or resource busy

Run 'docker run --help' for more information

The command failed.

14 hours ago, Anti-Matt-er said:

Tried MACVLAN and now it won't run. Still have the save variable errors too.

Any support to update the container with the recommendations from the PiHole dev? Any other changes I should make my my settings?

Switch to bridge network and right port settings will reappear.
You can't port map on custom networks like the docker br0, so either you can have pihole on its own IP with no mapping (ports are 1:1), or you can use the port mapping like the pihole devs suggest.

The error is likely the dhcp pool from docker network clashing with your dhcp set by your router.
Its also possible you need to restart the server as Unraid may not have cleaned up its network artifacts correctly.