diogomadeira

Hi everyone, I'm completely stuck with the Unraid Connect plugin. It constantly shows "Warning: API is offline!" in the web UI, and the Sign In button is grayed out. The local PM2 process says the API is online, but it keeps failing to initialize properly within the NestJS timeout window. System Info: Unraid Version: 7.2.4 Connect API Version: 4.32.1 Hardware Context: I recently migrated to a brand new USB Drive (SanDisk 32GB) because my old Kingston drive was causing file corruption. I copied my /config folder over and successfully transferred the Unraid license to the new USB GUID. The Symptoms: The plugin installs successfully via CA Apps. The Unraid UI shows the "CONNECT (BETA)" menu, but says Offline. netstat shows no port 3000 (which is expected for newer versions using the .sock file). Running /etc/rc.d/rc.unraid-api restart shows the PM2 process launching successfully (status: online). However, looking at /var/log/graphql-api.log, the API constantly hits a 25-second timeout (bootstrapNestServer timed out after 25011ms) right after checking the registration key, and never manages to handshake with the Mothership ("status":"PRE_INIT"). Troubleshooting Steps Already Taken: Clean Reinstall: Ran rm -rf /boot/config/plugins/dynamix.my.servers and /usr/local/unraid-api, then reinstalled via the Apps tab. Disk Spin-up: Noticed the timeout might be related to disks waking up. Forced a "Spin Up" on the array before restarting the API. (This worked once and showed Temperature provider available, but the UI remained offline). NGINX & Reboots: Reloaded nginx (rc.nginx reload) and did a full clean server reboot. Plugin Conflicts: Uninstalled unraid-management-agent just in case it was hogging the API socket. Fresh Tokens (Mothership): Suspecting old tokens from the previous USB drive were causing issues, I ran rm -f /boot/config/plugins/dynamix.my.servers/myservers.cfg and rm -rf /boot/config/plugins/dynamix.my.servers/keys and restarted the API to force a clean generation. Despite all this, the log remains identical. It tries to start, times out at 25s, and fails. Here is the relevant output from tail -n 50 /var/log/graphql-api.log: JSON [11:30:02 INFO app]: Registration key loaded {"apiVersion":"4.32.1+5c297da1"} [11:30:02 INFO app]: Dynamix config loaded {"apiVersion":"4.32.1+5c297da1"} [11:30:03 INFO app]: State manager initialized {"apiVersion":"4.32.1+5c297da1"} [11:30:03 INFO app]: Registration key watch active {"apiVersion":"4.32.1+5c297da1"} [11:30:03 INFO app]: Bootstrapping NestJS server (budget: 25011ms)... {"apiVersion":"4.32.1+5c297da1"} [11:30:16 INFO api]: Starting Nest Server on Port / Path: /var/run/unraid-api.sock {"apiVersion":"4.32.1+5c297da1","logger":"api"} [11:30:17 WARN RCloneService]: RClone API service is not initialized, skipping provider info loading {"apiVersion":"4.32.1+5c297da1","logger":"api","context":"RCloneService"} [11:30:27 INFO TemperatureService]: Temperature provider available: disk-sensors {"apiVersion":"4.32.1+5c297da1","logger":"api","context":"TemperatureService"} [11:30:27 INFO ConnectPluginModule]: Connect plugin initialized with {"mothership":{"status":"PRE_INIT"},"dynamicRemoteAccess":{"runningType":"DISABLED","error":null,"lastPing":null,"allowedUrl":null},"config":{"wanaccess":false,"wanport":0,"upnpEnabled":false,"apikey":"***REDACTED***","localApiKey":"***REDACTED***","username":"","avatar":"","regWizTime":"","dynamicRemoteAccessType":"DISABLED"}} {"apiVersion":"4.32.1+5c297da1","logger":"api","context":"ConnectPluginModule"} [11:30:32 ERROR app]: Failed to start NestJS server {"apiVersion":"4.32.1+5c297da1"} err: { "type": "Error", "message": "bootstrapNestServer timed out after 25011ms", "stack": Error: bootstrapNestServer timed out after 25011ms at Timeout._onTimeout (file:///usr/local/unraid-api/dist/assets/index-BBAyDURr.js:37:56) at listOnTimeout (node:internal/timers:588:17) at process.processTimers (node:internal/timers:523:7) } Is there any way to manually increase this 25s budget, or is there something else blocking the Mothership connection after a USB migration? Any help is greatly appreciated! Diagnostics attached. unraid-diagnostics-20260408-1140.zip

Existing pools. But I tried to delete all docker folder and the problem continue.

Same problem. unraid-diagnostics-20260109-1447.zip

Hello, I’m facing a persistent Docker issue on Unraid that I haven’t been able to resolve, even after extensive troubleshooting. I’d appreciate any insights or similar experiences. Issue descriptionAfter a cold boot / power-on: The first start of the array always causes Docker to fail Error shown: Docker Service failed to start failed to start containerd: timeout waiting for containerd to start If I then stop the array and start it again, Docker starts normally Any subsequent Docker restart works fine The problem only occurs on the first array start after power-on Important detail: This happens even with array auto-start disabled Boot Unraid → manually click Start Array On that first start, Docker fails Stop Array → Start Array → Docker works every time What I’ve already testedTo rule out configuration and software issues, I’ve tested: Fresh Unraid installation on a new USB flash drive No plugins, no custom scripts Docker using: docker.img Docker directory mode Docker data located on: NVMe SATA SSD No containers set to autostart No containers at all Various delays (sleep, rootdelay) Manual Docker restart User Scripts to automatically restart Docker Docker and containers work perfectly after the first array restart None of the above changed the behavior. ObservationsBased on all tests: This does not seem related to: Docker configuration Containers docker.img corruption Filesystem choice Plugins or scripts It appears that the first array start after power-on leaves the system in a bad state A single array stop/start reliably fixes the issue After that, the system is completely stable Additional contextThis setup used to work normally The issue appeared “out of nowhere” No hardware changes were made Once the array has been restarted once, everything works as expected QuestionHas anyone encountered a situation where: Docker fails only on the first array start after power-on containerd times out and a simple array stop/start fixes it every time? Could this be related to: storage controller initialization timing? NVMe / SATA firmware behavior? kernel block device readiness? something that only fully initializes after the first array stop/start? Any ideas on logs to check or known issues would be very helpful. Thanks in advance. unraid-diagnostics-20260109-1010.zip

What can I do to solve this problem?

I got this... cannot import 'disk2': I/O error Destroy and re-create the pool from a backup source.

I had a problem with the RAM, but already solve it... I was a BIOS config bug... Reset the BIOS and solve the problem.

Here is the diagnostic. servidor-unraid-diagnostics-20260102-1525.zip

Here is the print of the main tab with the error. 5523ab4a-cc63-45d4-beb1-2b537f9579d1.jfif

I had many consecutives energy shutdown and I had some problem with my unraid.... The pen drive get corrupted and I manage to get an old backup (the one in the unraid cloud didn't work), but The configuration of the array was a little diferent.... When I get the system up again one of the disk is Unmountable: wrong or no file system... But, i think because I use a backup with different config, the system start to do a a parity check.... I cancel it. I tried to mount the drive with unassigned Devices, but it fail.... What can I do to save the data of this disk? The SMART report is attached, if it helps to find out the problem. servidor-unraid-smart-20260102-1000.zip

I have the same problem here, but only when I access thru Nginx (reverse proxy). If I access inside the home network it works.