DuckWaze

This solved it for me to, Would me nice to get a option in tailscale plugin or fix for this.

@vw-kombi Do know if it always is "ip route add 100.64.0.0/10 dev tailscale1" ? Adding "ip route add 100.64.0.0/10 dev tailscale1" will only allow communication out to the fairphone right? So is ip route add 100.0.0.0/10 dev tailscale1" not the way to go? So that all devices can connect to the dockers? I do have the following tailscale devices: fairphone 100.64.x.x. Framework 100.94.x.x Proxmox 100.78.X.x UbuntuVM 100.97.x.X I have posted the same issue at https://forums.unraid.net/topic/196689-cant-acces-docker-with-tailscale-addres-trough-imported-wireguard-setup/#comment-1603519

Hello, With spaceinvador's i added a wire-guard Tunnel wg0 and with BitTorrent, for the most part it is working now i do get a WAN ip from from the eindpoint of de VPN. But when connecting with gui with tailscale ip i can't connected to the docker that has the wg0 network. Adding "ip route add 100.64.0.0/10 dev tailscale1" will only allow communication out to the fairphone right? So is ip route add 100.0.0.0/10 dev tailscale1" not the way to go? So that all devices can connect to the dockers? I do have the following tailscale devices: fairphone 100.64.x.x. Framework 100.94.x.x Proxmox 100.78.X.x UbuntuVM 100.97.x.X I saw the post of @vw-kombi put was wondering if adding "ip route add 100.64.0.0/10 dev tailscale1" is always the IP to addd. Because my tailscale ip is 100.81.x.x , Do i need to change the command to "ip route add 100.81.0.0/10 dev tailscale1" ? Is there a setting in the tailscale plugin or Wireguard network settings that allows this? When i want to run other docker containers on wg1 or wg2, ect will this also work? https://forums.unraid.net/topic/195755-using-wireguard-on-some-containers-to-access-vpn-this-stops-tailscale-from-accessing-the-container/#comment-1596813 Thanks in advance.

Hello, Just checking out if this is a future of a bug, but when i import a Wireguard config. The Local tunnel network pool stayś the same after every new wg0,wg1,wg2,wg3, ect. This is causing the issue that the handshake works but there is no network for the docker for example. Is this part of the issue with 7.2.2.?

LibreWolf. I do have issue's with not reading a log file or the terminal because u am unable to scroll down, Did a quick screen record of the issue. Than i have to zoom in/out to see the outcome Screencast From 2026-01-20 19-34-01.mp4

