waymon

It definitely said, that the change will take place once I reboot. It was like the 2nd or 3rd field on the plugins page. I got the machine to boot. Not sure what happened but when I rebooted the computer my USB was not first in the boot order....odd. Will try NUT again! Thanks! Edit-

Thanks. I removed the plugin and still not booting. All I did is install the plugin, it told me to restart. So I click the 'restart' button in unraid. And now it looks as if the machine isnt even getting to the usb boot. I see the logo for a hot second and then its just black. If I tap my power button it turns off. Normally I have to hold it. Its like the machine is stuck in the reboot mode or something....

I installed Network UPS Tools (NUT) by desertwitch from Community Applications and rebooted my server. Now it won't boot up. Do I just disable the plugin on the usb stick?

Thank you. I did some moving and found a sata power cable that worked. I didn't have to make any modifications. I thought I bought this hard drive off amazon new...so it wasn't shucked but now I don't see it in my order history so who knows where I got it from? haha thanks again.

Interesting. Thank you. The drive was in the array and working...but it was in a different position with a different power cable. So in theory, the old power connector had the 3.3v fix already?

Hello - I have an interesting problem. I have a 10tb parity drive that I replaced with a 24tb drive. The replacement worked great. Everything has been up and running for weeks. I'm now trying to use that old 10tb drive as an unassigned drive in my box. When I plug the 10tb back into my box, the drive does not show up. I then tested a 5tb drive - that does show up. I tested the 10tb in a external enclosure and it did showed up as an unassigned drive through USB. Why would the 10tb drive not show up when plugged in via SATA? (my HBA card is a LSI 9210-8i in IT Mode) I know the 10tb can used with my HBA card because it was my array...and now it uses a 24tb parity drive so size isnt an issue. I'm wondering if its a power thing?...can my PSU not support all my hard drives?...would a 10tb drive use more power than 5tb drive? Thanks -

What repo should we be using? vaultwarden/server:latest. - ? I'm running Version 2022.12.0 when I logging to the gui I see that at the bottom.

Thanks.

Damn. Looks like I might take a chance on the 13600k instead of the 12600k.....reports are looking positive.... Same socket so could always sell the 13gen and go back to 12 gen... hmm...considerations...

I have over 1000 torrents. I’d like to sort by “added” but without having to scroll to the bottom. Can you add “reverse added” ? thanks

Thanks. The extra lines was it. Appreciate the help! Looking forward to using this.

I created a custom network but neither my deluge or storm container would start. They would just fail. I changed it to the IP and now I am getting this error below. Why is it trying to connect to .103:60937 ? Where is it getting those numbers? 2022-10-31T14:04:50.568Z INFO api storm/server.go:93 Ready to serve HTTP connections on :8221/ 2022-10-31T14:04:58.859Z ERROR pool storm/pool.go:217 Failed to establish Deluge RPC connection {"error": "RPC error BadLoginError('Password does not match')\nTraceback: Traceback (most recent call last):\n File \"/usr/lib/python3.10/site-packages/deluge/core/rpcserver.py\", line 275, in dispatch\n ret = component.get('AuthManager').authorize(*args, **kwargs)\n File \"/usr/lib/python3.10/site-packages/deluge/core/authmanager.py\", line 121, in authorize\n raise BadLoginError('Password does not match', username)\ndeluge.error.BadLoginError: Password does not match\n"} 2022-10-31T14:04:58.859Z ERROR api storm/api.go:206 Internal Server Error {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "10.0.44.103:60937", "Time": "2022-10-31T14:04:58.827Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "32.771232ms", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"} 2022-10-31T14:05:35.647Z ERROR pool storm/pool.go:217 Failed to establish Deluge RPC connection {"error": "RPC error BadLoginError('Password does not match')\nTraceback: Traceback (most recent call last):\n File \"/usr/lib/python3.10/site-packages/deluge/core/rpcserver.py\", line 275, in dispatch\n ret = component.get('AuthManager').authorize(*args, **kwargs)\n File \"/usr/lib/python3.10/site-packages/deluge/core/authmanager.py\", line 121, in authorize\n raise BadLoginError('Password does not match', username)\ndeluge.error.BadLoginError: Password does not match\n"} 2022-10-31T14:05:35.647Z ERROR api storm/api.go:206 Internal Server Error {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "10.0.44.103:60956", "Time": "2022-10-31T14:05:35.636Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "10.539642ms", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"} 2022-10-31T14:09:24.064Z ERROR pool storm/pool.go:217 Failed to establish Deluge RPC connection {"error": "RPC error BadLoginError('Password does not match')\nTraceback: Traceback (most recent call last):\n File \"/usr/lib/python3.10/site-packages/deluge/core/rpcserver.py\", line 275, in dispatch\n ret = component.get('AuthManager').authorize(*args, **kwargs)\n File \"/usr/lib/python3.10/site-packages/deluge/core/authmanager.py\", line 121, in authorize\n raise BadLoginError('Password does not match', username)\ndeluge.error.BadLoginError: Password does not match\n"} 2022-10-31T14:09:24.064Z ERROR api storm/api.go:206 Internal Server Error {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "10.0.44.103:61176", "Time": "2022-10-31T14:09:24.054Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "10.38151ms", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"}

Still having an issue getting connected. Are these settings correct? This is my auth file

2022-10-16T04:46:18.932Z INFO api storm/server.go:93 Ready to serve HTTP connections on :8221/ 2022-10-16T04:46:25.305Z ERROR pool storm/pool.go:217 Failed to establish Deluge RPC connection {"error": "dial tcp: lookup binhex-delugevpn on 10.0.44.1:53: no such host"} 2022-10-16T04:46:25.305Z ERROR api storm/api.go:206 Internal Server Error {"Method": "GET", "URL": "/api/plugins", "RemoteAddr": "10.0.44.6:52296", "Time": "2022-10-16T04:46:25.165Z", "StatusCode": 500, "ResponseSize": 103, "Duration": "139.998576ms", "error": "A connection to the Deluge RPC daemon could not be established by the connection pool"} I'm getting the same thing. What do you mean "Try not to use IPs when using a custom docker network." What additional steps need to be taken? 😀

Going to follow this video to see if I can get it working on unraid. Currently getting this error with the ElasticSearch container. ERROR.txt