On 7/19/2023 at 5:43 PM, binhex said:

this sounds like it COULD be the libtorrentv2 bug hitting you, try switching to the tag name 'libtorrentv1' if you dont know how to do this then follow these instructions at Q5:- https://github.com/binhex/documentation/blob/master/docker/faq/unraid.md

Been about 3 weeks since I made the change and so far I've not had a single lockup 😀

Thanks for the help 👍

Hi all.

 

Im really close to upgrade ti 6.12.3.

 But i read somebody have problems with this. 

 

Is Q5

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

The rollback option if you get problems?

 

Thanks!

 

27 minutes ago, DanielPT said:

Hi all.

 

Im really close to upgrade ti 6.12.3.

 But i read somebody have problems with this. 

 

Is Q5

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

The rollback option if you get problems?

 

Thanks!

 

I’m running 6.12.3 without any issues. Q5 describes how to roll back a docker container to a previous version. Not the unRAID OS.

 

Downgrading the OS is described here.

14 minutes ago, wgstarks said:

I’m running 6.12.3 without any issues. Q5 describes how to roll back a docker container to a previous version. Not the unRAID OS.

 

Downgrading the OS is described here.

Hi

 

Thanks!

 

I was talking about the container

Its just dawned on me there is no "create Torrent" function within qbittorrent webui.

 

Does anyone know how to create a torrent that can be added to qbittorrent for uploading on Unraid,

 

Could I make it via windows application and then add it to Qbit on Unraid?

11 hours ago, wacko37 said:

Its just dawned on me there is no "create Torrent" function within qbittorrent webui.

 

Does anyone know how to create a torrent that can be added to qbittorrent for uploading on Unraid,

 

Could I make it via windows application and then add it to Qbit on Unraid?

Ok -just created my 1st using mktorrent, had to install NerdTools plugin and enable mktorrent then I followed the this document

 

https://bytesized-hosting.com/pages/how-to-create-a-torrent-using-mktorrent

 

Hope this helps someone in the future

 

First of all great work on this. I use ProtonVPN and having the random P2P port automatically set in qBittorrent is amazing.

 

I have an issue where if I use wireguard the local qBittorrent WebUI isn't accessible. If I use openvpn everything works fine, but I'd like to use wireguard if possible. I don't see any errors in supervisored.log with wireguard and I can see it says "qBittorrent process listening on port 8080". I haven't been able to figure out why I can't access it. I haven't found anything in the FAQ either. I've tried downloading different configs for different servers/countries and tried messing with the config settings on the download page, like proton's VPN accelerator being on or off (with NAT-PMP always on being the exception).

 

Anyone have any ideas?

I'm suddenly having an issue with this, getting the following from my logs:

 

Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 109, in emit
    self.flush()
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 68, in flush
    self.stream.flush()
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
Traceback (most recent call last):
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 102, in emit
    self.stream.write(msg)
OSError: [Errno 107] Transport endpoint is not connected
OSError: [Errno 107] Transport endpoint is not connected

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/supervisord", line 33, in <module>
    sys.exit(load_entry_point('supervisor==4.2.5', 'console_scripts', 'supervisord')())
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/supervisor/supervisord.py", line 361, in main
    options.close_logger()
  File "/usr/lib/python3.11/site-packages/supervisor/options.py", line 1250, in close_logger
    self.logger.close()
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 311, in close
    handler.close()
  File "/usr/lib/python3.11/site-packages/supervisor/loggers.py", line 86, in close
    self.stream.close()
OSError: [Errno 107] Transport endpoint is not connected
2023-08-09 15:29:07,428 DEBG 'watchdog-script' stderr output:
sed: can't read /config/qBittorrent/config/qBittorrent.conf: Transport endpoint is not connected

2023-08-09 15:29:31,452 WARN received SIGTERM indicating exit request
2023-08-09 15:29:31,452 DEBG killing watchdog-script (pid 301) with signal SIGTERM
2023-08-09 15:29:31,452 INFO waiting for start-script, watchdog-script to die
2023-08-09 15:29:31,453 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 23441593907920 for <Subprocess at 23441593916432 with name watchdog-script in state STOPPING> (stdout)>
2023-08-09 15:29:31,453 DEBG fd 15 closed, stopped monitoring <POutputDispatcher at 23441592009040 for <Subprocess at 23441593916432 with name watchdog-script in state STOPPING> (stderr)>
2023-08-09 15:29:31,453 WARN stopped: watchdog-script (exit status 143)
2023-08-09 15:29:31,453 DEBG received SIGCHLD indicating a child quit
2023-08-09 15:29:31,454 DEBG killing start-script (pid 300) with signal SIGTERM
2023-08-09 15:29:32,457 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 23441593901904 for <Subprocess at 23441593998288 with name start-script in state STOPPING> (stdout)>
2023-08-09 15:29:32,457 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 23441608411088 for <Subprocess at 23441593998288 with name start-script in state STOPPING> (stderr)>
2023-08-09 15:29:32,457 WARN stopped: start-script (terminated by SIGTERM)
2023-08-09 15:29:32,457 DEBG received SIGCHLD indicating a child quit

 

