UnraidC

I don't know why exactly, but this (or one of the things below) is what solved it in the end: I noticed that docker.img had grown >50gb (which is not normal from what I found on reddit somewhere as I only run a few dockers). I removed all dockers via the "Docker" tab in Unraid. I stopped the docker service (under "settings -> docker"). I tried to delete the docker.img via the option in the same menu after turning docker off, but nothing happened (was following these instructions: https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file), i.e. the file remained in place, even after several tries. I then tried to delete the file directly via system/docker/docker.img (going via the "Share" tab in Unraid) but whenever I hit delete nothing happened either (i.e. the file just remained in place). I rebooted the server, leaving the docker service off. I then tried again to delete the file (same as in step 5). This time it did delete and the system/docker/ folder ended up empty. I then used the "Cleanup Appdata" plugin to remove all of the appdata paths shown there (except for 3 which I was quasi sure were not the ones causing issues as they never did before) I reinstalled most dockers, except nginx and traefik. Remote access to server was working again - problem solved. So in the end it seems one of the dockers or some combination was causing issues (I still assume it was something related to Nginx or maybe Traefik even though I did almost nothing with the latter). Before doing the above I had already just tried deleting different dockers etc. but that did not resolve it. Cannot say why it worked but it did, so maybe it can help somebody else as well at some point without wasting hours of your life on it. In closing, thank you @JorgeB for taking the time and effort to think along with me, I appreciate it!

Hello, This is the diagnostic. The main issue for me is not the swap limit error but the fact that my server has no more remote access since messing around with Nginx. More info in this thread in case you'd spot something in the diagnostic file: tower-diagnostics-20241216-0128.zip

Just some update, a few more hours down the line: 1) I noticed that when I change anything in the Nginx docker (e.g. setting the network from "host" to "br0") it gives an error message saying something to the effect of "WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap" - I don't know if that is what is causing the server's network to fail? I honestly don't know to begin with what you suggested (that is not on you to be clear). After hours and hours and hours of messing around I'm completely lost. 2) Would deleting network.cfg start to get me out of this situation? (based on this thread): Or maybe Nginx would still be messing with something in the background? [edit: removed fluff]

Hello, I installed Nginx Manager and was playing around with it, only to end up losing all connectivity to my server (only accessible now via physical connection of monitor/keyboard/mouse and logging in to GUi from there). I am desperately trying to undo whatever issue this docker caused but I cannot seem to get rid of it, even if I remove the docker... I do notice that when I install it and change something, it also gives me the "kernel does not support swap limit capabilities" error, does it mean that that could be what is breaking my server? disclaimer: I'm a total novice at Unraid and anything IT related

Would the assumption be that the issue is likely with network.cfg on the USB drive? Is that something that is affected by Nginx? I am pretty sure the issue originated from / is caused by whatever it is that Nginx is doing or changed, I would like to try to reverse whatever Nginx did first (and just removing the docker apparently is not enough) and just get rid of everything related to Nginx before moving on to more complex potential solutions? Is there perhaps something to be found in the diagnostics files pointing to anything strange? When I open "servers.conf.txt" in the diagnostics file I see some reference to Nginx, but I don't know what to make of it.

I probably did not explain well: the GUI is working but only when I physically am connected to the server. The problem is that I cannot connect to the server from the PC anymore. Do I understand it correctly that I should basically get the oldest appdata backup that I have (Backup B mentioned above), plug the Unraid USB in my PC and override the config folder with the config folder in the Backup B and that should restore things to normal?

