Edited this post because fucking Synology. That was the issue.  2hrs of my life wasted troubleshooting this.

Edited June 26, 20242 yr by StabbyMeowkins

I just want to make sure im doing this safely. I want to route my firefox container through the binhex-qbittorrentvpn container.

Firefox container settings

Network Type: none

Extra parameters: --network container:binhex-qbittorrentvpn
Remove other container ports

binhex-qbittorrentvpn settings
 

Add a new port for firefox
Firefox container port: 5800

Host port: 5800

And lastly add port 5800 to VPN_INPUT_PORTS

Does this look safe? i dont want to accidentally open up my firefox container to everyone on the internet.

 

Best Regards!

Have a new unRaid build going, and my processor is struggling when downloading using this container. Admittedly, this processor is a lowly n5105, so if this sort of performance is to be expected, then I'll learn to live with it (for now...). When downloading 5 torrents, the cpu usage is around 40-90%. I'm using wireguard, although I did attempt using openVPN beforehand with similar results.

 

Thank you for any insights, much appreciated.

I'm having issues where the RSS downloader rules are not saving correctly. I can change the search strings and which feeds the rule applies to, but changing most of the options, such as whether to create a subfolder, whether or not to add paused, or save to a different directory, will not be saved once I close out of the download rules window. I've found moderate success trying to edit the json file with the downloading rules, but it's hard to know what options to use when I can't save the options I want to use as a basis.

On 6/30/2024 at 11:23 PM, celticGreen said:

Have a new unRaid build going, and my processor is struggling when downloading using this container. Admittedly, this processor is a lowly n5105, so if this sort of performance is to be expected, then I'll learn to live with it (for now...). When downloading 5 torrents, the cpu usage is around 40-90%. I'm using wireguard, although I did attempt using openVPN beforehand with similar results.

 

Thank you for any insights, much appreciated.

If you are downloading to a share in the fuse layer (none exclusive share) it might take up a good deal of CPU.

Please note that if you change it to an exclusive share you won't be able to use hard links when moving files.

Edited July 4, 20242 yr by Yock

In my system there is a memory leak on QbittorrentVPN container. The ram grow up until crash the system. I've limited my resource on docker to 94GB of RAM 

 

(from 22.30 to 9.00 the system runs in power saving mode)

 

And the system should be limited to 32GB + 8GB for torrent checks:

 

Someone can help me to understand what I can do to avoid it? 

Today after updating I keep getting "Error: error sending query: Error creating socket" in my log both on wireguard or on openvpn with different servers. Anyone else getting this error?

4 minutes ago, Lagadin said:

Today after updating I keep getting "Error: error sending query: Error creating socket" in my log both on wireguard or on openvpn with different servers. Anyone else getting this error?

I have the same error, using openvpn.

Same here, I turned on debug and see this in my logs...

 

2024-07-04 12:10:48.781171 [info] NAME_SERVERS defined as '84.200.69.80,37.235.1.174,1.1.1.1,37.235.1.177,84.200.70.40,1.0.0.1'
2024-07-04 12:10:48.798036 [debug] iptables default policies available, setting policy to drop...2024-07-04 12:10:48.814055 [debug] ip6tables default policies available, setting policy to drop...
Error: error sending query: Error creating socket
2024-07-04 12:10:48.852032 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:10:53.868701 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:10:58.884607 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:11:03.901040 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:11:08.916784 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...
Error: error sending query: Error creating socket
2024-07-04 12:11:13.932828 [debug] Having issues resolving name 'nl-amsterdam.privacy.network', sleeping before retry...

 

Some sort of dns error? I'm using PIA

Edited July 4, 20242 yr by Gex2501

Me as well getting the Error creating socket.

Found that it appears that having a custom docker network (so i can assign a custom ip to the container), is at least part of the issue. if i change network back to BRIDGE instead of BR0 then everything seems to fire up as per before. although a temp fix, i do need this docker (as well as others that i have piggy backing off the connection) to be running under a manually specified IP.

Edited July 4, 20242 yr by Migraine

5 minutes ago, Migraine said:

Me as well getting the Error creating socket.

Found that it appears that having a custom docker network (so i can assign a custom ip to the container, is at least part of the issue. if i change network back to BR0 then everything seems to fire up as per before. although a temp fix, i do need this docker (as well as others that i have piggy backing off the connection) to be running under a manually specified IP.

 

I set my tag to :4.6.5-1-05 and I'm back in business. It would seem there is an error with the :latest or :4.6.5-1-06 that was pushed just a few hours ago...

Edited July 4, 20242 yr by Gex2501

I have opened an issue on github: https://github.com/binhex/arch-qbittorrentvpn/issues/250

7 minutes ago, Gex2501 said:

 

I set my tag to :4.6.5-1-05 and I'm back in business. It would seem there is an error with the :latest or :4.6.5-1-06 that was just a few hours ago...

Yeah, I've reverted back to the tag mentioned above, and all is working again, thanks for posting the tag so i didn't have to go looking!, will wait till this issue can be rectified before upgrading.

 

** If your running your qbit on a manually specified network / ip hold off updating or revert back to the tag mentioned by Gex2501 (:4.6.5-1-05) **

 

*** If your running qbit on the typical bridge network then in theory you might be fine either way (updated or not) ***

Edited July 4, 20242 yr by Migraine

So my github issue was closed because this issue already exists: https://github.com/binhex/arch-qbittorrentvpn/issues/248

 

Sadly I don't have time to figure out the proper fix right now. Maybe someone else can explain what we need to do. Some kind of change to our unraid template?

1 minute ago, Gex2501 said:

So my github issue was closed because this issue already exists: https://github.com/binhex/arch-qbittorrentvpn/issues/248

 

Sadly I don't have time to figure out the proper fix right now. 

pull latest image, either 'check for updates' and apply or click on 'force update'.

I have performed a 'force update' and the issue persists, even with public DNS for NAME_SERVERS.

2 minutes ago, floepie05 said:

I have performed a 'force update' and the issue persists, even with public DNS for NAME_SERVERS.

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

is there a way to get "Display torrent content and some options" under "when adding a torrent" like the windows version of qbittorrent?

What it looks like and the option inside the windows version for context. \/\/

Just installed the latest update and now all i'm getting is "Error: error sending query: Error creating socket"

Previous version worked fine.

supervisord.log

Edited July 4, 20242 yr by Yock

3 minutes ago, Yock said:

Just installed the latest update and now all i'm getting is "Error: error sending query: Error creating socket"

Previous version worked fine.

 

1 hour ago, binhex said:

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

 

Sorry, pressed the save button too fast and was too slow to edit my post it seems.

Im getting this same error "Error: error sending query: Error creating socket" since the update, using PIA via OpenVPN, i know someone else who is using PIA via wireguard with the same issue too.

Any update on this?

21 minutes ago, Yock said:

Any update on this?

Simplest thing to do would be to revert to the previous tag as others have mentioned above.

Will do, thanks.