I also get a error installing a docker container with basic settings: Pulling image: lscr.io/linuxserver/librewolf:latest IMAGE ID [1731850543]: Pulling from linuxserver/librewolf. IMAGE ID [836152278c69]: Pulling fs layer. Downloading 100% of 30 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [c0f8eff906b8]: Pulling fs layer. Downloading 100% of 6 KB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [ec93c2cc9132]: Pulling fs layer. Downloading 100% of 1 KB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [3fd182487319]: Pulling fs layer. Downloading 100% of 703 B. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [5ea0e1d4cf5c]: Pulling fs layer. Downloading 100% of 427 B. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [a87fa2b784b1]: Pulling fs layer. Downloading 100% of 19 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [5a7d20a279ba]: Pulling fs layer. Downloading 100% of 4 KB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [258e6daccb85]: Pulling fs layer. Downloading 100% of 2 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [98aefebfe342]: Pulling fs layer. Downloading 100% of 20 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [90b6b7dceefc]: Pulling fs layer. Downloading 100% of 781 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [017adfba0d4a]: Pulling fs layer. Downloading 100% of 14 KB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [db62ed77d27e]: Pulling fs layer. Downloading 100% of 137 MB. Verifying Checksum. Download complete. Extracting. Pull complete. IMAGE ID [4932d558e2e5]: Pulling fs layer. Downloading 100% of 427 B. Verifying Checksum. Download complete. Extracting. Pull complete. Status: Downloaded newer image for lscr.io/linuxserver/librewolf:latest TOTAL DATA PULLED: 989 MB Command execution docker run -d --name='librewolf' --net='bridge' --pids-limit 2048 -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Tower" -e HOST_CONTAINERNAME="librewolf" -e 'LIBREWOLF_CLI'='https://www.linuxserver.io/' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:3000]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/librewolf-logo.png' -v '/mnt/user/appdata/librewolf':'/config':'rw' --shm-size=1gb 'lscr.io/linuxserver/librewolf' unexpected fault address 0x456e2d8d fatal error: fault [signal SIGSEGV: segmentation violation code=0x1 addr=0x456e2d8d pc=0xf2aec0] goroutine 1 [running]: runtime.throw({0x201512?, 0xc00046fb00?}) /usr/local/go/src/runtime/panic.go:1077 +0x5e fp=0xc0002df710 sp=0xc0002df6e0 pc=0x441e1e runtime.sigpanic() /usr/local/go/src/runtime/signal_unix.go:875 +0x285 fp=0xc0002df770 sp=0xc0002df710 pc=0x458465 github.com/docker/cli/cli/command/trust.newInspectCommand({0x120d4b8, 0xc000151680}) /go/src/github.com/docker/cli/cli/command/trust/inspect.go:26 fp=0xc0002df778 sp=0xc0002df770 pc=0xf2aec0 github.com/docker/cli/cli/command/trust.NewTrustCommand({0x120d4b8, 0xc000151680}) /go/src/github.com/docker/cli/cli/command/trust/cmd.go:22 +0x171 fp=0xc0002df808 sp=0xc0002df778 pc=0xf28731 github.com/docker/cli/cli/command/commands.AddCommands(0x120d4b8?, {0x120d4b8?, 0xc000151680}) /go/src/github.com/docker/cli/cli/command/commands/commands.go:55 +0x445 fp=0xc0002dfc10 sp=0xc0002df808 pc=0xf36a65 main.newDockerCommand(0xc000151680) /go/src/github.com/docker/cli/cmd/docker/docker.go:113 +0x4f8 fp=0xc0002dfcf8 sp=0xc0002dfc10 pc=0xf3aa38 main.runDocker({0x1202798?, 0xc000128bc0}, 0xc000151680) /go/src/github.com/docker/cli/cmd/docker/docker.go:350 +0x5d fp=0xc0002dfe78 sp=0xc0002dfcf8 pc=0xf3c03d main.dockerMain() /go/src/github.com/docker/cli/cmd/docker/docker.go:50 +0x1f9 fp=0xc0002dff28 sp=0xc0002dfe78 pc=0xf3a2b9 main.main() /go/src/github.com/docker/cli/cmd/docker/docker.go:32 +0x13 fp=0xc0002dff40 sp=0xc0002dff28 pc=0xf3a093 runtime.main() /usr/local/go/src/runtime/proc.go:267 +0x2d2 fp=0xc0002dffe0 sp=0xc0002dff40 pc=0x4448b2 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc0002dffe8 sp=0xc0002dffe0 pc=0x4753a1 goroutine 2 [force gc (idle)]: runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc00006cfa8 sp=0xc00006cf88 pc=0x444d0e runtime.goparkunlock(...) /usr/local/go/src/runtime/proc.go:404 runtime.forcegchelper() /usr/local/go/src/runtime/proc.go:322 +0xb8 fp=0xc00006cfe0 sp=0xc00006cfa8 pc=0x444b98 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc00006cfe8 sp=0xc00006cfe0 pc=0x4753a1 created by runtime.init.6 in goroutine 1 /usr/local/go/src/runtime/proc.go:310 +0x1a goroutine 3 [GC sweep wait]: runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc00006d778 sp=0xc00006d758 pc=0x444d0e runtime.goparkunlock(...) /usr/local/go/src/runtime/proc.go:404 runtime.bgsweep(0x0?) /usr/local/go/src/runtime/mgcsweep.go:280 +0x94 fp=0xc00006d7c8 sp=0xc00006d778 pc=0x42fc54 runtime.gcenable.func1() /usr/local/go/src/runtime/mgc.go:200 +0x25 fp=0xc00006d7e0 sp=0xc00006d7c8 pc=0x424dc5 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc00006d7e8 sp=0xc00006d7e0 pc=0x4753a1 created by runtime.gcenable in goroutine 1 /usr/local/go/src/runtime/mgc.go:200 +0x66 goroutine 4 [GC scavenge wait]: runtime.gopark(0xc00007e000?, 0x3eaba0?, 0x1?, 0x0?, 0xc0000071e0?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc00006df70 sp=0xc00006df50 pc=0x444d0e runtime.goparkunlock(...) /usr/local/go/src/runtime/proc.go:404 runtime.(*scavengerState).park(0x1ad0d80) /usr/local/go/src/runtime/mgcscavenge.go:425 +0x49 fp=0xc00006dfa0 sp=0xc00006df70 pc=0x42d529 runtime.bgscavenge(0x0?) /usr/local/go/src/runtime/mgcscavenge.go:653 +0x3c fp=0xc00006dfc8 sp=0xc00006dfa0 pc=0x42dabc runtime.gcenable.func2() /usr/local/go/src/runtime/mgc.go:201 +0x25 fp=0xc00006dfe0 sp=0xc00006dfc8 pc=0x424d65 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc00006dfe8 sp=0xc00006dfe0 pc=0x4753a1 created by runtime.gcenable in goroutine 1 /usr/local/go/src/runtime/mgc.go:201 +0xa5 goroutine 5 [finalizer wait]: runtime.gopark(0x198?, 0x11e51e0?, 0x1?, 0x5e?, 0x0?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc00006c620 sp=0xc00006c600 pc=0x444d0e runtime.runfinq() /usr/local/go/src/runtime/mfinal.go:193 +0x107 fp=0xc00006c7e0 sp=0xc00006c620 pc=0x423de7 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc00006c7e8 sp=0xc00006c7e0 pc=0x4753a1 created by runtime.createfing in goroutine 1 /usr/local/go/src/runtime/mfinal.go:163 +0x3d goroutine 19 [select, locked to thread]: runtime.gopark(0xc00006e7a8?, 0x2?, 0x60?, 0xe6?, 0xc00006e7a4?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc00006e638 sp=0xc00006e618 pc=0x444d0e runtime.selectgo(0xc00006e7a8, 0xc00006e7a0, 0x0?, 0x0, 0xc00012a010?, 0x1) /usr/local/go/src/runtime/select.go:327 +0x725 fp=0xc00006e758 sp=0xc00006e638 pc=0x454885 runtime.ensureSigM.func1() /usr/local/go/src/runtime/signal_unix.go:1014 +0x1a5 fp=0xc00006e7e0 sp=0xc00006e758 pc=0x46c0e5 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc00006e7e8 sp=0xc00006e7e0 pc=0x4753a1 created by runtime.ensureSigM in goroutine 1 /usr/local/go/src/runtime/signal_unix.go:997 +0xc8 goroutine 34 [syscall]: runtime.notetsleepg(0x0?, 0x0?) /usr/local/go/src/runtime/lock_futex.go:236 +0x29 fp=0xc0000687a0 sp=0xc000068768 pc=0x416789 os/signal.signal_recv() /usr/local/go/src/runtime/sigqueue.go:152 +0x29 fp=0xc0000687c0 sp=0xc0000687a0 pc=0x471a89 os/signal.loop() /usr/local/go/src/os/signal/signal_unix.go:23 +0x13 fp=0xc0000687e0 sp=0xc0000687c0 pc=0xb7a973 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc0000687e8 sp=0xc0000687e0 pc=0x4753a1 created by os/signal.Notify.func1.1 in goroutine 1 /usr/local/go/src/os/signal/signal.go:151 +0x1f goroutine 20 [select]: runtime.gopark(0xc0003e07b0?, 0x2?, 0x0?, 0x0?, 0xc0003e079c?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc0003e0648 sp=0xc0003e0628 pc=0x444d0e runtime.selectgo(0xc0003e07b0, 0xc0003e0798, 0x0?, 0x0, 0x0?, 0x1) /usr/local/go/src/runtime/select.go:327 +0x725 fp=0xc0003e0768 sp=0xc0003e0648 pc=0x454885 os/signal.NotifyContext.func1() /usr/local/go/src/os/signal/signal.go:288 +0x66 fp=0xc0003e07e0 sp=0xc0003e0768 pc=0xb7a566 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc0003e07e8 sp=0xc0003e07e0 pc=0x4753a1 created by os/signal.NotifyContext in goroutine 1 /usr/local/go/src/os/signal/signal.go:287 +0x165 The command failed.

