Anyone else seeing this since the upgrade?

551 nobody 20 0 723776 52780 32616 R 99.9 0.1 12:27.18 qbittorrent-nox

High CPU usage on Unraid 7.2.6 with the latest qbittorrent 5.2

Update
Apparently it's a bug related to RSS refresh interval introduced in #22448 . When RSS reader is enabled but no feed is configured, it enters a busy infinite loop.

Workaround: You can disable RSS or add a feed to resolve this.

Edited May 13May 13 by musicking

On 5/12/2026 at 6:35 PM, TheDon said:

not sure if binhex grabs the list dynamically from an api

This ^, i also have a dynamically updating Gist:- https://gist.github.com/binhex/0d8bc1974bad90f8a61d2d4219ef862c

9 hours ago, binhex said:

This ^, i also have a dynamically updating Gist:- https://gist.github.com/binhex/0d8bc1974bad90f8a61d2d4219ef862c

Swapped to the new server name in my wg0.conf, worked instantly on container restart.

Thanks @binhex !

So I tried the latest Unraid update, 7.2.6 to 7.3.0 and had the issue with webui not working, reverted to previous version and everything works again. Weird.

hi all - i'm tracking to get all the search plugins added to qbt-vpn so i can natively search inside the client. I try to add a link (i.e. raw.githubusercontent.com/XXX/YYY-qBittorrent-plugin/main/YYY.py) to the "search plugin" -> "install new plugin" box but nothing happens. i'm on branche binhex/arch-qbittorrentvpn:5.1.1-1-01. Is there anything i can do to get this working?

2 hours ago, crowdx42 said:

So I tried the latest Unraid update, 7.2.6 to 7.3.0 and had the issue with webui not working, reverted to previous version and everything works again. Weird.

I have the same problem.

After change the Endpoint Server to a new one without Port in my wg0.conf its running again.

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/page/202/#findComment-1622597

Edited May 14May 14 by Wetterchen

3 minutes ago, Wetterchen said:

I have the same problem.

After change the Endpoint Server to a new one without Port in my wg0.conf its running again.

https://forums.unraid.net/topic/75539-support-binhex-qbittorrentvpn/page/202/#findComment-1622597

Well I just went back to the previous Unraid release and it works fine. Not sure why upgrading Unraid would have this effect though.

Apologies to jump in like this in-between conversations, @crowdx42 & @Wetterchen.
I was just curious if 🐞the issue I'm having might be connected to what you are exchanging about?

I have not yet reverted back to another any other version, but just updated from 7.2.6 to 7.3 today.
Having had the mentioned issue already with 7.2.6, I'm more than puzzled as I can still not connect to the WebUI.

1 hour ago, IMACRAB said:

Apologies to jump in like this in-between conversations, @crowdx42 & @Wetterchen.
I was just curious if 🐞the issue I'm having might be connected to what you are exchanging about?

I have not yet reverted back to another any other version, but just updated from 7.2.6 to 7.3 today.
Having had the mentioned issue already with 7.2.6, I'm more than puzzled as I can still not connect to the WebUI.

It might be a coincidence but PIA recently changed many of its server URLs; in my case the specific URL was no longer listed. Perhaps the old URL continued to work until the upgrade because the session was still active, and the connection was dropped during the upgrade.

In the "old" configuration the server was specified including the :1337 port—this is no longer necessary.

@IMACRAB

This is your issue-

2026-05-12 19:12:59,551 DEBG 'start-script' stdout output:

[debug] Having issues resolving name 'www.google.com'

Are you running any DNS blockers like AdGuard or Pi-Hole?

Hello,

I need some help with to see if I set up binhex - qBittorrentVPN with an actual vpn correctly. I have Nord and was looking for some assistance to see if I set things up right such as the kill switch. I did look around for some help but either I did not understand or it got confusing (I can be a dumbass some time hehe).

PLS help

Thanks!!!

28 minutes ago, SantanD said:

Hello,

I need some help with to see if I set up binhex - qBittorrentVPN with an actual vpn correctly. I have Nord and was looking for some assistance to see if I set things up right such as the kill switch. I did look around for some help but either I did not understand or it got confusing (I can be a dumbass some time hehe).

PLS help

Thanks!!!

You don’t need a kill switch.

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Scroll down to Q1.

