ur1-diagnostics-20260328-2054.zip

I noticed the timestamps in the graphql-api.log were adrift from the system time, before I lose more time tshooting my OIDC stuff I'm bothered about the time drift.

NTP is configured and working, hardware and software clocks are in sync. syslog timestamps all as expected.

root@blackrack:/# echo "System Time: $(date)"; echo "Hardware Time: $(hwclock --show)"

System Time: Fri Mar 13 20:58:10 GMT 2026

Hardware Time: 2026-03-13 20:58:10.218973+00:00

root@blackrack:/# logger "Test timestamp"

root@blackrack:/# tail -n1 /var/log/syslog

Mar 13 20:58:14 blackrack root: Test timestamp

Yet for the API...

root@blackrack:/# unraid-api stop

[PM2] [unraid-api](0) ✓

root@blackrack:/# rm /var/log/graphql-api.log

root@blackrack:/# echo "System Time: $(date)"; echo "Hardware Time: $(hwclock --show)"

System Time: Fri Mar 13 20:59:01 GMT 2026

Hardware Time: 2026-03-13 20:59:01.975691+00:00

root@blackrack:/# unraid-api start

Starting the Unraid API

[PM2][WARN] Applications unraid-api not running, starting...

[PM2][WARN] App unraid-api has option 'wait_ready' set, waiting for app to be ready...

[PM2] App [unraid-api] launched (1 instances)

+--- unraid-api

namespace : default

version : 4.29.2+c39b0b26

pid : 608133

pm2 id : 0

status : online

mode : fork

restarted : 0

uptime : 1s

memory usage : 224.9mb

error log : /var/log/graphql-api.log

watching : no

PID file : /var/log/.pm2/pids/unraid-api-0.pid

root@blackrack:/# tail -n5 /var/log/graphql-api.log

[20:03:07 INFO NestApplication]: Nest application successfully started {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"NestApplication"}

[20:03:07 INFO api]: Server listening on /var/run/unraid-api.sock {"apiVersion":"4.29.2+c39b0b26","logger":"api"}

[20:03:07 INFO api]: Nest Server is now listening {"apiVersion":"4.29.2+c39b0b26","logger":"api"}

[20:03:07 INFO app]: Startup complete in 582ms {"apiVersion":"4.29.2+c39b0b26"}

[20:03:08 INFO MothershipGraphqlClientService]: Connected to wss://mothership.unraid.net/ws {"apiVersion":"4.29.2+c39b0b26","logger":"api","context":"MothershipGraphqlClientService"}

Any help appreicated.

API version: 4.28.2

Hello dear Unraiders, I have simple setup of an array with one data disk and one parity drive.

I wanted to obtain HDD temperature of both parity and the data disk.

This query however:

curl -X POST http://192.168.1.10/graphql -H "Content-Type: application/json" -H "X-API-Key: d61........x" -d '{"query": "query {
    array {
        disks {
            name
            size
            status
            temp
        }
    }
}
"}'

Returns only disk1 temperature

{"data":{"array":{"disks":[{"name":"disk1","size":17578328012,"status":"DISK_OK","temp":31}]}}}

As I wanted to regulate an external FAN speed based on this not having all drives temperatures is an issue....

(Of course in case the HDD is sleeping, unraid should not spin-up the drive)

Thanks for any suggestions

when is the connect plugin going to fix the api and graph stuff...

Running on supported version 7.2.2
plugin: skipping: unraid_connect_cleanup_for_unsupported_os_versions.sh - Unraid version too high, requires at most version 6.12.0
Backing up original files...
Backup complete.
Patching header logo if necessary...
Current API version on server: 4.28.0
Connect wants to install API version: 4.28.2
Connect has a newer API version - proceeding with upgrade
Installing package...
Removing old package file: /boot/config/plugins/dynamix.my.servers/dynamix.unraid.net-4.28.0-x86_64-213.txz
Stopping Unraid API service before upgrade...
Stopping Unraid API service...
[PM2] [unraid-api](0) ✓
Cleaning up existing node_modules directory...
Removing: /usr/local/unraid-api/node_modules
Cleaning up existing unraid-components directory...
Clearing contents of: /usr/local/emhttp/plugins/dynamix.my.servers/unraid-components

+=============================================================================================================================================+
| Upgrading dynamix.unraid.net-4.28.0-x86_64-213 package using /boot/config/plugins/dynamix.my.servers/dynamix.unraid.net-4.28.2-x86_64-1.txz |
+=============================================================================================================================================+

