w1ll1ng

Is there yet any written guide on how to set this up from scratch?

Is there a separate thread or discussion that clarifies how you identify that the USB flash stick is dying or the root of the problems? I'm already using a cheap flash drive, similar to the PNY-manufactured HP-branded one mentioned earlier in this thread. Since it works, I suppose I won't "fix" it with a different one. It'd be nice to be able to clearly identify when the USB stick becomes the problem, though.

I'm sorry; yes, I meant that it says "incompatible."

As a newbie to Unraid, this entire thread is kinda bonkers. I just walked out of a Microcenter, yesterday, with a short form-factor Sandisk USB drive, and I'm here because I have the same problem as everyone else: the USB flash creator doesn't work. Is someone going to tell me that Microcenter is selling counterfeit products? Reading in this thread how unraid users are recommended to agonize over their selection of a usb stick is seemingly antithetical to the entire premise of unraid, which I thought was: use any old hardware and it just works. At some point, there's going to be a market-driven solution to this problem: there will be no (market for) USB sticks that fit the requirements, and unraid will have to change. That is basically the take-away from this thread: the market is almost there.

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.

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.

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