jquery

Thanks for the warning. I found out that the connection works when I use a usb-c to usb-a cable and plug it into a usb-a port on my server. A usb-c to usb-c connection doesn’t work. Unfortunately I dont have a long enough cable laying around. I moved all the equipment around just to try this out 🤣 It may be the port, a configuration issue or the cable. I am not in the mood to troubleshoot further. I will simply buy a longer usb-c to usb-a cable and call it a win.

Thank you so much for updating the plugin. Unfortunately, my Ecoflow is not being recognized. I also ran „Auto Config“ after resetting the configuration and it told me that no UPS devices were found. i feel like I am missing a very basic step or something. nut-debug-20250410141028.zip

It would be awesome if that was the solution! Any idea when the next version of NUT for unraid will be released, so I can try ecoflow support?

Here it is, thanks! nut-debug-20250405192327.zip

I am trying to get an ecoflow delta 3 plus to work with NUT. It is on the compatibility list, so it should work. However, I can't even get the NUT service to start. Right after installing the NUT plugin, without any changes to the settings, I get this error: "NUT was not able to start successfully - please check the SYSLOG for more information." Syslog says this: Writing NUT configuration... rc.nut: Updating permissions for NUT... rc.nut: Checking if the NUT Runtime Statistics Module should be enabled... rc.nut: Disabling the NUT Runtime Statistics Module... rc.nut: Network UPS Tools - Generic HID driver 0.53 (2.8.2) rc.nut: USB communication driver (libusb 1.0) 0.47 rc.nut: libusb1: Could not open any HID devices: insufficient permissions on everything rc.nut: No matching HID UPS found rc.nut: Driver failed to start (exit status=1) rc.nut: Network UPS Tools - UPS driver controller 2.8.2 Any help is appreciated.

this error seems to be caused by the fact that the ./db/bitcoin directory can't be created. I solved that by manually creating the directory inside the electrs folder. After that electrs could't access the auth-cookie in the bitcoin-node directory, because the permissions were jumbled. I fixed that by changing the permissions. annoyingly, the permissions are reset every time I restart the bitcoin docker. But even after all that electrs can't connect to the RPC service of bitcoind. No matter what I try, I get a "connection refused" error. I am at my wits end. And since there does not seem to be any kind of support here, I am ready to give up. edit: I solved the last bit: The problem was, that the bitcoin RPC service is only listening on localhost by default. I couldn't figure out how to change that, unfortunately, because I couldn't figure out how to pass "-rpcallowip" when the docker starts. Instead, I changed the network to "host" in the settings of the bitcoin docker and the electrs docker. Now they are listening on the same IP and the localhost connection works. Now I only need to find a way to automatically change the permissions on the .cookie file each time the bitcoin docker restarts.# Finally, I am not sure, if its a good idea to run v0.9 of electrs when 0.10.4 is already out.

did you try forwarding the port 41641 (UDP) to your unraid server? its important that your tailscale devices connect directly and not via relay (DERP) servers. Using the relay servers is the most likely reason for slow performance: https://tailscale.com/kb/1257/connection-types

I get this error too and I don't know what to do about it. I have never used the tailscale docker container and I also don't know how the "set" command can help here. If I access "tailscaleip:5252" the web interface works as expected. Thanks for implementing the option to change the port, by the way! tailscale-diag-20240114-133830.zip

I understand! Thanks for all your work! the reason I need this functionality is because I have multiple tailscale clients that I want to forward ports to, so that they can all accept direct connections.

Still haven’t found a solution. The official guide points me to a file that doesn’t exist in the path that the guide specifies. It should be here: /etc/defaults/tailscaled where does the plugin place this file?

I want to change the port that tailscale listens on for incoming connections. where/how can I do that so that it stays persistent? Specifically, I want to change the default port 41641 to something else.

I have the tailscale plugin up and running and it works for the most part, but i can‘t access any IPs on the br0 interface. I have a bunch of docker containers on the br0 interface. Accessing their IPs doesn’t work. I have already advertised the subnet and enabled it in the tailscale management interface. I can access all VMs running on unraid and even the web interface of my router in my LAN. Only the IPs on the br0 interface don’t work. any ideas? update: I solved it myself by enabling "Host access to custom networks" in the docker settings in unraid. Is this a "dangerous" setting? The help text says that I should know what I am doing before enabling it. In which context could this setting be problematic? tailscale-diag-20231217-012807.zip