Hi Jorge, The system is now running with plugins and array stable for 8 day's. Today i tried to enable docker and start to install the dockers. When i try to make a custom docker network for the dockers "dockernet" i get the following error. Thanks again: ) root@Tower:~# docker network create dockernet unexpected fault address 0x456e2d8d fatal error: fault [signal SIGSEGV: segmentation violation code=0x1 addr=0x456e2d8d pc=0xf2aec0] goroutine 1 [running]: runtime.throw({0x201512?, 0xc0004c7b00?}) /usr/local/go/src/runtime/panic.go:1077 +0x5e fp=0xc0002df710 sp=0xc0002df6e0 pc=0x441e1e runtime.sigpanic() /usr/local/go/src/runtime/signal_unix.go:875 +0x285 fp=0xc0002df770 sp=0xc0002df710 pc=0x458465 github.com/docker/cli/cli/command/trust.newInspectCommand({0x120d4b8, 0xc00040a000}) /go/src/github.com/docker/cli/cli/command/trust/inspect.go:26 fp=0xc0002df778 sp=0xc0002df770 pc=0xf2aec0 github.com/docker/cli/cli/command/trust.NewTrustCommand({0x120d4b8, 0xc00040a000}) /go/src/github.com/docker/cli/cli/command/trust/cmd.go:22 +0x171 fp=0xc0002df808 sp=0xc0002df778 pc=0xf28731 github.com/docker/cli/cli/command/commands.AddCommands(0x120d4b8?, {0x120d4b8?, 0xc00040a000}) /go/src/github.com/docker/cli/cli/command/commands/commands.go:55 +0x445 fp=0xc0002dfc10 sp=0xc0002df808 pc=0xf36a65 main.newDockerCommand(0xc00040a000) /go/src/github.com/docker/cli/cmd/docker/docker.go:113 +0x4f8 fp=0xc0002dfcf8 sp=0xc0002dfc10 pc=0xf3aa38 main.runDocker({0x1202798?, 0xc00031b400}, 0xc00040a000) /go/src/github.com/docker/cli/cmd/docker/docker.go:350 +0x5d fp=0xc0002dfe78 sp=0xc0002dfcf8 pc=0xf3c03d main.dockerMain() /go/src/github.com/docker/cli/cmd/docker/docker.go:50 +0x1f9 fp=0xc0002dff28 sp=0xc0002dfe78 pc=0xf3a2b9 main.main() /go/src/github.com/docker/cli/cmd/docker/docker.go:32 +0x13 fp=0xc0002dff40 sp=0xc0002dff28 pc=0xf3a093 runtime.main() /usr/local/go/src/runtime/proc.go:267 +0x2d2 fp=0xc0002dffe0 sp=0xc0002dff40 pc=0x4448b2 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc0002dffe8 sp=0xc0002dffe0 pc=0x4753a1 goroutine 2 [force gc (idle)]: runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc000072fa8 sp=0xc000072f88 pc=0x444d0e runtime.goparkunlock(...) /usr/local/go/src/runtime/proc.go:404 runtime.forcegchelper() /usr/local/go/src/runtime/proc.go:322 +0xb8 fp=0xc000072fe0 sp=0xc000072fa8 pc=0x444b98 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc000072fe8 sp=0xc000072fe0 pc=0x4753a1 created by runtime.init.6 in goroutine 1 /usr/local/go/src/runtime/proc.go:310 +0x1a goroutine 3 [GC sweep wait]: runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc000073778 sp=0xc000073758 pc=0x444d0e runtime.goparkunlock(...) /usr/local/go/src/runtime/proc.go:404 runtime.bgsweep(0x0?) /usr/local/go/src/runtime/mgcsweep.go:280 +0x94 fp=0xc0000737c8 sp=0xc000073778 pc=0x42fc54 runtime.gcenable.func1() /usr/local/go/src/runtime/mgc.go:200 +0x25 fp=0xc0000737e0 sp=0xc0000737c8 pc=0x424dc5 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc0000737e8 sp=0xc0000737e0 pc=0x4753a1 created by runtime.gcenable in goroutine 1 /usr/local/go/src/runtime/mgc.go:200 +0x66 goroutine 4 [GC scavenge wait]: runtime.gopark(0xc00007c000?, 0x3eaba0?, 0x1?, 0x0?, 0xc0000071e0?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc000073f70 sp=0xc000073f50 pc=0x444d0e runtime.goparkunlock(...) /usr/local/go/src/runtime/proc.go:404 runtime.(*scavengerState).park(0x1ad0d80) /usr/local/go/src/runtime/mgcscavenge.go:425 +0x49 fp=0xc000073fa0 sp=0xc000073f70 pc=0x42d529 runtime.bgscavenge(0x0?) /usr/local/go/src/runtime/mgcscavenge.go:653 +0x3c fp=0xc000073fc8 sp=0xc000073fa0 pc=0x42dabc runtime.gcenable.func2() /usr/local/go/src/runtime/mgc.go:201 +0x25 fp=0xc000073fe0 sp=0xc000073fc8 pc=0x424d65 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc000073fe8 sp=0xc000073fe0 pc=0x4753a1 created by runtime.gcenable in goroutine 1 /usr/local/go/src/runtime/mgc.go:201 +0xa5 goroutine 5 [finalizer wait]: runtime.gopark(0x198?, 0x11e51e0?, 0x1?, 0x5e?, 0x0?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc000072620 sp=0xc000072600 pc=0x444d0e runtime.runfinq() /usr/local/go/src/runtime/mfinal.go:193 +0x107 fp=0xc0000727e0 sp=0xc000072620 pc=0x423de7 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc0000727e8 sp=0xc0000727e0 pc=0x4753a1 created by runtime.createfing in goroutine 1 /usr/local/go/src/runtime/mfinal.go:163 +0x3d goroutine 8 [select, locked to thread]: runtime.gopark(0xc0000747a8?, 0x2?, 0xb5?, 0x8?, 0xc0000747a4?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc000074638 sp=0xc000074618 pc=0x444d0e runtime.selectgo(0xc0000747a8, 0xc0000747a0, 0x0?, 0x0, 0xc00016d060?, 0x1) /usr/local/go/src/runtime/select.go:327 +0x725 fp=0xc000074758 sp=0xc000074638 pc=0x454885 runtime.ensureSigM.func1() /usr/local/go/src/runtime/signal_unix.go:1014 +0x1a5 fp=0xc0000747e0 sp=0xc000074758 pc=0x46c0e5 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc0000747e8 sp=0xc0000747e0 pc=0x4753a1 created by runtime.ensureSigM in goroutine 1 /usr/local/go/src/runtime/signal_unix.go:997 +0xc8 goroutine 9 [syscall]: runtime.notetsleepg(0x0?, 0x0?) /usr/local/go/src/runtime/lock_futex.go:236 +0x29 fp=0xc000074fa0 sp=0xc000074f68 pc=0x416789 os/signal.signal_recv() /usr/local/go/src/runtime/sigqueue.go:152 +0x29 fp=0xc000074fc0 sp=0xc000074fa0 pc=0x471a89 os/signal.loop() /usr/local/go/src/os/signal/signal_unix.go:23 +0x13 fp=0xc000074fe0 sp=0xc000074fc0 pc=0xb7a973 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc000074fe8 sp=0xc000074fe0 pc=0x4753a1 created by os/signal.Notify.func1.1 in goroutine 1 /usr/local/go/src/os/signal/signal.go:151 +0x1f goroutine 18 [select]: runtime.gopark(0xc00006e7b0?, 0x2?, 0x0?, 0x0?, 0xc00006e79c?) /usr/local/go/src/runtime/proc.go:398 +0xce fp=0xc00006e648 sp=0xc00006e628 pc=0x444d0e runtime.selectgo(0xc00006e7b0, 0xc00006e798, 0x0?, 0x0, 0x0?, 0x1) /usr/local/go/src/runtime/select.go:327 +0x725 fp=0xc00006e768 sp=0xc00006e648 pc=0x454885 os/signal.NotifyContext.func1() /usr/local/go/src/os/signal/signal.go:288 +0x66 fp=0xc00006e7e0 sp=0xc00006e768 pc=0xb7a566 runtime.goexit() /usr/local/go/src/runtime/asm_amd64.s:1650 +0x1 fp=0xc00006e7e8 sp=0xc00006e7e0 pc=0x4753a1 created by os/signal.NotifyContext in goroutine 1 /usr/local/go/src/os/signal/signal.go:287 +0x165 root@Tower:~#