Pre-installing package dynamix.unraid.net-4.28.2-x86_64-1...
Removing package: dynamix.unraid.net-4.28.0-x86_64-213-upgraded-2025-12-18,13:01:04
Installing package dynamix.unraid.net-4.28.2-x86_64-1.txz:
PACKAGE DESCRIPTION:
# dynamix.unraid.net (Unraid API)
#
# Provides the Unraid API and Connect services for Unraid OS.
# This package enables remote management, monitoring, and access
# to Unraid servers through the Unraid Connect platform.
#
# Features include system monitoring, notifications, remote access,
# and integration with the Unraid Connect dashboard.
#
# Homepage: https://unraid.net/
Executing install script for dynamix.unraid.net-4.28.2-x86_64-1.txz.
Package dynamix.unraid.net-4.28.2-x86_64-1.txz installed.
Package dynamix.unraid.net-4.28.0-x86_64-213 upgraded with new package /boot/config/plugins/dynamix.my.servers/dynamix.unraid.net-4.28.2-x86_64-1.txz.
Starting Unraid Connect installation...
Setting up Unraid API...
Running setup_api.sh
Starting API setup script
Environment: CONFIG_DIR=/boot/config/plugins/dynamix.my.servers, API_BASE_DIR=/usr/local/unraid-api
UNRAID_BINARY_PATH=/usr/local/bin/unraid-api
Env file already exists
API setup completed at Thu Dec 18 13:01:17 CST 2025
Running post-installation verification...
Running verify_install.sh
Performing comprehensive installation verification...
Checking executable files...
✓ Executable file /usr/local/bin/unraid-api exists and is executable
✓ Executable file /etc/rc.d/rc.unraid-api exists and is executable
✓ Executable file /usr/local/emhttp/plugins/dynamix.my.servers/scripts/gitflash_log exists and is executable
Checking directories...
✓ Directory /usr/local/unraid-api exists
✓ Directory /var/log/unraid-api exists
✓ Directory /usr/local/emhttp/plugins/dynamix.my.servers exists
✓ Directory /usr/local/emhttp/plugins/dynamix.unraid.net exists
✓ Directory /etc/rc.d/rc6.d exists
✓ Directory /etc/rc.d/rc0.d exists
Checking symlinks...
✓ Symlink /usr/local/bin/unraid-api exists -> ../unraid-api/dist/cli.js
✓ Symlink /usr/local/sbin/unraid-api exists -> ../bin/unraid-api
✓ Symlink /usr/bin/unraid-api exists -> ../local/bin/unraid-api
Checking configuration files...
✓ Environment file /boot/config/plugins/dynamix.my.servers/env exists
Checking shutdown configuration...
Checking for shutdown scripts in rc6.d...
✓ Shutdown script for flash-backup exists and is executable
✓ Shutdown script for unraid-api exists and is executable
✓ rc0.d symlink exists
✓ unraid-api is in PATH

Tower_NUTsettings.mhtml Tower_Syslog.html

Will it allow all commands to enable a new webgui frontend or is it just for managing/monitoring?

Ta

I recently purchased a LincStation N2 and would like to set it up for remote access—either from outside my local network or over a different internet connection. Could someone please guide me through the necessary configuration steps for Windows?

Any help would be greatly appreciated!

Best regards

When making it in the GUI the API key itself is blank. When I click copy it does nothing. When I try to copy whatever text is there it just copies the password dots that contain no key.

In case I missed it in the docs; is there a way to put the server into sleep, reboot or shutdown via the API?

For people who don't have parity disk and don't do them, the API would automatically show the read-check info in its place which I do on schedule.

That is how it should be. If Parity Check is not available because there is no parity disk, check for Read-Check data and send that.

I would like to know when this will be fixed.

Thanks

--header 'content-type: application/json' \

--header 'x-api-key: XXXX' \

--url 'http://192.168.0.30/graphql' \

--data '{"query":"query Info {\n info {\n time\n }\n}"}'

always leads to

{"errors":[{"message":"Forbidden resource","locations":[{"line":2,"column":3}],"path":["info"],"extensions":{"code":"FORBIDDEN","originalError":{"message":"Forbidden resource","error":"Forbidden","statusCode":403}}}],"data":null}

Triple checked everything and tried many variations.

If i damage my token value on purpose i receive a 401 instead, so token is valid.
Tokens Permissions should also be okay to read this simple field: (also tried many other fields...nothing seems to work)
In Apollo / Playground the API is accessible.

--- Edit
It works with an api token with full admin permissions Role: Admin)

A readonly token (Role: Viewer) does not work.
---

Any ideas or hints?

I am trying to add my Unraid server to the NZB360 app on android. It is asking me for a api key but i can't find it anywhere on my server. I am currently on version 7.1.4.

I have looked online and i found that it was suppose to be in the management access in settings but i don't have anything regarding API Keys in there.

Many thanks for you assistance.

Is there a way to completely disable the User/Password login when a OIDC provider is configured? As an extra, just disable it on specific IP-Ranges?

also, FYI: pm2 is aliased to '/usr/local/unraid-api/node_modules/pm2/bin/pm2'

I have attached a screenshot and logs files.

konshu-diagnostics-20250901-1625.zip logs.gtar

Running 7.1.4 and have 5 "Connect" API keys and and 2 "CliInternal" API keys. I'm trying to better understand each of their use and if I can delete non-used ones.

Any suggestion here? What happens if I go and delete all of them, will it break the API/Unraid? Will they just get recreated automatically by the system?

I usually keep my API keys pretty tidy on any platform so this is bugging me a bit :)

Thanks!

I'm unable to successfully create any API keys. If I create one through the terminal, or on the Management Access page, i'm able to go through the process and it looks like it successfully create a key, but if i refresh the page or run unraid-api apikey, the API key that I created disappears, so doesn't seem to properly create and stick.

unraid-api apikey --name HomeAssistant --create --roles ADMIN --permissions array:read,info:read,shares:read

Error: Invalid roles. Valid options are: ADMIN, USER, CONNECT, GUEST

I have turned on developer mode. I've tried "ADMIN" as lower case as well.

Thanks