1 hour ago, wgstarks said:

You don’t need a kill switch.

https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md

Scroll down to Q1.

Thank you for that.

What I’m mainly trying to verify is whether qBittorrentVPN is actually routing all torrent traffic through NordVPN and not exposing my server/home IP at all.

Could you clarify what the best way to confirm the container is truly using the NordVPN tunnel?

53 minutes ago, SantanD said:

Thank you for that.

What I’m mainly trying to verify is whether qBittorrentVPN is actually routing all torrent traffic through NordVPN and not exposing my server/home IP at all.

Could you clarify what the best way to confirm the container is truly using the NordVPN tunnel?

1. Open the Unraid Docker tab.

2. Click the binhex-qbittorrentvpn container and select Console.

3. Type curl ifconfig.me and press Enter.

4. The output should be your VPN provider's IP address. If it matches your home IP, the VPN is not working.

The iptables issue for QNAP and Synology users has been worked around, please pull tagged 'latest' when you get a chance.

2 hours ago, binhex said:

The iptables issue for QNAP and Synology users has been worked around, please pull tagged 'latest' when you get a chance.

I can also confirm that the image for arm64 running on my Raspberry Pi 5 is working great. Thank you for this :)

17 hours ago, wgstarks said:

@IMACRAB

This is your issue-

2026-05-12 19:12:59,551 DEBG 'start-script' stdout output:

[debug] Having issues resolving name 'www.google.com'

Are you running any DNS blockers like AdGuard or Pi-Hole?

Yes, I'm using AdGuard Home (also as DHCP host).
Here however also nothing fundamentally changed - it's still running on Unraid.
The only difference is that I now, completely cut out my Internet Box (Orange LiveBox) that I previously only used as a limited DHCP Host of two IPs (itself & unraid).

+ can this really be the issue why I cannot use the WebUI?
Everything else seems to be launching fine

Edited May 15May 15 by IMACRAB

1 hour ago, IMACRAB said:

can this really be the issue why I cannot use the WebUI?
Everything else seems to be launching fine

Yes. Qbit app is failing to start due to the dns failure. I would suggest white listing your docker in AdGuard.

When the container updates to version 5.2 the subcategories stop working. Using 5.1, in the Downloads settings I have the boxes checked for "Use Subcatergories" and "Use Category Paths in Manual Mode" checked. When I update the container to 5.2 those boxes are not checked. If I check the boxes and save, those changes are not retained. When I look at the settings again, the boxes are not checked again. Reverting back to 5.1 fixes the issue.

This is not a new install. I have been using this setup for years.

1 hour ago, wgstarks said:

Yes. Qbit app is failing to start due to the dns failure. I would suggest white listing your docker in AdGuard.

Would you have an idea how to pull that off?
I was able to find out where to get the IP address to be "172.17.0.2".

But now I'm not sure where to go with it in AdGuard Home.
Whitelisting doesn't seem very straight forward there...

I tried setting it up as a 'Client' and deselected global settings, but it didn't change anything.
Would there be another way, or am I using the wrong IP?

1 minute ago, IMACRAB said:

Would you have an idea how to pull that off?

Might try just turning AdGuard off and see if that solves the qbit issue first. I don’t use any blockers so can’t help with that.

50 minutes ago, exactopposite said:

When the container updates to version 5.2 the subcategories stop working.

This appears to be a result of changes made in 5.2 so not really a container problem but here are some suggestions from Google.

https://www.google.com/search?q=qbittorrent+subcategories+not+working+version+5.2&ie=UTF-8&oe=UTF-8&hl=en-us&client=safari#lfId=ChxjMe

54 minutes ago, wgstarks said:

Might try just turning AdGuard off and see if that solves the qbit issue first. I don’t use any blockers so can’t help with that.

Had it turned off, even rebooted the qbit docker but still couldn’t access it.

The logs also still show the unresolved Google issue

12 minutes ago, IMACRAB said:

Had it turned off, even rebooted the qbit docker but still couldn’t access it.

The logs also still show the unresolved Google issue

Sorry, I’m out of ideas. I can see it’s a DNS issue but not sure about next steps.

Alright. Found the issue, which was all to basic.
The wireguard config lease expired. Creating a fresh config through Proton VPN did the trick.
Should have thought about that before :S

Thanks for your help guys 🙏