batscarfacehypernova

Since it appears that the subheading may have been changed since this was posted, here's the current link: https://docs.unraid.net/unraid-os/using-unraid-to/manage-storage/array/replacing-disks-in-array/#re-enabling-a-disabled-disk-rebuilding-onto-itself

It's assigned to host. I've tried the others as well, as well as assigning it directly to the network interface and giving it its own ip.

Hi guys, I've been banging my head against the walls trying to figure out what the hell might be making Plex's remote access unhappy. I have a static IP, and normally my ISP shouldn't be doing CGNAT, but for some reason, things aren't working. Now that I figured out that by default, Wireguard on UnRaid means "everyone gets wireguard", Plex's connection checker is correctly reporting my external IP. canyouseeme.org reports the port as closed. The OpnSense rule is copied from another sever I have running on another port. That one reports as open, no problem, which would point to the issue being with UnRaid. I've checked the rules multiple times. I've edited the source rule with the IP to the UnRaid server, and swapped ports around inside of Plex: port closed from canyouseeme. Here's iptables on the UnRaid box: root@Tower:~# iptables -L -n Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination DOCKER-USER all -- 0.0.0.0/0 0.0.0.0/0 DOCKER-ISOLATION-STAGE-1 all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED DOCKER all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ctstate RELATED,ESTABLISHED DOCKER all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 WIREGUARD all -- 0.0.0.0/0 0.0.0.0/0 Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain DOCKER (2 references) target prot opt source destination ACCEPT tcp -- 0.0.0.0/0 172.31.200.2 tcp dpt:8989 ACCEPT tcp -- 0.0.0.0/0 172.31.200.2 tcp dpt:9897 ACCEPT tcp -- 0.0.0.0/0 172.17.0.2 tcp dpt:9696 ACCEPT tcp -- 0.0.0.0/0 172.17.0.3 tcp dpt:5055 ACCEPT tcp -- 0.0.0.0/0 172.31.200.3 tcp dpt:6789 ACCEPT tcp -- 0.0.0.0/0 172.31.200.4 tcp dpt:7878 ACCEPT tcp -- 0.0.0.0/0 172.31.200.5 tcp dpt:8989 Chain DOCKER-ISOLATION-STAGE-1 (1 references) target prot opt source destination DOCKER-ISOLATION-STAGE-2 all -- 0.0.0.0/0 0.0.0.0/0 DOCKER-ISOLATION-STAGE-2 all -- 0.0.0.0/0 0.0.0.0/0 RETURN all -- 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-ISOLATION-STAGE-2 (2 references) target prot opt source destination DROP all -- 0.0.0.0/0 0.0.0.0/0 DROP all -- 0.0.0.0/0 0.0.0.0/0 RETURN all -- 0.0.0.0/0 0.0.0.0/0 Chain DOCKER-USER (1 references) target prot opt source destination RETURN all -- 0.0.0.0/0 0.0.0.0/0 Chain WIREGUARD (1 references) target prot opt source destination Here's ss on the UnRaid box: root@Tower:~# ss -tuln | grep 32400 tcp LISTEN 0 1024 0.0.0.0:32400 0.0.0.0:* Here's from inside the docker: # awk 'NR>1 && $4=="0A" && toupper(substr($2,10,4))=="7E90"{print "LISTEN on port 32400 (row:",$0,")"}' /proc/net/tcp LISTEN on port 32400 (row: 19: 00000000:7E90 00000000:0000 0A 00000000:00000000 00:00000000 00000000 99 0 27804597 1 000000001f001745 100 0 0 10 0 ) Anyone got a clue as to what I might be missing here ?

Ah, that makes more sense - thanks !!!

@ich777, I don't seem to be able to find the Zabbix-server or Zabbix-Webinterface dockers either in your repo or from a community apps search. Any clues as to what I may be doing wrong ?

Yeah, figured this wasn't the one to cut my dockerisation newbie teeth on... looks like it's VM time, folks ! (and thanks for taking the time to look into it, @Squid)

Hey guys, would anyone with the knowledge on how to do this be willing to take the time to make an UnRaid template for this PFSense log visualiser ?

For those with adoption problems, this seems to have done the trick. It'd been mentioned here, but without a walkthrough. For some reason, the GUI approach didn't work for me. TL;DR: ssh into the AP. then mca-cli Now issue the set-inform command with the IP address of your Unifi controller [in our case, the IP of your UnRaid box. Don't forget to change to the correct port if you're not allocating 8080 to the controller]. set-inform http://192.168.3.2:8080/inform

Also, there's this cute little kink with the SM BMC where you need to physically unplug the device to make it reset and actually apply the cooling profile... lowering the thresholds fixed the rest of it, thanks a lot for the hint !!! (while I'm at it - I'd also corrected the temp thresholds for the M.2, since they're significantly higher than what you'd have for those spinny 60's things we still have to live with for the time being... not sure it had any effect other than no more blinky gifs, which is something)

And useful to stop the SM boards from the annoying cycling thing, too I'd tried the raw commands, they seemed to go through but don't seem to have any effect. Thanks for the pointer - forgot to mention I'd already set the IPMI to optimal. Best I can see is an error during boot with ipmifan saying the motherboard isn't supported yet...

Hey, I'm having this weird annoying issue with a Supermicro X10 xeon-d board, which had the SM "cycling" thing going at default... Switched a few things around in the IPMI settings, and the board will now boot with fans at a reasonable speed, which'll ramp up to full-on after a minute or so, so I'd suspect only once Unraid loads... I mean, it's not throwing errors or anything, it's mostly that it probably makes the box noiser than it could or should be... (I've tried putting the upper thresholds to proper variants of the manufacturer's max speeds, didn't change a thing, and also tried adding the Dynamix temp/autofan plugins on top, no luck with that, can't detect the PWM controller or any other temp sensor than the CPU's coretemp) Any clue as to what I'm doing wrong ? Section 607_FAN1 ## this is the silent wings case fan ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 1600.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 1700.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 1800.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 674_FAN2 ## this is a noctua 92mm ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 741_FAN3 ## this is a noctua F12 ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection Section 808_FAN4 EndSection Section 875_FANA ## this is a noctua 92mm ## Possible values: Yes/No Enable_All_Event_Messages Yes ## Possible values: Yes/No Enable_Scanning_On_This_Sensor Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Assertion_Event_Upper_Non_Recoverable_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Critical_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Lower_Non_Recoverable_Going_Low Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Critical_Going_High Yes ## Possible values: Yes/No Enable_Deassertion_Event_Upper_Non_Recoverable_Going_High Yes ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Critical_Threshold 400.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Critical_Threshold 300.000000 ## Give valid input for sensor type = Fan; units = RPM Lower_Non_Recoverable_Threshold 200.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Critical_Threshold 2100.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Critical_Threshold 2400.000000 ## Give valid input for sensor type = Fan; units = RPM Upper_Non_Recoverable_Threshold 22000.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Positive_Going_Threshold_Hysteresis 100.000000 ## Give valid input for sensor type = Fan; units = RPM; 'None' to not use hysteresis Negative_Going_Threshold_Hysteresis 100.000000 EndSection