viper1190
Members
-
Joined
-
Hi, Just curious, has anyone been able to get this container to work with an AMD GPU? I have tried the ollama containers and got them to work but cannot get any of the SD containers to work.
-
Tried without any username/password. Still the same. You might be right, some network issue which I can't quite figure out. Will post here if I ever figure it out.
-
Thanks for this container. I was trying to get this working however, I have a strange situation. I have wg0 configured properly, and then proxy-server container configured to use wg0 (http and socks are both enabled on proxy server). Container itself seems to work fine, I can curl to get my external IP and it seems correct. However, on my laptop, I have configured my browser to use this proxy using my internal unraid IP with credentials (screenshot below). But the browser simply refuses to connect with this configuration. There are no errors or warnings in the proxy-server container. I can connect to other services on my unraid server without any issues (so it seems to be an issue specific to this container). Also, I enabled tailscale for proxy-server, and I am able to use the container as an exit node on other devices and it seems flawlessly. Am I missing anything with HTTP/SOCKS proxy configuration?
-
Thanks for this plugin, its great. I have an issue whenever the server restarts due to power failures. It seems like data is not persisted. "Persist Database on Reboot" is set to "Yes" (and greyed out, I cannot change it). Tool tip says in case of power failures it will restore the database from the flash drive. But in my case it just resets to 0. Any ideas to fix this would be very helpful!
-
Thank you, I went through this issue today after a simple restart - no hardware changes. CMOS clear fixed the issue. Probably something to do with onboard NICs, not sure if this happens with ad on cards.
-
Since updating to 7.1.3 I have been having some strange issues with my Unraid server. I observed the issue after my dashboard application Homarr started showing red status for containers hosted on NUC PC. Homarr uses pings behind the scenes to show status. Here's my network setup: I have a AI Mesh setup. a primary (master) router and 2 mesh nodes (1 connected via cable, 1 over WiFi 5). My Unraid server is connected to the WiFi node along with 2 other devices (1 NUC PC which runs my PiHole Ad Blocker and a Laptop which I use to connect to my servers (via SSH or Web UI). All of these devices are connected to the WiFi mesh node using a LAN cable. At first I thought this could be an AI Mesh issue, But here are some observations: I can ping Unraid server from my laptop and NUC PC (I can even access Unraid Web GUI, no issues) I CANNOT ping my laptop or my NUC PC from unraid console. It just hangs without any command output. Below screenshot is the ping result while pinging my laptop. However, I CAN ping other devices that are connected to other mesh nodes (for ex. my Home Assistant device and also the primary router). Any help would be very much appreciated. PS: I have updated unraid to 7.1.4 to see if the issue goes away. But it hasn’t.
-
I have the same issue with a different container (pihole-unbound). Haven't received any response on developer's GitHub. Could you please elaborate on what certificates are needed on the container and how we can manually install them? Thanks!
-
Hi, is the tailscale integration with unraid 7.x supposed to work out of the box? Currently I get the below error. ERROR: Can't get Tailscale JSON Apparently this is due to missing ca certificates in the container. Anyone else have this issue?
-
alright, thanks for clarifying.
-
What about any of the modules installed (for example AZ). Are they also retained post reboot?
-
For someone coming across this, I fixed it by adding "--restart=always" against extra parameters as shown in below. Be sure to turn the "Advances Mode" ON while editing the docker template otherwise this field will not show up.
-
I realize this is an old thread but I just wanted to add a few things from my experience today which someone might find useful. Thanks @Salzgablah for the detailed post above. 1. It's very important to follow the first step i.e. writing the keyfile using echo command. Any other means simply didn't work for me. If I did it via nano, unraid would refuse to unlock the array saying its an invalid keyfile. 2. Copying from remote share somehow always ended up with a keyfile that was having executable attribute (* next to it). I had to add "chmod -x /root/keyfile" in the script that goes into the go file after the file was copied.
-
Thanks a lot, that did the trick.
-
First of, I am pretty new to unraid ecosystem so pardon me if I am doing anything naive. I am trying to add a new cache pool of 2x2TB SSDs. I want to set them up as BTRFS Encrypted Raid1. However, I do not see any option to change their format. I tried setting default format (in Settings => Disk Settings => Default File System to BTRFS Encrypted) to no avail. If I stop the array and click on the any of the pool drives, the filesystem option is disabled (as shown in the screen capture below). Where else can I do it? Or is this simply not possible? There is no data on the drives so format/reformat is not a problem. I tried looking around in forums but couldn't find much. PS: Unraid version I am using is 6.12.8
