Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

kylehandy123

Members
  • Joined

  • Last visited

  1. Updating to 7.1.4 solved the issue. I did check my containers and found the cause of the containers restarting. None appears to be restarting randomly. Closing thread.
  2. New diags attached. I know this was likely not a great move, but I updated to Unraid 7.1.4 which appears to have so far prevented the issue of "The docker server failed to start" despite already running, from occurring again. mainserver-diagnostics-20250927-1555.zip
  3. As the title suggests. The docker service appears to not be running, but I can still access containers that were running before the docker tab reports this. This has been occuring for the last 7-10 days. Diagnostics attached. mainserver-diagnostics-20250927-0235.zip
  4. I went ahead and removed the duplicate files. I was under the impression that mover would skip the files. This did get things moving and mover has moved nearly 3TB of data over the last few days now, so thank you for your advice. I'm attaching new diagnostics moreso for my understanding - mover is being extremely slow compared to what I'm used to, with no changes minus new, identical drives, being added to my server (same drives I already use). This may be my own fault, but nonetheless, I at least want to try to understand what the hold up is. Edit: It appears mover has grinded to a halt again. mainserver-diagnostics-20250604-1917.zip
  5. I updated to Unraid 7.1.2. Although mover does move a handful of files, it eventually stops, despite reporting it's still running. New diagnostics attached. mainserver-diagnostics-20250602-0016.zip
  6. Hi all, I recently added 2 new drives. I've noticed Mover is no longer moving files in any reasonable time frame. I have mover logging enabled, and watching the log, I rarely see any files move. I also realize I do not have a parity drive. I have 2 new Seagate Ironwolf NAS drives waiting to be installed once this problem is solved. Diagnostics are attached. mainserver-diagnostics-20250601-1810.zip
  7. Fair enough! I'll return here when needed if problems continue upon correcting network issues among others. I appreciate both of you for helping up until now.
  8. I had an nginx container running that needed port 80, and would fail consistently without it. @trurl Could you lock this thread? I have discovered further problems outside unraid, so until I resolve those, I won't be able to finish resolving unraid. I apologize.
  9. Tried safe mode. No WebUI on any machines other than the actual Unraid server. Diags attached. mainserver-diagnostics-20250212-1721.zip
  10. Apologies regarding the other category. See attached logs taken immediately after the array reported running. mainserver-diagnostics-20250212-0719.zip
  11. Hey all, I have an open ticket for issues with the docker engine crashing. But as a result of working on fixing that in said other ticket, I'm now unable to access the WebUI after restoring the USB from a backup, or using a fresh USB image with the config files moved over to retain plugin/docker templates and settings. For some reason, when I took diagnostics, two zip files were created. Hence the two attachments. See attached. mainserver-diagnostics-20250211-1716.zip mainserver-diagnostics-20250211-1721.zip
  12. Apologies. Apparently I completely blanked. Attached. Two log files generated back to back, so I've attached them both. I'm not sure why this occurred. mainserver-diagnostics-20250211-1721.zip mainserver-diagnostics-20250211-1716.zip
  13. Final update for the night. I am unable to connect to the webui anymore. I can use the physical server with a monitor to get the GUI up, and it's connected to the network, but I can't connect to the webui from any system. IP and port of the unraid machine is the same as before. I need ideas on how to correct this. Secondly, all docker containers are gone, so I will need to reinstall them all. This is fine, I have the appdata, and everything should work fine. Albeit very frustrating since this will take quite a few hours to do since my backup wasn't super recent, but recent enough it's usable. Any ideas?
  14. Noting new issues, upon rebuilding the USB: I can't access the WebUI but the unraid box does have a working internet connection, and local connection, as far as I can tell. All of my docker containers are gone? So I'll now have to reinstall them all? Trying to troubleshoot the whole no webui issue now.
  15. Making note here that I have just rebuilt the existing USB and am currently booting the server. I'll reply either if it crashes, or stating that its working normally.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.