Hi Jorge, Sorry for the delay, But the server is not at my home and i sometimes want to keep it running for x hours to see the effect of changes. No that's not what i mean, It seems that when i have the CA installed together with the Array running (I named it wrong "running parity" i mean running Array). The system crashed when i had a running ARRAY and installed the CA, On the installation screen of the CA it was only white, And the server didn't respond. So then i shutdown the server removed the CA plugin and started the server and everything was good. So i installed the CA with a stopped ARRAY and the where no problems. Then i stared the Array and it when down again. So i removed the user docker templates and started again, Now it's running for 3 day's and i installed today the CA and it keeps running. Could it bee that the user templates could cause this when i already exist in the folder and the are mayby corrupt/misconfiguration? Thanks,

Enjoy your beer in the mean time mate

Yes, This is only with the settings as mention above 1. Recreate it using the USB tool 2. Restored "super.dat and the pools folder for the assignments and disk.cfg" 3. I also did a second memory check with same results. But i can run the parity without any issue's until i install or start the community plugin together with a running parity. So i am wondering if the community plugin is using some "corrupt" file on the disk that could get it to crash. May-by if i can replace/delete that file it would solve the issue? At this moment i deleted the community plugin again en restarted the server and parity, It's now running the parity check. I will let the server run like this. With only the parity started and without the community plugin to see what will happen. I did a new diag with the current setup for you(?), Thanks. tower-diagnostics-20250212-1905.zip

