cinsun42

Members
  • Posts

    4
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

cinsun42's Achievements

Noob

Noob (1/14)

2

Reputation

  1. So simple, that works perfectly. Thank you!
  2. First off, thank you for this awesome plugin! I initially attempted to set up set up my NUT server on pfsense, but I struggled with a bunch of connection issues right from the start so this was my next best alternative. For some background I have a pretty old UPS that I purchased in 2014, specifically the CyberPower CP1500AVRLCD. It doesn't look anything like the current model that is shown on their website - its has a blue display and rubberized power button that lights up blue, if anyone is familiar. In terms of autodetection with the NUT plugin, everything seems to be fine in terms of detecting the correct model (https://networkupstools.org/ddl/Cyber_Power_Systems/CP1500AVRLCD.html) However, I think some of the parameters that have been predefined are causing the power draw to be reported incorrectly. Specifically, it only reports about 50% of what is shown on the UPS display and the apcupsd plugin (I'm not using this plugin simultaneously btw). My assumption is that since battery.voltage.nominal is set to 12 and I have two 12 volt batteries wired in series in this UPS, it is incorrectly reporting the power draw. The confusing part is that battery.voltage reports around 13.8-13.9, so that somewhat invalidates my theory. Any thoughts on how I might go about addressing this issue? Can I just make some ups.conf adjustments myself, or are these fields not user definable? I'm attaching my current configuration for reference, I'd appreciate any help you can provide! EDIT: I just noticed ups.realpower.nominal is reported as 388 - I assume this should state 900 for my UPS
  3. You were absolutely right, there was a conflict with Plex. I don't care to utilize L2 discovery with the unifi controller so I removed the port 1900 line completely and it installed without issue. Many thanks!
  4. Hi all, could use some help diagnosing this issue. I'm getting an error on container install right out of the gate, here is the log: docker run -d --name='unifi-controller-reborn' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="unRAID.Server" -e HOST_CONTAINERNAME="unifi-controller-reborn" -e 'MEM_LIMIT'='4096' -e 'MEM_STARTUP'='2048' -e 'UMASK'='002' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='https://[IP]:[PORT:8443]' -l net.unraid.docker.icon='https://user-images.githubusercontent.com/11403137/277435263-1b01facd-1b15-4ba7-9495-e709c291d67f.jpg' -p '8443:8443/tcp' -p '3478:3478/udp' -p '10001:10001/udp' -p '8080:8080/tcp' -p '1900:1900/udp' -p '8843:8843/tcp' -p '8880:8880/tcp' -p '6789:6789/tcp' -p '5514:5514/udp' -v '/mnt/user/appdata/unifi-controller-reborn':'/unifi/var':'rw' --memory=8G '11notes/unifi:7.5.187-unraid' 15abcafd03f2dfa0c76eda1003a99088e41973fb6d750a7b44bfb3d064b4113b docker: Error response from daemon: driver failed programming external connectivity on endpoint unifi-controller-reborn (1fcf720f1c65810e0c6fad7cac6e72cc211ef6d950e7e556fccd90966dcfce86): Error starting userland proxy: listen udp4 0.0.0.0:1900: bind: address already in use. The command failed. I've looked at the port allocations for my other docker containers and I don't see any reference to port 1900, so I'm not seeing where the conflict is. Any other ideas where I can start looking to resolve this?