I'm new to unraid--I still have two weeks left in my trial--and I am rather frustrated.  I'm trying to keep this to a question / request for help, but in attempting to solve it myself, things do not get better.

 

Generally speaking, I have the same problem that many others seem to do--some nebulous API error / cloud socket closed nonsense, which subsequently prompts other "fake" error messages that I've lost all network connectivity and that my cable is unplugged--despite me accessing it from elsewhere on the LAN.  Rebooting the entire server makes the API error go away and so fixes my problem, but rebooting every few days is not a habit I want to get into. 

 

I have to reboot the server, because none of the other fixes (e.g., the api restart command) seem to actually do anything.  I've attempted to review & edit the network settings, but I have to disable the VM and docker to do that (requiring like a dozen additional clicks; a bit obnoxious).  Unfortunately, docker says it's stopped but the network settings says it's not, and I'm back rebooting to fix the problem. 

 

Surely this is not "the way it is" with Unraid?  If I regularly have to reboot or troubleshoot like this, I'd like to know before my trial ends.

 

 

 

Edit: attached diagnostics

 

silverstone-diagnostics-20230706-1221.zip

Edited July 6, 20232 yr by w1ll1ng

Sorry you're experiencing issues. This is definitely not the norm.

 

If the issue is not actively happening for you it'll be very difficult to know what's causing it. As I'm not seeing anything in the diagnostics related to the unraid-api issues.

 

So if it does happen again

1. On your Unraid server navigate to /Settings/ManagementAccess#UnraidNetSettings
2. Scroll all the way to the bottom
3. Download the unraid-api logs
4. Please open a support request on our Contact Page (https://unraid.net/contact#form)
   • "Purpose for Contact" field choose "Unraid Connect"
   • "Link to Forum Post" field supply this forum post URL
5. Then reply to the email message you receive with your unraid-api logs attached.
   • The logs may contain sensitive information so do not post them publicly.

Our Connect devs will then work with you to try and figure out your issue.

I sincerely appreciate your response!  No, the issue is not active for me at the moment---because I rebooted!

 

I will definitely follow your instructions the next time it happens.  It's happened at least three times since I started my unraid trial, so chances are it'll happen again within the next week or so.

 

In full disclosure, I'm probably not using unraid to its fullest.  It's a plex server for now, and maybe something more, later.  All that to say, I haven't done anything intentional in the "Management Access" or "Unraid Connect" portions of this settings window; I haven't provisioned a myunraid.net SSL Cert (because i'm not sure if I need or want to do that); and I hope my ignorance (and ignoring) of these sections isn't causing these problems.

Alright.  I have a brand new motherboard, cpu, and ram (and cache drive, though that one was only a month old anyhow): intel 12400, asrock z690 itx board, and some gskill 3200 non-ECC memory.  I completely lost access to the unraid server (on the old hardware) while I was out of town, last week, and it was inaccessible for most of the week.  Frustrating, especially as there was absolutely nothing I could do.

 

I will comment again if the random disconnection happens again with this all-new-hardware setup.