Elbinho

Ok, the solution seems to be to hardcode the WebUI URL in the container settings, as mentioned here: I'm still not sure what the underlying problem is, but this workaround works for me

Interesting, I just tried Edge and Chrome instead of Firefox. Those browsers give a little more feedback: Instead of simply doing nothing, they open a new tab pointing at about:blank#blocked My Unraid is whitelisted in all extensions I use in Firefox, so maybe it's a firewall issue. I'll try to play around with that a bit

I tried reinstalling two of the affected containers, and the problem persists even if I delete the respective user/appdata folder before reinstalling. What fixes the problem is switching the containers from custom network to bridge, but that isn't an option. Also, the working containers also use custom network without this problem

Tried that, problem persists in safe mode

Sooo, I tried searching the forums, but somehow I didn't find anything about this. About half of the Dockers I use (most of them are binhex releases curiously, but not all of them), don't open the WebUI, when I click the link on the Unraid Dashboard. Every other link in that menu (start, stop, console, ...) works without problems, but WebUI just does nothing. The UIs are running and accessible, it is just the link from the Dashboard that doesn't do anything. All of those links worked in the past, but slowly, one after another somehow died and stayed dead. Does this happen to anyone else? It isn't world-ending, but sometimes it is quite inconvenient

Is there a way to acknowledge a smart warning and have the plugin return to green for that drive? I have a used disk with 2 reported uncorrectable errors, which is why I got it for free. Those errors happened a few thousand runtime hours ago, and since then the drive is operating without a hitch. For the normal Unraid interface, I can just acknowledge the errors, and Unraid will show me a green thumbs up. The only option I found in Disk Location, would be to raise my general limit for UECC, but I don't want to do that for all of my drives, just this one drive

Nice, thanks

Hi, I installed zsh on my machine, and seems to work quite nicely when I ssh into it, but the terminal button in the WebUI seems to default to bash, so when I open a terminal with this button, the first thing I have to do is run zsh. Is there a way to change this button to zsh directly?

I messed up by running the permission reset tool without excluding appdata, so now my mealie won't run (exec /app/run.sh: permission denied) I think I just have to chmod +x the script to fix this, but I don't know where to find it (/app/data is set in the docker variables, but no idea where /app can be found) Edit: so I found run.sh in four different subvolumes in /mnt/user/system/docker/installed/btrfs/subvolumes, but chmodding it was fruitless. Is there a way to fix this without losing my recipe data?

My docker containers won't start anymore, I guess I somehow messed up by running the permission reset tool. docker run for jellyfin (as an example) shows: docker run -d --name='binhex-jellyfin' --net='eth0' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Mimir" -e HOST_CONTAINERNAME="binhex-jellyfin" -e 'TCP_PORT_8096'='8096' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8096]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/binhex/docker-templates/master/binhex/images/jellyfin-icon.png' -v '/mnt/user/Plex/':'/media':'rw' -v '/mnt/user/appdata/binhex-jellyfin':'/config':'rw' 'binhex/arch-jellyfin' e9f1ffb2ec3a305ab4ed5c54985f5bf300187d42415aad833edee7127869d386 docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/usr/bin/dumb-init": permission denied: unknown.

Have started the preclear, seems to run fine. Will post an update tomorrow Edit: Zeroing is taking longer than I anticipated, but everything looks fine. Gonna mark this as solved for now

I swapped cables with my pool drive (what was sdb before), and it seems better. Pool hasn't acted up yet, but then I haven't started the array yet, just done some SMART checks mimir-diagnostics-20240312-1703.zip

Hi, my parity drive dropped offline repeatedly a few weeks ago. As the whole config is kinda new, I was unsure whether it was really a drive problem (could be, the drives are old) or some trouble with connections. I decided to replace the drive and figured I could maybe look at the replaced drive some more when I have some spare time. My replacement just arrived and I tried to assign it as my new parity, and it dropped offline immediately. Tried a preclear, which also failed. Logs are attached. Is the new drive just broken, or do I have some other issue with the system? preclear_disk_WP019LE1_9499.txt mimir-diagnostics-20240312-1613.zip

Ähm....das habe ich ja in meinem ersten Post beschrieben. Wenn ich die IP manuell eingebe, bekomme ich wie gesagt die Fehlermeldung "Die IP-Adresse wird bereits von einem anderen Gerät verwendet!" (manchmal ist es vielleicht doch nicht so einfach?) Edit: Weil die Frage sich mir auch aufdrängt: Nein, die IP wird von keinem anderen Gerät verwendet, nur von dem swag Container, für den ich die Portweiterleitung einrichten will

Würde ich gerne machen, aber das Gerät taucht leider nicht in den Verbindungen auf. Swag läuft, pingen kann ich die Adresse auch, aber weder im für die Portfreigabe relevanten Pulldown-Menü, noch in der Liste aller bekannten LAN-Geräte ist swag mit der entsprechenden IP zu sehen

Hi, ich verzweifle hier gerade ein wenig. Prinzipiell sollte ne Portfreigabe ja eigentlich eine unkomplizierte Sache sein, aber meine Fritzbox 6591 weigert sich beharrlich (oder ich bin zu blöd :)) Ich möchte gerne 80 und 443 von außen an swag auf meinem Unraid weiterleiten. Der swag-Container hat die interne IP 10.x.y.10, die physische IP des Unraids ist 10.x.y.1. Ich kann allerdings in der Fritzbox keinen Port an diese "virtuelle" Container-IP weiterleiten, die Fehlermeldung ist "Die IP-Adresse wird bereits von einem anderen Gerät verwendet!". Edit: Ich habe im Changelog gelesen, dass es wohl Probleme mit Fritzbox-Portfreigaben mit ipvlan geben kann, und habe daher auf macvlan umgestellt, aber ohne Erfolg