Mainfrezzer

That seems to be the normal modus operandi for the unraid-api docker, if its the same were talking about. It seems to scrape the webui and you do have to enter your credentials.

Try adding 1.1.1.1 or 8.8.8.8 as dns in unraids networksettings and see if that fixes it.

The Server under 5.X.XXX.112 doesnt seem to have a dns server running

So, ive set it up on my end for visual guidance.

Binhex

 


Chrome:



What you need to enter into the binhex console
 
iptables -A OUTPUT -s 172.17.0.0/16 -d 10.0.0.0/24 -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT && iptables -A INPUT -s 10.0.0.0/24 -d 172.17.0.0/16 -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT
Change the 10.0.0.0/24 to whatever your network is. 192.168.0.0/24 for example.

Now you can access your Binhex Interface on UNRAID-IP:8181 and your chrome docker is UNRAID-IP:8080


From the chrome docker you can just access the rest from the 172.17.0.X:PORT



As mentioned before, if you go the privoxy route, which i highly recommend, it looks like this:

You change in binhex the Key 8: (ENABLE_PRIVOXY) to "yes"

you open your firefox, chrome, edge, whatever. Go to setting and search for "Proxy"

You set the http proxy to your unraidip:8118

now your browser gets routed through the vpn container and can access 172.17.0.X natively and you dont need to use the iptables command on every binhex-container start.

Die ganze Konfiguration war schon richtig. Das Problem ist der Speedport bzw Unraids implementierung von Wireguard. Das ausbleiben von "Ping" antworten, ich hab nicht genau geguckt welche spezifische icmp Abfrage da gestartet wird, macht Unraids Wireguardclient unnutzbar. Wundert mich dass das nicht schon vorher bemerkt wurde. Die ollen Telekomrouter sind ja doch sehr verbreitet. Aber ich denke mal dass die Leute die sowas hier aufsetzen ne Fritzbox haben und die hat, solange man nicht die Box manipuliert, keine möglichkeit ipv4 icmp anfragen zu blocken.

Achja:
Ich habs jetzt einfach so gelassen dass sich Server 2 zu Server 1 verbindet. Ist ja im Endeffekt egal und wahrscheinlich auch besser weil so Server 1 nicht warten muss dass die öffentliche IP von Server 2 geupdated wird.

The auto-start order is determined by the order the containers are listed on the docker page, from top to bottom. Pre 6.12 you can just drag and drop to change the order, Post 6.12 you need to hit the little lock icon on the right hand side of the menu bar before youre able to do so.

your nic, which i assume is in this case eth1 should show up there and then youll have this option there



that turns eth1 into br1



this is how its looking for me right now

xfs is only available for single disk pools. your option would be zfs mirror in that case.

As it has been said earlier, that's impossible currently with the Filemanager (from unraid share/disk to ud). Krusader with the mountpoint /mnt works for me perfectly fine as gui. You could also export the UD disk/remote share via SMB and copy that way.

the auto tune is too aggresive and turns off the NIC when theres absolutely nothing going on on the network and never turns it back on again. Had that happen to me aswell. 

 
# ------------------------------------------------- # Set power-efficient CPU governor # ------------------------------------------------- #/etc/rc.d/rc.cpufreq powersave # ------------------------------------------------- # Enable power-efficient ethernet # ------------------------------------------------- # enable IEEE 802.3az (Energy Efficient Ethernet): Could be incompatible to LACP bonds! #for i in /sys/class/net/eth?; do dev=$(basename $i); [[ $(echo $(ethtool --show-eee $dev 2> /dev/null) | grep -c "Supported EEE link modes: 1") -eq 1 ]] && ethtool --set-eee $dev eee on; done # Disable wake on lan #for i in /sys/class/net/eth?; do ethtool -s $(basename $i) wol d; done # ------------------------------------------------- # powertop tweaks # ------------------------------------------------- # Enable SATA link power management echo med_power_with_dipm | tee /sys/class/scsi_host/host*/link_power_management_policy # Runtime PM for I2C Adapter (i915 gmbus dpb) #echo auto | tee /sys/bus/i2c/devices/i2c-*/device/power/control # Autosuspend for USB device echo auto | tee /sys/bus/usb/devices/*/power/control # Runtime PM for disk echo auto | tee /sys/block/sd*/device/power/control # Runtime PM for PCI devices #echo auto | tee /sys/bus/pci/devices/????:??:??.?/power/control # Runtime PM for ATA devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/ata*/power/control

This is my setting. the cpu govenor is disabled because i franky dont need it and the effient ethernet bit is the problematic one, that also why its disabled. auto tune just turns that one on.

