Zhono

Trying to setup SparkyFitness. I have the frontend setup, which starts fine, and I can load up the login screen(it does show an error popup in the bottom right, since there is no backend to connect to). I was already running Postgres 15, so I manually created a database and user, and setup all of the permissions and extensions and whatnot as per the SparkyFitness docs. But the backend will not start. I just get: Failed to start server: Error: getaddrinfo ENOTFOUND http://192.168.0.215 at /app/SparkyFitnessServer/node_modules/.pnpm/[email protected][email protected]/node_modules/pg-pool/index.js:45:11 at process.processTicksAndRejections (node:internal/process/task_queues:104:5) at async getSystemClient (/app/SparkyFitnessServer/db/poolManager.ts:76:18) at async applyMigrations (/app/SparkyFitnessServer/utils/dbMigrations.ts:12:18) { errno: -3008, code: 'ENOTFOUND', syscall: 'getaddrinfo', hostname: 'http://192.168.0.215' } edit* Nevermind, I solved it myself. Couldn't get this working no matter what I tried. Ended up installing Portainer from the Community Apps, using Portainer to setup the SparkyFitness stack per their instructions, which worked perfectly right away, and then used all of the environment variables and other settings from that to manually recreate those container templates in Unraid's Docker system so they can be managed like everything else, without having to keep Portainer (though I might keep it available anyway, since it's useful).

One more update to this, just in case anyone finds this post because they have the same/similar issue. I had decided that even if my Thunderbolt enclosure wouldn't work anymore on Unraid, maybe I could still make use of the enclosure and drives if I were to pass the Thunderbolt controller through to a VM running an OS that CAN make use of it. So of course I went to Tools/System Devices, found the USB4/Thunderbolt controller on the list, checked the box, and hit the "Bind selected to VFIO at boot" button, and rebooted. Wouldn't you know it, when I rebooted and logged back in, all of the drives in that enclosure were suddenly appearing under Unassigned Devices, and I was able to stop the array and add those drives in and start the array back up. And just like that, my array just regrew by 32TB that I thought was just going to sit around doing nothing after updating to Unraid 7. I feel stupid for not thinking to try such a simple step 4 months ago, but I guess better late than never.

Trying to setup Comic-Library-Utils and the container won't start. All I get in the logs is: edit: Nevermind. Had to manually create an Appdata folder for the container and map it to /config when setting it up. It starts fine now

As the title says. My system is built with an AMD mini PC with several USB 4(so Thunderbolt/40 Gbps compatible) ports, two nvme drives, and multiple hard drive enclosures loaded with an assortment of had drives. Originally, I had been using two Terramaster enclosures for the last 5 years or so. Rock solid, but only 5Gbps usb connection, so it's slower the dirt. Finally decided it's time for an upgrade to both storage and speed, so I hit up black friday sales and managed to get an Orico 5-bay Thunderbolt enclosure, a MediaSonic 8-bay 10Gbps enclosure, and a handful of WD 8TB drives. Moved my drives over from the Terramaster enclosures to the MediaSonic, put the new 8TB drives into the Orico, paid the $69 to upgrade my key from Plus to Pro(now that I am over 12 drives), and I was back up and running in less than 30 minutes, faster than ever, and with double the storage. Unfortunately, I've been watching SpaceInvader's tutorial videos on setting up Tailscale and other newer features, which made me decide that as long as I am doing upgrades, I may as well try getting on Unraid 7. Ran the upgrade, rebooted, and immediately the Thunderbolt enclosure and drives were no longer detected. Though I knew it wasn't the problem, I spent a bunch of time mucking around with power cycling the enclosure and server, swapping cables, etc. Nothing. Hit the button to downgrade back to 6.12.14, the enclosure and drives immediately work again. The non-Thunderbolt enclosure worked the whole time with no issue. So I'm wondering, anyone else have this issue? Is this a known thing, maybe? Is there a fix? Anything I can do at all to get on Unraid 7 with my hardware setup? Or can I expect that if it doesn't work anymore in RC1, that it's probably going to continue to not work in the official Unraid 7 release? Any time I search for "thunderbolt" in these forums, it's just posts about people wanting to use Thunderbolt networking, and no real useful information in fixing anything, regardless. Back on 6.12.14 for now, but I'd rather not be trapped on Unraid 6 and locked out of new features, and I also have no intention of downgrading the hardware back to the much slower stuff. So I'm not really sure what to do here. *edit* Decided to search again, and I found some threads I didn't find last time, somehow. People discussing exactly this. Wis I could delete this post now, as it is pointless. Also, seems like the answer is basically "no, there is no solution"

Any chance this will be getting updated to the latest version of Nextcloud? There are a lot of new features getting missed out on, if you use this version. Like the AI stuff.

Just finally got around to setting this up. Was already running containers for MariaDB, phpmyadmin, and Letsencrypt(I switched from Traefik 2 to Letsencrypt using Spaceivader's guide when I moved to unraid). For you other Letsencrypt people, here's the process. It was as simple as opening phpmyadmin and creating a new user "wordpress" and selecting to also automatically create a database with all privileges. Install the wordpress container, giving the database info I just created in phpmyadmin. For databse server info, I give it MariaDB's internal ip and port, and place the wordpress container on the Custom:proxynet, same as all of my containers. I also copy whatever internal IP MariaDB was assigned when I set it up, and tell MariaDB to use that as a fixed IP, so it doesn't change on me and break things. Then in the Letsencrypt/nginx "proxy-confs" folder, make the file wordpress.subdomain.conf, and fill it with: server { listen 443 ssl; listen [::]:443 ssl; server_name mydomain.com; #change this to your domain or subdomain include /config/nginx/ssl.conf; client_max_body_size 0; location / { include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; set $upstream_app wordpress; set $upstream_port 80; set $upstream_proto http; proxy_pass $upstream_proto://$upstream_app:$upstream_port; proxy_max_temp_file_size 2048m; } } Then open the site and do the standard wordpress setup. You'll notice I use my primary domain without a subdomain and it works perfectly fine. Just make sure the Letsencrypt container is not set to "subdomains only = true". Also, it is VITAL that you clear your browser's cache, or wordpress may keep redirecting your front page, to a page not found. At least it did for me(kept sending my to mydomain.com/ui/dashboard). And that's it, everything should work fine. Of course, I have not yet started messing with any of the more complex themes/plugins/addons I want to use. Hopefully they all work without issue.