Hello everyone, Disclaimer: Unraid is by far the most IT technical thing I have ever done, all based on iterative trial and error. It seems I really messed up this time however. Definitions PC = my main computer (1st machine) Server = the 2nd machine that has Unraid on it Everything is purely within the LAN network, both PC and Server are in the same house, i.e. both are connected to the walls in their respective rooms via an ethernet cable. How the problem started: Decided to give Ngninx a try since I wanted to see if I could get HTTPS working. Installed Nginx docker, messed around with it a bit, seemed like I could not get it to work (could get it to make an SSL certificate via DuckDNS and set up some Proxy Hosts with duckdns subdomains, but everything staid HTTP when I clicked on the proxy host). Basically had no idea what I was doing. Was experimenting with having Nginx Proxy Hosts direct to different ports etc. and figured I'd just trial and error things a bit while following some Youtube tutorials etc. to see how far I'd get. Basically that's how I got this far using Unraid over the past several months in general. I was not aware about this being potentially dangerous outside of the docker containers, in hindsight I guess I should have. At some point I was also changing some ports in the different docker settings (as far as I know I did not create any overlapping ports, but who knows) and tried putting some dockers from "Bridge" to "br0" etc. (not having any deep understanding about the differences) but that did not seem to do much, in the end I just set everything back to "Bridge". Installed Traefik docker in Unraid, but then decided against starting to mess around with that as well, so jumped back to Nginx. All of a sudden I did not have LAN access to the server anymore (purely from messing around with Nginx as far as I could tell). Strangely, I could still go to different tabs within the Nginx GUI itself (e.g. "Proxy Host" and "SSL" tabs) but all the other dockers (including Unraid GUI itself) were unavailable so I was basically stuck - I tried to walk my steps back in Nginx but I don't know at what stage everything broke and I don't remember when I changed what, as I had been messing with it on and off over the course of several hours. Whenever I try to connect to the Server (or any of the dockers like Nextcloud or Jellyfin) from my PC via my PC browser (tested multiple browsers, using bookmarks to e.g. Nextcloud so nothing changed there either), both via "tower.local" or the "IP address", I get this message: "This site can’t be reached 192.168.0.100 [note: this is my local Unraid server IP] refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED" Once the problem occured: I still see the Server on its fixed LAN IP when logging into my modem, so that seems normal. I can get into the Server via physically connecting a screen/keyboard/mouse and booting into GUI (it seems to actually start a Linux instace and automatically opened a Firefox browser showing the Unraid GUI in there - hopefully makes sense?). The GUI in the Firefox browser on the server connects to the tower.local address in the adress bar. When I open a second tab in that Firefox browser on the server I seemingly can use the IP address to get to the login screen as well. However, I cannot get to the login screen via my PC anymore, neither to any of the dockers and SMB is also down (cannot get to my folders via windows explorer on PC). I tried connecting via my PC browser both without the dockers running and after the dockers started. Booting the Server in Unraid safe mode also does not change anything it seems. I think I managed to get the diagnostics file (see attachment). When I open "servers.conf.txt" in the diagnostics file I see some reference to Nginx, but I don't know what to make of it. I just mention it here because it may be relevant for somebody who does know how to read it. I really tried troubleshooting it myself but I honestly do not know what else to do anymore at this stage without potentially creating an even bigger mess. I hope one of the experts here can help me get my server back up and running. Any help would be greatly, greatly appreciated. // Reporting back on some more troubleshooting I did in the meantime: Uninstalled the Nginx docker. Did not change anything. Reinstalled the Nginx docker, which gave errors because it as a standard uses port 80. I changed the Nginx docker settings back to what it was before I removed it. Strangely, when I then launched the Nginx GUI on the server, it just got me straight into Nginx, where it apparently had remembered the login credentials and still had the proxy host and SSL certificate? In other words, removing the Nginx docker apparently did not remove everything related to it and as a result also did not solve the issue and I still only have physical access to server with nothing remote (on the LAN) working tower-diagnostics-20241216-0128.zip

