[[Support] binhex - DelugeVPN]

7 hours ago, Wetterchen said:

 

So i have new information here. 

The support from the tracker said the Client send a false peer_id.

Normaly the code beginning with "-DE..." 

But now its beginning with "--DE".. thats wrong and the Tracker blocked me. 

Its happend with the release of the latest version. 

 

I rolled back to binhex/arch-delugevpn:2.0.4.dev38_g23a48dd01-3-01 and all working fine again. 

 

4 hours ago, webvictim said:

I'm also having this problem on trackers which support Deluge 2.0.x. They report "Your client version is not whitelisted."

 

I suspect that https://github.com/binhex/arch-delugevpn/commit/08b611e5058bb5f84b6d4f4adf5eed864fa86c6c is the reason why.

 

Thanks guys. With this info I used the ltConfig plugin to change peer_fingerprint to -DE204D- and the tracker was happy again with the new docker version. -DE203s- works also. Btw, the error I was receiving from my tracker was "Error: Anonymous client". Couldn't figure it out without your help.

[[Plugin] Dark Theme (now highly configurable!)]

2 hours ago, Skitals said:

Solution is to switch to Theme Engine. Dark Theme is included, and all themes are use a stock "base theme" to get around all the hard coding.

Switched to Theme Engine and all is well. Thanks.

[[Plugin] Dark Theme (now highly configurable!)]

Feb 3 05:44:38 Tower nginx: 2020/02/03 05:44:38 [error] 6468#6468: *2831 open() "/usr/local/emhttp/<br /><b>Warning</b>: filemtime(): stat failed for /usr/local/emhttp/plugins/unassigned.devices/assets/style-dark.css in <b>/usr/local/emhttp/plugins/dynamix/include/Helpers.php</b> on line <b>248</b><br />/plugins/unassigned.devices/assets/style-dark.css" failed (2: No such file or directory), client: 192.168.1.170, server: , request: "GET /%3Cbr%20/%3E%3Cb%3EWarning%3C/b%3E:%20%20filemtime():%20stat%20failed%20for%20/usr/local/emhttp/plugins/unassigned.devices/assets/style-dark.css%20in%20%3Cb%3E/usr/local/emhttp/plugins/dynamix/include/Helpers.php%3C/b%3E%20on%20line%20%3Cb%3E248%3C/b%3E%3Cbr%20/%3E/plugins/unassigned.devices/assets/style-dark.css?v= HTTP/1.1", host: "tower", referrer: "http://tower/Main"

I'm getting this error in my log with the Dark Theme plugin installed whenever I click on the Main tab of the unRAID gui. If I remove the plugin, the error goes away.

[[Support] binhex - DelugeVPN]

2 hours ago, Guanyin said:

I keep getting this in my logs which crashes Deluge.

 

2020-01-20 18:45:01,825 DEBG 'watchdog-script' stdout output:
[info] Starting Deluge Web UI...

2020-01-20 18:45:01,825 DEBG 'watchdog-script' stdout output:
[info] Deluge Web UI started

2020-01-20 18:45:01,988 DEBG 'watchdog-script' stderr output:
Unable to initialize gettext/locale!

2020-01-20 18:45:01,988 DEBG 'watchdog-script' stderr output:
'ngettext'
Traceback (most recent call last):
File "/usr/lib/python3.8/site-packages/deluge/i18n/util.py", line 118, in setup_translation
builtins.__dict__['_n'] = builtins.__dict__['ngettext']
KeyError: 'ngettext'

 

is there a known solution for this issue? I've seen it on this thread before but couldn't find a solution to the problem.

I have this error as well but it seems to be pretty harmless. See the issue posted here Issue#151. Perhaps there is another error in your log causing deluge to crash for you.

[Unraid Forum 100K Giveaway]

My favorite thing about unraid is that it still runs great on my very modest hardware.

 

Can't think of any new features I need right now.

[[Support] binhex - DelugeVPN]

20 minutes ago, PeterB said:

How?  I'm told that I'm on latest and deluge is still at 1.3.15

Try "Check for Updates" on the Docker page.

[[Support] binhex - DelugeVPN]

Seeing this error in the log since upgrading to the deluge 2.0 version:

 

2019-06-19 00:33:39,400 DEBG 'watchdog-script' stderr output:
/home/nobody/deluge.sh: /home/nobody/config_deluge.py: /usr/bin/python2: bad interpreter: No such file or directory

 

I changed the shebang on line 1 to "#!/usr/bin/python3" and modified the print statements to be python3 compatible and all is working.

[unRAID OS version 6.4.0 Stable Release Available]

Just upgraded from 6.3.5 to 6.4.0, process went very smoothly. The only thing I had to do was upgrade my CA Backup plugin to v2 and re-enter settings. One thing I noticed in the Docker page, "Version" shows as "not available" for all of my dockers.

 

Loving the speed of the new interface. Thanks for all your hard work on this release.

[No CPU Scaling Driver installed]

I had this problem as well (Intel Q6600). The kernel showed acpi_cpufreq module was loaded but cpufreq-info showed "no or unknown cpufreq driver is active on this CPU". I discovered that I had to enable Intel SpeedStep in the BIOS CPU Management settings. After booting the driver was functioning.