Crilith

Thanks for the quick response, I'll look into this.

Fix common problems recommended posting a diag here in hopes someone could help me find out what caused this. The only strange behaviour I have had is my ombi docker will occasionally send out an email notification to a user upon a file becoming available, approximately 50x a day until I delete the request in ombi. I have not had time to dig into the cause of that but it sounds like it could be related to this. tower-diagnostics-20231017-1842.zip

Every other driver is showing as normal, but both parity drives are MIA. Their LEDs are lit up on the backplane, so the computer sees them, just not unraid. Edit: I installed a new HBA card during the "reboot" and apparently knocked one of the cords loose. This was an operator error, please close the topic.

I am trying to connect a PiKVM (hat v3.3) to my unraid server on a GA-7PESH2 motherboard and the video capture works at the beginning during bios, but after that stops. I am told that pikvm does not support 1080p60 and likely that is the reason it stops working as it boots into the OS, but I cannot figure out how to change unraid's base resolution. All of the topics I find are related to booting in gui mode. Can someone point me in the right direction?

After you change it to Method 2 and apply, and while the container is running, click the icon on the docker tab and click console. Type vi ../Macinabox/unraid.sh Go to line 250 and press i to edit change 001-86606 to 071-05432 press escape then :wq to save Now reboot the docker.

I updated today and was unable to get it to start or to access the web interface, so I reverted to this version and everything works again.

This fixed it for me, is there a fix planned or is this permanent?

So going off this I just commented out the HostKeys and pointed the authorized keys to the one that gets copied from the /go file and it seems to work. Now I just need to reboot the system and make sure it persists.

Somehow my sshd_config was replaced with a 0 byte file. I used the ssh plugin to replace the config, but now it is complaining that "Permissions 0777 for '/boot/config/ssh/ssh_host_ed25519_key' are too open." it has this error for all of my keys. When I try to chmod the files they stay a 0777. I cannot figure out how to override the chmod through the terminal window.

I do something similar, but to tunnel I setup a dynamic port. Connection -> SSH -> Tunnels -> Source port: 8080 and change Local to Dynamic -> Add. Then I create a shortcut to Chrome with "C:\path\to\chrome.exe" --proxy-server="socks5://127.0.0.1:8080" --proxy-bypass-list="localhost;127.0.0.1" and now everything I do in that browser window acts like it's on my network. I can access https://tower and can just click the docker and hit Webui and it loads like normal.

I tried this many times but never deleted the appdata. That fixed it. Thank you.

I tried that, in that same example, right after I tried just logging in. Also, the first password I set was over 4 characters. I did notice though that when I try and log in I get access denied, but when I use mysqladmin it says connection failed

I cannot get a password to work with this container no matter what I try. I have tried leaving it at the default password and tried setting one. I tried deleting the logs, and tried using the console to set it. # mysql -u root -p Enter password: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) # mysqladmin -u root -p password password Enter password: mysqladmin: connect to server at 'localhost' failed error: 'Access denied for user 'root'@'localhost' (using password: YES)'