Thank you for your reply, I am a bit intimidated by what you are saying though as it seems to be a lot of things that I can individually mess up and I don't know what any of it means or what steps to take... I am really at absolute beginner level. If at all possible I'd like to start with the simplest possible solutions where I can cause the least amount of collateral damage. Backup the flash drive -> you mean run the Appdata Backup plugin? I have 2 backup files (.zip) via Appdata Backup: "Backup A" from today (16 december) which I just manually did via the "Manual Backup" button in the plugin. "Backup B" from the 2nd of december (when everything was still working normally). Alternatively, do you mean a "Backup C" that I would need to create now using Unraid Connect. I found these instructions via https://docs.unraid.net/connect/flash-backup/: "Navigate to Settings → Management Access → Unraid Connect and under Flash backup click the Activate button. Wait for the activation and initial backup job to complete." However, I read there "Important: Backups from the flash device do not include the config/shadow or config/smbpasswd files. User accounts are preserved, but their passwords are not. This means that when you restore from backup, you will need to set passwords for your users including root. We also don't store any of your WireGuard keys". This makes me very nervous as I am afraid of getting locked out entirely / having to mess around with setting up SMB shares again Also, I had a look but I do not see any "Unraid Connect" options under "Settings → Management Access"? I see that within the Appadata Backup plugin there is also a "restore" tab, is there any point in trying that before going through the chain you mentioned above? Recreate using the USB tool Are you referring to https://unraid.net/blog/new-usb-creator ? I found this description online: "You download the unraid USB creator. Download a zip copy of your flash drive backup from unraid connect. Plug new flash drive into the computer, open the USB creator, on the drop down select local file, point to the flash drive zip file. Select your USB drive then create." -> would this be the Appdata Backup file or the Unraid Connect file in your advice or are they essentially the same? just restore the bare minimum, like the key, super.dat and the pools folder for the assignments -> I don't know what that means or how to do that, could you please elaborate or point me to some information? also copy the docker user templates folder -> copy it to where? if all works you can then reconfigure the server -> what should work before I reconfigure what/how on the server? or try restoring a few config files at a time from the backup to see if you can find the culprit -> I don't know what the actual process is here to restore a few config files at a time? Which config files and what order and so on and finding the culprit would imply breaking it again? Thank you for your help, your time and effort is much appreciated!