so you can basically remove the auto tune line and replace it with just this

 
# ------------------------------------------------- # powertop tweaks # ------------------------------------------------- # Enable SATA link power management echo med_power_with_dipm | tee /sys/class/scsi_host/host*/link_power_management_policy # Runtime PM for I2C Adapter (i915 gmbus dpb) #echo auto | tee /sys/bus/i2c/devices/i2c-*/device/power/control # Autosuspend for USB device echo auto | tee /sys/bus/usb/devices/*/power/control # Runtime PM for disk echo auto | tee /sys/block/sd*/device/power/control # Runtime PM for PCI devices #echo auto | tee /sys/bus/pci/devices/????:??:??.?/power/control # Runtime PM for ATA devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/ata*/power/control

For you current problem, not being able to access the server, you can only get it done by hooking up a keyboard to it and running cmds to try to bring the nic back up or shutdown to the server to make the modifications on the usb drive so that never happens again.


Edit:

or also the (Runtime PM for I2C Adapter (i915 gmbus dpb) i cant remember why i turned it off, i know it had a reason but honestly i have no clue why now

Edit #2:

I did see that the PCI Devices is disabled/commented out, thats was on my end the important second line because my NIC is treated as PCI device. But you would have to check how it works in your setup.

So to sum it up, once again

 
# ------------------------------------------------- # powertop tweaks # ------------------------------------------------- # Enable SATA link power management echo med_power_with_dipm | tee /sys/class/scsi_host/host*/link_power_management_policy # Autosuspend for USB device echo auto | tee /sys/bus/usb/devices/*/power/control # Runtime PM for disk echo auto | tee /sys/block/sd*/device/power/control # Runtime PM for ATA devices echo auto | tee /sys/bus/pci/devices/????:??:??.?/ata*/power/control Should work out but it depends on what you have as a system. 
Thats a link for a bit more information on it
https://forums.unraid.net/topic/98070-reduce-power-consumption-with-powertop/

You have to have something, a usb thumbdrive for example, in Disk 1 of the Array. Currently you're unable to start "Unraid" without a single device in the "Unraid Array"

I wouldn't bet on that since
I'm certain it's due to the switch time, especially since the Synology worked fine. Either the ups specsheet is lying or the evga psu is not up to spec

Thats even too much efford put in^^

all you need to do is literally this 
 

This.mp4    

Klingt stark nach Host Access enabled. Da müsste man manuell den Adapter ändern in der wireguard config.
 
Mit dem neuen System in 12.4 hab ich's noch nicht ausprobiert, in den vorherigen Versionen musste man in der config von z.b. br0 die 4 Einträge auf shim-br0 ändern. Problem dass da auftreten kann ist allerdings dass wenn der Server mal Probleme hat und das Array nicht läuft, man nicht mehr drauf kommt. Kann natürlich gelöst werden indem man 2 Verbindungen einrichtet und nur einen davon auf das shim Interface wechselt. Dann hat man nen Backup. Im Notfall. Hatte das hier auch Mal ins Forums gepostet vor Ner ganzen Weile für 6.11.5 glaube ich.
 
Für 6.12.4 müsste ich tatsächlich Mal später gucken. Stecke gerade noch im Zug fest


Update:

6.12.4 ist das selbe, schimpft sich jetzt nur vhost0 statt eth0 (bei macvlan setups, was ich hier jetzt mal ganz stark annehme)
 

In der rechten Menuleiste das grüne Schloss anklicken, dann klappt das verschieben.

Ist seit 6.12.X neu.

Docker stoppen. In den Docker Einstellungen das "Docker directory:" löschen. Docker starten, die Apps(Docker-Container) aus dem Community App Store wieder installieren. 

Man kann Docker selbst nicht einfach 1:1 über verschiedene Dateisysteme kopieren. XFS benutzt overlay2, Btrfs irgendwas und zfs benutzt zfs.

Der Appdata share beinhaltet die permanenten Daten, die wichtig sind. Alles im /system/docker ist absolut verwerfbar (bis eventuell auf die Netzwerkkonfiguartionsdatei)

https://forums.unraid.net/topic/78993-solved-how-to-create-a-virtual-nic-for-internalisolated-use-only/

Weiter unten in dem Thema wird erläutert wie man Docker den Virtuellen Nic verwenden lässt. Ist ordentliches Gefummel.
Viel Glück mit PFSense, OPNsense hatte mir weniger Kopfweh bereitet.


(Persönlicher Ratschlag basierend auf meiner Erfahrung. Es ist wesentlich einfacher, so lange man nur Webservices braucht und zufälligerweise eine Fritzbox hat, nen USB to Ethernet Adapter zu besorgen. Die Dockercontainer auf den USB NIC zu legen und dann bei der Fritzbox ins Gastnetz zu werfen. Cloudflare ist da tatsächlich auch ein ganz nützliches Tool, da man ja keine Ports freigeben kann, allerdings ja wunderbar raus kommt  )

Wanted to give an Update. I actually found a solution to my surprise. I recently bought a USB3 to Ethernet Dongle and just shoved it in there. It supports being bridged and to my surprise, now it acutally keeps the same IP6 Identifier. So this is a single NIC-Bridge Problem.