When i tried to make a diagnostics by terminal i get the following root@Tower:~# diagnostics Segmentation fault

Hi, I tested it with Firefox, Edge en Librewolf. In normal mode & private mode. On my other notebook it's the same issue. The strange thing is that it just started when installing the "Community plugin" in combination with a running Array. "Community plugin" with the array offline doesn't give a problem in de browser. But when i click to start array after a few sec. i get the screens like above.

Hi Jorge, I still have the same problems so i decided to do replace the USB key with you steps. 1. Recreate it using the USB tool 2. Restored "super.dat and the pools folder for the assignments and disk.cfg" I booted the system and manually started the array without any problem. But when i install the "Community plugin" the systems start showing blank screens everywhere. Like in the screenshot i am able to ping the server but the webpage is unusable. I am able to use the terminal for example Ifconfig. But clicking on the log button doesn't do anything. Do you have any suggestions for this issue? Thanks

Hi Jorge, I made a back-up of the 3 plugin folders (Plugin, Plugin - error and plugin removed) then i emptied them and did a reboot. Seems that the system is running good now. I reinstalled the com. plugin. I do notice that my dockers are missing some functions. Do you now the solution to this? I found out that when i re-added the files from template-user the option is back. Do i have to put other files back, I emptied all files in (Plugin, Plugin - error and plugin removed) Also i found Batman?.. This file is not pressed in the new installed com.plugin THnaks