Reporting back on some more troubleshooting I did in the meantime: Uninstalled the Nginx docker. Did not change anything. Reinstalled the Nginx docker, which gave errors because it as a standard uses port 80. I changed the Nginx docker settings back to what it was before I removed it. Strangely, when I then launched the Nginx GUI on the server, it just got me straight into Nginx, where it apparently had remembered the login credentials and still had the proxy host and SSL certificate? In other words, removing the Nginx docker apparently did not remove everything related to it and as a result also did not solve the issue [edit: apparently there was some misunderstanding here on my end because the settings of the dockers are saved separately in appdata, so when you remove a docker but don't remove the appdata, the next time you install the docker again it just loads its settings from the appdata again and it looks like nothing happened - clever design but I had no idea how it worked so to me it looked completely illogical when I wrote this post because I assumed that removing the docker is to remove everything including any settings, which in Unraid turned out to not be the case here even though I assume that Nginx related appdata on its own was not what was causing issues, but idk.]

Hello everyone, Definitions PC = my main computer (1st machine) Server = the 2nd machine that has Unraid on it Everything is purely within the LAN network, both PC and Server are in the same house, i.e. both are connected to the walls in their respective rooms via an ethernet cable. How the problem started: Decided to give Ngninx a try since I wanted to see if I could get HTTPS working. Installed Nginx docker, messed around with it a bit, seemed like I could not get it to work (could get it to make an SSL certificate via DuckDNS and set up some Proxy Hosts with duckdns subdomains, but everything staid HTTP when I clicked on the proxy host). Basically had no idea what I was doing. Was experimenting with having Nginx Proxy Hosts direct to different ports etc. and figured I'd just trial and error things a bit while following some Youtube tutorials etc. to see how far I'd get. Basically that's how I got this far using Unraid over the past several months in general. I was not aware about this being potentially dangerous outside of the docker containers, in hindsight I guess I should have. At some point I was also changing some ports in the different docker settings (as far as I know I did not create any overlapping ports, but who knows) and tried putting some dockers from "Bridge" to "br0" etc. (not having any deep understanding about the differences) but that did not seem to do much, in the end I just set everything back to "Bridge". Installed Traefik docker in Unraid, but then decided against starting to mess around with that as well, so jumped back to Nginx. All of a sudden I did not have LAN access to the server anymore (purely from messing around with Nginx as far as I could tell). Strangely, I could still go to different tabs within the Nginx GUI itself (e.g. "Proxy Host" and "SSL" tabs) but all the other dockers (including Unraid GUI itself) were unavailable so I was basically stuck - I tried to walk my steps back in Nginx but I don't know at what stage everything broke and I don't remember when I changed what, as I had been messing with it on and off over the course of several hours. Whenever I try to connect to the Server (or any of the dockers like Nextcloud or Jellyfin) from my PC via my PC browser (tested multiple browsers, using bookmarks to e.g. Nextcloud so nothing changed there either), both via "tower.local" or the "IP address", I get this message: "This site can’t be reached 192.168.0.100 [note: this is my local Unraid server IP] refused to connect. Try: Checking the connection Checking the proxy and the firewall ERR_CONNECTION_REFUSED" Once the problem occured: I still see the Server on its fixed LAN IP when logging into my modem, so that seems normal. I can get into the Server via physically connecting a screen/keyboard/mouse and booting into GUI (it seems to actually start a Linux instace and automatically opened a Firefox browser showing the Unraid GUI in there - hopefully makes sense?). The GUI in the Firefox browser on the server connects to the tower.local address in the adress bar. When I open a second tab in that Firefox browser on the server I seemingly can use the IP address to get to the login screen as well. However, I cannot get to the login screen via my PC anymore, neither to any of the dockers and SMB is also down (cannot get to my folders via windows explorer on PC). I tried connecting via my PC browser both without the dockers running and after the dockers started. Booting the Server in Unraid safe mode also does not change anything it seems. I think I managed to get the diagnostics file (see attachment). When I open "servers.conf.txt" in the diagnostics file I see some reference to Nginx, but I don't know what to make of it. I just mention it here because it may be relevant for somebody who does know how to read it. [edit: removed fluff]

Hello, What solved it for me up to now was: 1) No "hidden" shares (i.e. all shares are purely set to "Export = Yes", with user access restrictions - as a result everybody on the network can see every share but most users can only read and/or write a few shares that are relevant to them). 2) Manually added network connections for the relevant shares, based on the LAN IP address. I think it sucks that this was such a pain in the ass to troubleshoot and that some settings (like "Yes (hidden)" export settings) seem to be de facto unuseable, at least to me, but it is what it is I guess. Hope it helps!

Just some feedback from a very recent new user of Unraid. I have been mostly happy with the experience up to now. In theory legacy users will not be affected (not that I put any money on "Trust me bro" statements right after previous model turnarounds, but that is a different matter), but I care about more than just myself when I am going around recommending stuff to people as I have been doing with Unraid since I started with it a few weeks ago. It is your product and you are free to do with it what you want, obviously. I am not coming at this from any "moral" perspective or anything like that. At the same time, your end user does not care about your internal issues and cost structures (at least not the new ones signing up). That does not mean that I do not get the need for recurring income, but there are other models for doing so that are also proven in the market and that I personally find more palatable (e.g. paid business support, saying this as a business owner by the way who would potentially end up paying such support). The reality is that without security updates (as confirmed in the FAQ) you are de facto turning it into a subscription model for an internet-connected server system. You can twist and turn about that as much as you want, but the twisting and turning about it is perhaps the most offputting element of this to me to be honest, more than the model change itself. At least don't insult people's intelligence, I believe my own lying eyes and cannot be convinced that gravity does not affect me while observing that objectively it does. If this had been announced a few weeks ago in this manner I would have never gotten into Unraid, and I will also not be recommending it anymore to others. A friend of mine just received his server hardware on my recommendation but I told him to look elsewhere after reading this. That at least is 1 lost customer, nearly 2 if I had known before (but of course I myself will ride it out now with the legacy license while it lasts). In any case, it completely shifts the USP and perception of the product and the company, and for sure made the alternatives much more attractive. I am purely from a business perspective very curious to see what this will lead to in the mid to long run, fully assuming you know best how to run your own company even though from my own perspective I raised an eyebrow and shook my head at the course you are pursuing here.

