hes

Hallo, Sorry for late reply, I was on holiday trip. Thanks, it worked to re-install connect plugin. I could not re-sign since it was grayed out. I did not think that the most obvious step will help 🙂 BR

Hallo, can you plz check the discussion in general support forum? I have the problem that unraid api cannot connect to server and I get red triangle in dashboard saying API is offline. In addition to the description in the topic below I tried to run "unraid-api restart" but I get same error as shown ... What is wrong? What can I do? Thanks

forgot to attach the API log file: logs.json

You are right, the anonymizer works quite well. I did some little cleaning of plain names in the file ... Syslogs show the error: Apr 11 12:41:09 unraid rc.nginx: Starting Nginx server daemon... Apr 11 12:41:10 unraid root: node:internal/modules/package_json_reader:268 Apr 11 12:41:10 unraid root: throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null); Apr 11 12:41:10 unraid root: ^ Apr 11 12:41:10 unraid root: Apr 11 12:41:10 unraid root: Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'execa' imported from /usr/local/unraid-api/dist/cli.js Apr 11 12:41:10 unraid root: at Object.getPackageJSONURL (node:internal/modules/package_json_reader:268:9) Apr 11 12:41:10 unraid root: at packageResolve (node:internal/modules/esm/resolve:768:81) Apr 11 12:41:10 unraid root: at moduleResolve (node:internal/modules/esm/resolve:854:18) Apr 11 12:41:10 unraid root: at defaultResolve (node:internal/modules/esm/resolve:984:11) Apr 11 12:41:10 unraid root: at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:685:12) Apr 11 12:41:10 unraid root: at #cachedDefaultResolve (node:internal/modules/esm/loader:634:25) Apr 11 12:41:10 unraid root: at ModuleLoader.resolve (node:internal/modules/esm/loader:617:38) Apr 11 12:41:10 unraid root: at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:273:38) Apr 11 12:41:10 unraid root: at ModuleJob._link (node:internal/modules/esm/module_job:135:49) { Apr 11 12:41:10 unraid root: code: 'ERR_MODULE_NOT_FOUND' Apr 11 12:41:10 unraid root: } Apr 11 12:41:10 unraid root: Apr 11 12:41:10 unraid root: Node.js v22.14.0 Apr 11 12:41:10 unraid rc.nginx: Nginx server daemon... Started. MY main problem is the RED Triangle in Unraid UI saying that API is not connected. But its maybe not related to error above. Syslog also says: Apr 11 12:40:41 unraid rc.local: Checking DNS... Apr 11 12:40:41 unraid rc.local: ⚠️ Warning: Your DNS server (192.168.1.1) is unable to resolve 'mothership.unraid.net' Apr 11 12:40:41 unraid rc.local: Recommend navigating to Settings -> Network Settings and changing your DNS server to 8.8.8.8 But thats no true. When I make "nslookup mothership.unraid.net" on unraid cmd line I get: Server: 192.168.1.1 Address: 192.168.1.1#53 Non-authoritative answer: Name: mothership.unraid.net Address: 172.67.69.176 Name: mothership.unraid.net Address: 104.26.3.117 Name: mothership.unraid.net Address: 104.26.2.117 Thats wired ... BR unraid-diagnostics-20250411-1503.zip

I suppose the Moderator is from Unraid team? Can I upload somewhere? not sure if there are sensitive or privacy information in it.

Hallo, I have same problem. I get red triangle saying that API is offline. If I'm deleting network.cfg doesnt help. Same issue. I also have the same error as above for nginx restart. What can I do? cat /boot/config/network.cfg # Generated settings: IFNAME[0]="br0" DHCP_KEEPRESOLV="no" DHCP6_KEEPRESOLV="yes" BONDNAME[0]="bond0" BONDNICS[0]="eth0 eth1 eth2 eth3" BONDING_MODE[0]="1" BONDING_MIIMON[0]="100" BRNAME[0]="br0" BRNICS[0]="bond0" BRSTP[0]="no" BRFD[0]="0" PROTOCOL[0]="ipv4" USE_DHCP[0]="yes" USE_DHCP6[0]="" SYSNICS="1"