Any thoughts? Thank you!

I've recently run into a problem with using this docker container...

 

It started when my cache drive filled up from downloads. After I cleared some space, I was unable to login to my BitTorrent web UI. I did some google searching and some people recommended changing/removing settings in the .conf file, however the things they always say to change/remove in that file are missing. It seems like my file is messed up. If I try to delete the file it does not regenerate with all the info. Manually adding lines to change the password also doesn't seem to work.

 

Ive tried to login with my old password and the default password and none work. I also tried reinstalling the docker container and I can't seem to get back in. Any help is appreciated.

Random question, and I don't think it's been asked yet. I'm monitoring qBittorrent/data/logs/qbittorrent.log from a splunk universal forwarder container. The log is getting saved as 600, so the splunk user from the other container cannot read it. How would I go about changing the permissions for that file (without having to do it manually) to be readable to others?

 

Thank you

Heya,

 

Container won't start for me all of a sudden, has been working fine all week.

 

Error I get:

 

2023-08-19 14:54:15.619603 [info] Host is running unRAID
2023-08-19 14:54:15.638155 [info] System information Linux 45f93a930e14 6.1.38-Unraid #2 SMP PREEMPT_DYNAMIC Mon Jul 10 09:50:25 PDT 2023 x86_64 GNU/Linux
2023-08-19 14:54:15.660715 [info] OS_ARCH defined as 'x86-64'
2023-08-19 14:54:15.681645 [info] PUID defined as '99'
2023-08-19 14:54:15.718547 [info] PGID defined as '100'
2023-08-19 14:54:15.759454 [info] UMASK defined as '000'
2023-08-19 14:54:15.779683 [info] Permissions already set for '/config'
2023-08-19 14:54:15.801727 [info] Deleting files in /tmp (non recursive)...
2023-08-19 14:54:15.827788 [info] VPN_ENABLED defined as 'yes'
2023-08-19 14:54:15.848815 [info] VPN_CLIENT defined as 'wireguard'
2023-08-19 14:54:15.869467 [info] VPN_PROV defined as 'custom'
2023-08-19 14:54:15.897223 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2023-08-19 14:54:15.928502 [crit] VPN configuration file /config/wireguard/wg0.conf does not contain 'Endpoint' line, showing contents of file before exit...

** Press ANY KEY to close this window **

 

It's not showing contents of file before exit if that helps.

 

my wg0.conf file looks like this:

 

[Interface]

# Device: Just Moth

PrivateKey = ***

Address = 10.67.102.237/32

DNS = 10.64.0.1

 

[Peer]

PublicKey = ***

AllowedIPs = 0.0.0.0/0

Endpoint = 154.47.30.143:51820

 

Any help would be great!

Heya,
 
Container won't start for me all of a sudden, has been working fine all week.
 
Error I get:
 
2023-08-19 14:54:15.619603 [info] Host is running unRAID
2023-08-19 14:54:15.638155 [info] System information Linux 45f93a930e14 6.1.38-Unraid #2 SMP PREEMPT_DYNAMIC Mon Jul 10 09:50:25 PDT 2023 x86_64 GNU/Linux
2023-08-19 14:54:15.660715 [info] OS_ARCH defined as 'x86-64'
2023-08-19 14:54:15.681645 [info] PUID defined as '99'
2023-08-19 14:54:15.718547 [info] PGID defined as '100'
2023-08-19 14:54:15.759454 [info] UMASK defined as '000'
2023-08-19 14:54:15.779683 [info] Permissions already set for '/config'
2023-08-19 14:54:15.801727 [info] Deleting files in /tmp (non recursive)...
2023-08-19 14:54:15.827788 [info] VPN_ENABLED defined as 'yes'
2023-08-19 14:54:15.848815 [info] VPN_CLIENT defined as 'wireguard'
2023-08-19 14:54:15.869467 [info] VPN_PROV defined as 'custom'
2023-08-19 14:54:15.897223 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf
2023-08-19 14:54:15.928502 [crit] VPN configuration file /config/wireguard/wg0.conf does not contain 'Endpoint' line, showing contents of file before exit...
** Press ANY KEY to close this window **
 
It's not showing contents of file before exit if that helps.
 
my wg0.conf file looks like this:
 
[interface]
# Device: Just Moth
PrivateKey = ***
Address = 10.67.102.237/32
DNS = 10.64.0.1
 
[Peer]
PublicKey = ***
AllowedIPs = 0.0.0.0/0
Endpoint = 154.47.30.143:51820
 