Unfortunately the problem came back a few days later now: again got the "check spelling" error... Really don't know what to do anymore. Any help or thoughts would be appreciated

I'm hesitant to say it but for the past 2 days the issue seems to have improved (watch it going wrong tomorrow of course). I am not sure what made the difference, but I think it may have been putting every exported file to "Yes" now and no more "Yes - hidden" Was not able to set up the Network Neighborhood with any results. Will see how it goes and report back if anything changes. Thanks for the suggestions, fingers crossed that it remains stable...

I tried that in my earlier post but would get the same "check spelling" error in the end. As you say, the internet solutions do not seem to be working... What a mess indeed, was hoping for a smoother experience when I got started with Unraid

I think the instructions skip a step because when just creating a Network Neighborhood folder on my desktop it does not become shared? I am indeed working from the Admin account of the windows desktop.

Quick question on the Network Neighborhood instructions: The Network Neighborhood folder I created per the instructions is not automatically shared like shown in the sceenshot in the "Unraid & Windows 10 SMB Setup" pdf referred to above. When I click the Share button in the Properties/Share tab of my Network Neighborhood folder, it says: After a while, I get this message: No idea what the problem would be. To circumvent this, I click Advanced Sharing then I can tick a box to "share this folder": This then results in the folder appearing to be shared like in the "Unraid & Windows 10 SMB Setup" pdf: I then copy the blacked out network path (which refers to the folder on the desktop). Following that, I try to add the network location as instructed, resulting in this: So that does not seem to solve things

OK, I will give it a try and report back. Yes, aside from the recurring reboots sometimes to try and get the shares to show up again up to now (hopefully resolved at some point and then in theory to stay on permanently). This is a tricky one given my use case and circumstances, will try the Network Neighbourhood first - fingers crossed. Thanks for your time and assistance!

Both desktop and server have wifi turned off and running on an ethernet lan connection. No but I thought that was only necessary when you don't have this view automatically (from the "Unraid & Windows 10 SMB setup" PDF referenced earlier in this thread): Under Network, I can see the Unraid server when it works (like ELSIE1 in the example screenshot above, but with my own unraid server name), but often after waking dekstop from sleep it is not there anymore. All of the shares have been added individually as network locations, as well as the unraid server itself. But I have done it directly and not in a separate "Network Neighbourhood" folder, is there any reason why adding the extra step of a folder would change anything you think? Yes when it works I can access the server via Windows Explorer. The problem is that often it does not show up under Network, thus not allowing me to access the shares from Windows Explorer (not from the "Network" view like in the screenshot above, not from the mapped drives under This PC and not from the quick access links referring to them). Originally I was only using the server name. Because of the issues I experienced I also tried to use the IP, but the issue persists ("check spelling" error and not seeing the server nor the shares in windows explorer when waking desktop from sleep). I have not noticed any differences whether or not I am connecting through IP or server name, nor with having only 1 or multiple credentials (i.e. only or both based on name and IP) set up. All the drives were added as a network location individually and afterwards those netword locations were pinned to quick access as well (i.e. the experienced issue is not due to typo's). Curious about your thoughts!

Given the context the server is intended to be used in I do not want other people on the network to be able to put something onto a public share, (i.e. all exported shares must be private for my use case). As such I did not have any public shares set up. Even so, I added one just now to see if it makes any difference going forward (but would not want one structurally). Will report back on this later if this would solve anything.

