I tried to post a reply, but it didn't like my email so it probably won't appear. Just as well, it wasn't complimentary.

I rebooted after installing connect since there was no backup button or login button.

The reboot did the trick, it now shows the backup as active and up-to-date. But what does that mean?

I must say, for all that unraid wants you to use connect I have no idea why. Besides this backup (that appdata backup did better) what function does connect serve?

I searched the forum for the phrase "unraid connect" and this thread was the only result on page 1. There were admittedly 257 results, so I'll go look at some more threads. But I don't feel like it is my job to search for stuff like this, it is unraid's job to provide guidance. And I mean when and where I need it, not buried in the manual. Just having an explanation of what screens and options do is mandatory in my worldview. For instance on the ManagementAccess setting there are 3 API tabs. What the heck is an API and why should I care? It never gives the slightest clue. (/rant)

There is help in the Unraid webUI. Many settings have help which you can toggle on/off by clicking on the label for the setting. You can also toggle on/off help for the whole webUI by clicking the help (?) button in the main bar.

Thanks

1 hour ago, trurl said:

There is help in the Unraid webUI. Many settings have help which you can toggle on/off by clicking on the label for the setting. You can also toggle on/off help for the whole webUI by clicking the help (?) button in the main bar.

Thanks trurl. That looks like it will be useful to me.

Sorry to be a pest, but how do I connect your name in my reply to you so you are notified you were mentioned in my post? (or is that even how it works?)

Type @

followed immediately by the first few letters of the username

then when the popup appears, you must select the username

Like this

@NewDay

Also, when you "react" to a post (Like, Thanks, etc.) it also notifies the user.

@trurl Thank you. So easy when you know.

After upgrading from 7.2.3 to 7.2.4 the API wont start. Logs show Failed to start NestJS server

[20:58:38 INFO GraphQLModule]: Mapped {/graphql, POST} route {"apiVersion":"4.31.1+726ae51e","logger":"api","context":"GraphQLModule"}

[20:58:41 ERROR app]: Failed to start NestJS server {"apiVersion":"4.31.1+726ae51e"}

err: {

"type": "Error",

"message": "bootstrapNestServer timed out after 29703ms",

"stack":

Error: bootstrapNestServer timed out after 29703ms

at Timeout._onTimeout (file:///usr/local/unraid-api/dist/assets/index-BMII9FSH.js:37:56)

at listOnTimeout (node:internal/timers:588:17)

at process.processTimers (node:internal/timers:523:7)

}

[20:58:41 ERROR app]: API-ERROR {"apiVersion":"4.31.1+726ae51e"}

err: {

"type": "Error",

"message": "bootstrapNestServer timed out after 29703ms",

"stack":

Error: bootstrapNestServer timed out after 29703ms

at Timeout._onTimeout (file:///usr/local/unraid-api/dist/assets/index-BMII9FSH.js:37:56)

at listOnTimeout (node:internal/timers:588:17)

at process.processTimers (node:internal/timers:523:7)

}

ur1-diagnostics-20260328-2054.zip

On 3/27/2026 at 1:44 PM, JorgeB said:

If the plugin is uninstalled, but the orange icon doesn't show, open a terminal window and copy/paste

unraid-api plugins install unraid-api-plugin-connect

Once that's done, refresh the GUI and you should now see the orange icon.

It shows but I can't sign in, it's grayed out.

On 3/28/2026 at 11:00 PM, tjsyl said:

After upgrading from 7.2.3 to 7.2.4 the API wont start. Logs show Failed to start NestJS server

[20:58:38 INFO GraphQLModule]: Mapped {/graphql, POST} route {"apiVersion":"4.31.1+726ae51e","logger":"api","context":"GraphQLModule"}

[20:58:41 ERROR app]: Failed to start NestJS server {"apiVersion":"4.31.1+726ae51e"}

err: {

"type": "Error",

"message": "bootstrapNestServer timed out after 29703ms",

"stack":

Error: bootstrapNestServer timed out after 29703ms

at Timeout._onTimeout (file:///usr/local/unraid-api/dist/assets/index-BMII9FSH.js:37:56)

at listOnTimeout (node:internal/timers:588:17)

at process.processTimers (node:internal/timers:523:7)

}

[20:58:41 ERROR app]: API-ERROR {"apiVersion":"4.31.1+726ae51e"}

err: {

"type": "Error",

"message": "bootstrapNestServer timed out after 29703ms",

"stack":

Error: bootstrapNestServer timed out after 29703ms

at Timeout._onTimeout (file:///usr/local/unraid-api/dist/assets/index-BMII9FSH.js:37:56)

at listOnTimeout (node:internal/timers:588:17)

at process.processTimers (node:internal/timers:523:7)

}

ur1-diagnostics-20260328-2054.zip

Exact same problem......reboots don't fix it.

Just like so many here I'm getting the same thing with the unraid connect saying the API is offline. I have tried rebooting, I have tried to restart the API, I have uninstalled and reinstalled Unraid connect and nothing has resolved it yet. Is there any kind of fix for this yet or is there anything else that I can try that can fix this?

olympus-diagnostics-20260414-2019.zip

Why does your syslog start in Nov 19 if you just rebooted?

6 hours ago, saiyantwan said:

I have uninstalled and reinstalled Unraid connect and nothing has resolved it yet

If it's not working with Connect, the best "solution" for now is to leave Connect uninstalled and updated when a new one is out, which should be very soon.

There was a new Connect released yesterday, it may help with this issue. Please retest.

1 hour ago, JorgeB said:

There was a new Connect released yesterday, it may help with this issue. Please retest.

ok thanks working now