Any help would be great!

Where is the wg0.conf file located?

Sent from my 22021211RG using Tapatalk

Figured my issue out. Seems my whole config reset, including password and default folders.

 

Any idea why this happens?

On 8/20/2023 at 8:13 PM, Alias_ZA said:

Figured my issue out. Seems my whole config reset, including password and default folders.

 

Any idea why this happens?

if you server has had a unclean shutdown due to crash or power interruption for instance then data loss can occur, including loss of configuration.

5 hours ago, binhex said:

if you server has had a unclean shutdown due to crash or power interruption for instance then data loss can occur, including loss of configuration.

As someone who spent about a month dealing with their server being unreliable, I ran into this issue a lot, and wanted to share why I think it comes up for this container more than others.  

The qBittorrent.conf file is being written to constantly even when there are no changes being made, at least once a minute.  These frequent writes make it much more likely there will be a corruption issue when the system or container crashes unexpectedly.  I doubt you're doing anything intentionally to cause this, but I spun up the linuxserver Qbit container (without vpn, proxy, any of the extra things you've added obviously) and it hasn't made any writes to the qBittorrent.conf file in 20 minutes.  

 

The other reason I think this issue keeps coming up here is that it's more than an inconvenience.  I use categories to place different files at different locations.  When the .conf file reset happens, it doesn't just return the instance to a blank slate.  It still remembers the active torrents, but none of my category configurations for them.  So as soon as the container starts it uses qBit's automatic torrent management mode and the default location and starts moving every single file I have seeding into the default download directory.  

 

I've solved my unrelated server instability issues and haven't run into this issue in a while, but even so I still make sure to only have the container start manually so I can check it.  

Alternative WebUI issue

 

I have two qbit dockers running fine until I noticed my Unraid OS is 18 months old since last update (6.9.3). I know I shouldn't be updating unless there is issue, as issues usually show up right after upgrade. This time is really painful. My USB is corrupted thus I lost some of the dockers config and had to re-do the settings. 

Anywhoo, one of qbit docker is still getting error. The issue is every time I turned on Alternative Web UI to use the dark theme, I'd lost Web UI access with the error "Unacceptable file type, only regular file is allowed.". 

To be honest the other Qbit docker is running fine with dark theme. What is the problem? Is this Unraid 6.12.3 issue?  

Every time I tried to enable Alternative WebUI, it gives the error above, what I have to do is to go into qbit config and change that flag to false, save, reboot the qbit docker, and I can then access the Web UI, but otherwise it's a pain. 

 

Adding that this is Unraid 6.12.3 and Binhex-QbitVPN 4.5.4.

Thanks.

Edited August 30, 20232 yr by Rhodius

Hello,

 

A new update came out and I have to stay on the version I'm on. 

 

How can I tell unraid to not update the container? 

41 minutes ago, urbanracer34 said:

Hello,

 

A new update came out and I have to stay on the version I'm on. 

 

How can I tell unraid to not update the container? 

In the repository field type a colon after the existing text followed by the tag number for the version you want installed. You can get the tag numbers from the dockerhub link in the first post.

20 minutes ago, wgstarks said:

In the repository field type a colon after the existing text followed by the tag number for the version you want installed. You can get the tag numbers from the dockerhub link in the first post.

So for version 4.5.4 I would put in tag "4.5.4-1-03" after "binhex/arch-qbittorrentvpn?"

Edited August 31, 20232 yr by urbanracer34
clarify

29 minutes ago, urbanracer34 said:

So for version 4.5.4 I would put in tag "4.5.4-1-03" after "binhex/arch-qbittorrentvpn?"

Yes, if that’s the tag you want. Don’t forget the colon in between.

binhex/arch-qbittorrentvpn:4.5.4-1-03

And then click apply

It worked! Thank you so much! 

Been having a lot of issues with trackers "not working" only with this qbittorrent docker. Any ideas? I can't for the life of me figure out why this is happening. These torrents are coming from 1337x where they report hundreds of seeds and twice as many peers yet I struggle to connect to even 2 or 3 sometimes. It's only happening with this docker. Any idea where I should start diagnosis?

 

Edit: I'm using CyberGhostVPN, openvpn protocol.

 

 

Edited September 1, 20232 yr by sgiampa
VPN information omission

I can't torrent anything anymore. All of a sudden, every time I try to add a torrent, it stalls and says "errored". In the log it says error: permission denied.

 

I have no idea what to do from here. 

Two days ago everything was working fine. I don't know what changed.

I'm using binhex-qbittorrentvpn

 

 

Just be careful out there guys and don't use default creds and for the love of God turn off upnp.
https://torrentfreak.com/qbittorrent-web-ui-exploited-to-mine-cryptocurrency-heres-how-to-fix-230902/

Sent from my 22021211RG using Tapatalk