Yes, I had several shares as export "Yes - Hidden". Based on your post I changed all exported shares to just "Yes" now, but this did not change anything: after desktop went to sleep and logging back on I again got the "check spelling" error. Re: case sensitivity: my shares are structured like this for example: 1. Documents 2. Images I.e. a digit followed by a dot and a space followed by a capitalized word. Do you think that is causing issues?

Hello, Apologies for the delayed reply, have been completely swamped by work the past few days but still very eager to follow up on this I am trusting your expertise over mine, so diagnostics attached below: [diagnostics file removed] Additional information re: desktop: Windows 11 Pro Version 22H2 (when checking for updates it says everything is up to date). I have followed all the guides mentioned above I believe (private network, credentials set up (originally for only the name, then also for the IP - sometimes the IP one works when the name one does not, but almost always when 1 has the issue the other gets the "check spelling" error as well), set up network drives, no insecure guest logons, SMB 1.0 turned off in Windows Features - screenshots in OP). The desktop does not share any folders (only Unraid exports shares, all private). Would be great if you would be willing to have a look - thank you in advance!

Edit: diagnostics added in a post below.

Edit: diagnostics added in a post below.

Edit: what seems to have stabilized things a bit is not using the shares export option "Yes-Hidden" anymore, but using only "Yes" or "No". Edit: turns out a few days later that the problem occurred again, to my despair Any help or thoughts would be appreciated. Hello, Context: Have set up Unraid server, which is the most IT-technical project I have ever done - my professional expertise lies elsewhere but I am eagerly trying to learn. Docker containers etc. work fine, up to now have always been able to access webgui's so that has not been an issue (yet). The problem I am running into is that often I cannot access the shares through my Windows Explorer. It is very inconsistent, sometimes I can, sometimes I cannot (e.g. after a reboot of pc, or of Unraid, or most often after pc went to sleep, etc.). The "solution" is then to reboot the desktop and/or unraid (sometimes several times) but it is a hassle and cannot be the intended way of working. The error message that I get is Windows cannot access "server name" and to "check the spelling". At that stage the server is also not detectable in the network. It basically makes the Unraid server unusable for the purpose it was intended when I cannot consistently access the shares through windows explorer... I have tried everything I could find online I think, sometimes based on posts of several years ago, but the problem remains so I now landed at the point of complete desperation after having wasted a lot of frustration and hours of very scarce free time on this. I hope something positive can still be salvaged from it with the help from people here who know better. The current situation is as follows: Router set to allocate a fixed local IP address to the Unraid server. In Unraid itself the IPv4 address assignment is set to automatic and it picks up the IP address allocated to it by the router (edit: afterwards have also tried changing it to static with the same router allocated IP while also still letting the router allocate the IP, but does not seem to change anything either way). I can also access all webgui's of Unraid itself and various dockers through this address using the assigned ports. Note: before this I set only a static address in Unraid itself (the same one as now is allocated by the router) and did not have the router assign it, this made no difference (in fact I hoped setting the IP address in the router vs in Unraid would fix things). SMB setting as follows based on some forum posts I found. Note the extra configuration settings, which originally only consisted of the first line (ntlm auth = yes). Whether these settings are here in full, only the first line or nothing at all does not seem to affect anything. All shares are private like this (sometimes export = "yes" and sometimes "yes (hidden)". I always refer to user 1 credentials. Insecure guest logins have been disabled under local group policy editor / local computer policy / computer configuration / administrative templates / network / lanman workstation. Under credential manager in windows the user 1 credentials have been added and allow me to access the shares when they sometimes show up. This is what shows up in the log. Please feel free to request any necessary info I possibly forgot to include here and I will adjust this post accordingly. Any and all help would be welcome and very much appreciated, I genuinely gave it my best try based on the information I was able to piece together from various online sources before bothering people with it here. I hope I did not bite off more than I can chew and end up having wasted my time and money on this but it is looking bleak Thank you so much for having a look!