Nimrad

I found my own issue. Without my knowledge I was connected over wireguard so my IP was not in fact whitelisted.

Sorry, that was a typo. I meant that my local IP is 192.168.1.57. My previous fix was rolling back, making a personal password and white listing my IP ranges before updating again.

Suddenly having issues reaching the WebUI (again). I fixed it recently due to the update requiring password etc, but now out of the blue I can't reach it. It's running fine and talking to *arr apps. Trying to reach locally from 192.167.1.57, and thought this was the correct setting for it.

I'd prefer a more elegant solution, but if it's not possible I think I'm just gonna change to another client. For some reason it's impossible to mass-edit tracker info in Deluge(except custom scripts, which is a bit out of my comfort zone atm), and I fear one day I have to change my passkey for hundreds of torrents.

I'm sorry if this has been asked before, but I'm having an issue regarding seeding many torrents at the same time and someone made me aware of this. I'm not sure how to read the status of this bug, but if I understand correctly this is still not fixed? I suspect I might be affected by this bug as I am seeding around 2000 torrents and some are not showing up as active in the tracker where I seed. No error message from Deluge, but some torrents are showing "Next announce: ∞", and I suspect this bug might be the reason. Is there a way I can manually edit the default "active_tracker_limit"?

I have a weird issue that I don't know how to fix. For some reason I can't reach Deluge when connected remotely to my server over Wireguard. All other dockers work fine, and I know Deluge is running fine, but I just can't seem to reach the UI. Any idea how to troubleshoot this?

So, I just got it to work. Turns out the .conf was somehow corrupted during copying and I had to manually change it. Some random characters were added in my file. BTW, for others: My file worked as I posted it. As for #3; I manually changed the IP before posting here(sorry, I should've said so). Thanks so much for the help!

Mine looks similar: [Interface] PrivateKey = fffff Address = 10.34.0.134/16 DNS = 10.35.53.1 [Peer] PublicKey = fffff AllowedIPs = 0.0.0.0/0,::/0 Endpoint = pvdata.host:3389

Nobody knows what this last error means? Are there any other logs I could explore to troubleshoot this? As mentioned the config file works fine in windows.

I just tried to switch to using Wireguard from my VPN Provider. I made a .conf file that works fine when I test it from my laptop and I dropped it in the wireguard folder. Deluge doesn't want to use it though, it just wont start. It renamed the file to wg0.conf. Logs: 2020-12-27 15:26:34.989348 [info] System information Linux 46f19ca4e7a6 5.10.1-Unraid #1 SMP Thu Dec 17 11:41:39 PST 2020 x86_64 GNU/Linux 2020-12-27 15:26:35.018259 [info] OS_ARCH defined as 'x86-64' 2020-12-27 15:26:35.046192 [info] PUID defined as '99' 2020-12-27 15:26:35.091854 [info] PGID defined as '100' 2020-12-27 15:26:35.141391 [info] UMASK defined as '000' 2020-12-27 15:26:35.162540 [info] Permissions already set for volume mappings 2020-12-27 15:26:35.207769 [info] Deleting files in /tmp (non recursive)... 2020-12-27 15:26:35.234431 [info] VPN_ENABLED defined as 'yes' 2020-12-27 15:26:35.258965 [info] VPN_CLIENT defined as 'wireguard' 2020-12-27 15:26:35.285307 [info] VPN_PROV defined as 'custom' 2020-12-27 15:26:35.321662 [info] WireGuard config file (conf extension) is located at /config/wireguard/wg0.conf 2020-12-27 15:26:35.357376 [crit] VPN configuration file /config/wireguard/wg0.conf does not contain 'Endpoint' line, showing contents of file before exit...

Any idea why AutoRemove is not removing the oldest torrents? I have no exemptions, but still my oldest torrents are still there.

It seems I have the same issue as you guys. Just to elaborate, I don't use NZBGet.

I'm also getting these errors. Not sure if relevant, but no mirroring to flash either.

Short backstory: I've been having issues with my unraid freezing and am in the troubleshooting phase now. I haven't been able to mirror/store syslog to flash/array, and was made aware in my previous post it might be a bug in the beta. So, I want to try and downgrade to Stable branch(according to this previous forum post), but it's not possible to select Stable. When I change to "Stable", the row loads and then reverts back to "Next" branch: Any idea why? Is there something else I can do?

Ok thanks. I updated to beta 35 just now and it’s still the same issue.