DaFr0n

Where do I identify the culprit in the diagnostic files please? It also looks like my CCTV_Pool HDD is dying, would you agree as it keeps going read only and the allocated share is a 'invalid path'

Docker within the UnRaid WebUI. Again, this is for various dockers all created within the WebUI. This is using the below App. https://github.com/willfarrell/docker-autoheal/issues

Could someone please help with how I'm meant to set a docker container up to use Autoheal? Autoheal is set as AUTOHEAL_CONTAINER_LABEL=heal My dockers containers I want to watch have: AUTOHEAL_CONTAINER_LABEL=heal I'm not sure if this is correct as the Github states AUTOHEAL_CONTAINER_LABEL: autoheal-app Logs for auto heal show: AUTOHEAL_CONTAINER_LABEL=heal AUTOHEAL_START_PERIOD=0 AUTOHEAL_INTERVAL=5 AUTOHEAL_DEFAULT_STOP_TIMEOUT=10 AUTOHEAL_ONLY_MONITOR_RUNNING=false

Problem solved... I'm not sure how this happened but my Pelican-Wings changed to pulling ghcr.io/mainfrezzer/pelican-panel:latest I have changed this back to wings:latest & all is well. Thanks for the help

Just tried the above, same issue mate

Yes updated wings and panel, still the same issue.

laravel-2025-04-06.log Logs attached

Has anyone else's updated and after no longer able to connect to their node. I have changed the Pelican owner to 'nobody' as suggested above but no node connection. Assume something in a update has changed as it worked great previously with multiple servers "Failed to load resource: the server responded with a status of 404 (Not Found)"

Hi all, I have tried multiple solutions without success. My aim is to have the below~: Bedrockconnect (running in docker, needs port 19132) I have installed this and I can see user IDs etc. so I know its working Run a Geyser Bedrock server within Pelican Docker (Pterodactyl) Again I can get this working fine, but it needs port 19132, which doesn't respect changes in the server.properties for port changes. Therefore, how would I go about getting these 2 instances to run allowing both to access port 19132 & be connectable. As you would expect at the moment, if I start one, I get a port reservation error on the other. I was thinking macvlan or ipvlan, but I will be honest that side of things is new to me 😁

They are on the same SATA power cable, also the same cable splitter on the LSI HBA. But then again so are a few other disks, I have just moved some cables around, waiting for it to reboot

Looks like there is also a possible issue with disk 2 according to the notifications

Hi all, looks like the parity issue is back. Is it time to replace the drive? Unraid just threw a bunch of errors, need to go through them now unraid-diagnostics-20241205-1739.zip

Thanks, I will have another look, as its done this on multiple occasions, however always resyncs

Hi all, would someone help me read my diag file to understand if my parity disk is faulty. I have tried, removing, restarting array, stopping, readding disk, to force a parity sync. However it keeps disabling so I guess there is a error somewhere. Thanks in advance unraid-diagnostics-20240927-1852.zip

Does anyone know if this method still works, I'm struggling to get it up and running.