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:

1. Clean Reinstall: Ran rm -rf /boot/config/plugins/dynamix.my.servers and /usr/local/unraid-api, then reinstalled via the Apps tab.

2. 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).

3. NGINX & Reboots: Reloaded nginx (rc.nginx reload) and did a full clean server reboot.

4. Plugin Conflicts: Uninstalled unraid-management-agent just in case it was hogging the API socket.

5. 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

This has been happening to multiple users with the last 2 or 3 Connect releases, including myself, just in one server. You can uninstall Connect for now; it should then start again, and try once more when a new Connect release is out.