urmyboyblue

Members
  • Posts

    6
  • Joined

  • Last visited

Everything posted by urmyboyblue

  1. I have a Realtek R8186 NIC and the Fix Common Problems app listed this as a warning for me. I assume it doesn't apply, correct?
  2. https://github.com/go-gitea/gitea/issues/25915#issuecomment-1640933269 Followed this to get mine working.
  3. Thanks @Indmenity83! I had this issue where the Plex container was logging to log.json and filling up /run which caused problems with all containers not starting (found that from here) I was deleting the log.json file manually but bow this --no-healthcheck option prevents it from happening. Would love to know if this is happening because of something else being wrong or if it's a bug that should be fixed.
  4. Same!! Been pulling my hair out trying to figure this out too! Thanks @vstylez_!! Is this a bug or something gone awry? EDIT Found this which on another thread which was causing my issues. Added the "--no-healthcheck" option under my Plex container and the logs stopped.
  5. I'm getting these as well periodically. Best I can tell is that they seem to happen when my backup share (over Tailscale) starts seeing some issues (possibly packet loss somewhere?) and "du" or "df" (can't remember) starts failing to that remote share. But once it happens there is no recovery - even when the remote Tailscale node recovers, which I can see from my laptop on my same home LAN. The main issue I start seeing is that my docker apps won't restart and throw an exception. The only way to recover Unraid is a reboot. Yeah, I know the Tailscale container states that it is intended to provide remote access to Unraid only (not any gateway functionality).
  6. Great utility... thanks!! I have it all working (using SWAG/NGINX - /opt/log directory path is set to my SWAG /mnt/user/appdata/swag/log/nginx/ folder) and pulling into the access.log. I am seeing this error message though: nginx: [alert] could not open error log file: open() "/var/lib/nginx/logs/error.log" failed (13: Permission denied) Couldn't find much from a Google search. Any idea how to fix it? The error.log file is in the same directory as access.log so I assume it can read it.