Hi Jorge, Removing or Renaming, I renamed them all to .old, Do i also need to do the folders? Can you tell me if like the cpu/gpu plugin change settings somewhere else and where to find them for example the intel-gpu-top/>

Hi JorgeB, Still no boot when starting to normal mode, I do get this error as seen on the picure (sorry again from the phone). When i started back to Safe mode "No plugin". It gets back online and i started the array.

Hi Jorge, When i do a reboot to normal mode it won´t come back online. I when back to safe mode "without plugin" and it came back online. THanks

Hi Jorge, Yes also the Parity Check when good. The dockers are running without a issue. Last check completed on Wed 22 Jan 2025 09:28 AM (today) Duration: 1 day, 10 hours, 6 minutes, 44 seconds. Average speed: 146.6 MB/s Finding 0 errors. Should i do a reboot to normal mode now?

I did discovery that in the safe mode the port changed to :80 instead of :9980 what my setting was, So now i am in the GUI back again, tower-diagnostics-20250120-2054.zip

I added the Cache driver en started the array then firefix local crashed and was unable to do anything in the gui anymore. After a while i shutdown the system by the cli with "shutdown" when i start up now to "start with GUI" the system locks on the login screen and i am unable to login. Keyboard isn´t responding and numlock isn´t reacting, When i ping to the IP i get no reaction. After a boot without ¨ Safe mode - no plugin" the systeem boot with black screen no system info when booting on the screen just black but turned on. After a while i am now able to ping. But no web interface.

