graemeh

In case it happens for anyone else: I have 3 instances of MariaDB. When I set up the third one, the /config path used was the same as the default for a second instance, /mnt/user/appdata/mariadb-1. I didn't bother changing this when I set up the second MariaDB. This lead to weird Could not connect to 192.168.0.162:3308 : unexpected end of stream, read 0 bytes from 4 (socket was closed by server) errors in the Booklore log. It is a simple fix. Edit the MariaDB instance, toggle the Advanced view and scroll to find the /config path and give it a unique name. Save, then restart the Booklore instance. profit

Got it, thanks again!

That was it! Thank you soo much! So I can learn, can tell me where you were looking the the Diagnostics bundle that you found the issue?

Oh shoot, I had pulled down someone else's diagnostics file and that is what I originally uploaded. I'm soo sorry!

I only have one Unraid machine but maybe some of my faffing about removed it (I did not remove it myself). Here is an updated Diagnostic morrigan-diagnostics-20250227-1613.zip

I don't see that file.

@MAM59Yes, I'm sure. See below terrible phone screenshot (sorry). Tailscale is for remote access to the machine when I'm away from home, only the plugin, it isn't used within any specific containers. It was working prior to the hardware upgrade. @JorgeB(inexperience) I don't don't see how, VM manager is offline and I don't have any old VMs on the machine. Where would I go to remove that passthrough?

Hiya, I did some hardware upgrades on my unraid server (replacing the CPU and MoBo), I can boot into web GUI mode (with monitor attached) but I don't see Unraid showing up in my router and I'm not getting any IP listed for eth0 when I enter 'ip a' in the unraid terminal. I know that my cable and router are good because the same were in use earlier today without issue. The new MoBo has a 2.5gNIC, RT8125. Here is my diagnostics file, any help would be greatly appreciated! tower-diagnostics-20250124-1521.zip