Sorry, Thatś because the external webpage isn´t working only the local, So i hookup a display to the system and do it directly. Sorry i do have this one from syslog tower-diagnostics-20250120-1047.zip

Hello, I got into problems after i wanted to open the webpage of unraid and clicked selected the *http://192.168.1.248:9980/webGui/include/Boot.php" link from my browser history without looking to the exact link, My server did than a shutdown and thatś when the problems started. I got the message as seen on the image "Kernel Panic", After a reboot(reset). The Cache drive is dismounted as seen in the image also there is the message "Unclean shutdown Detected". What is now the best way to proceed i am able to add the cache drive. How can i do this without the data-loss on my cache drive? Thanks in advance,

Thank for your reply i checked the systemboard but cant find the setting,,, I added some screenshots of the setting. @SimonF*The systemboard in the video is btw from a other type

Hi, Thanks for your reply. This weekend i did some changes to the server and upgraded it to 7.0.0-rc.2 and to the newest BIOS version. But there is no change, Then i changed the setting as in the image "VGA Detection" to IGNORE. In my opinion should would this setting the bios ignore if there is a DGPU or IGPU and just skip the check. But this didn't change for me the fact that it ain't working. Do you have some other advice? Thanks

Hi Thank you for your time to comment. I posted to the Intel Plugin forum, to see if the can help me. https://forums.unraid.net/topic/92865-support-ich777-amd-vendor-reset-coraltpu-hpsahba/page/85/#findComment-1504406