Jump to content

ljm42

Administrators
  • Posts

    4,427
  • Joined

  • Last visited

  • Days Won

    27

Posts posted by ljm42

  1. The .local domain uses Multicast DNS ( https://en.wikipedia.org/wiki/Multicast_DNS ) so an actual DNS server is not required. It is the only domain that works that way though, all other domains require a DNS server.

     

    The easiest solution would probably be to use the DNS server that your domain registrar provides, assuming they let you point at internal IPs. Cloudflare can work too. Note that you may need to disable DNS Rebinding Protection on your router and/or DNS servers to let clients resolve local IPs for FQDNs.

     

    You may find this page of the docs helpful:
    https://docs.unraid.net/unraid-os/manual/security#securing-webgui-connections-ssl

  2. You are getting call traces related to macvlan, please see the known issues section of the 6.12.0 release notes:

    https://docs.unraid.net/unraid-os/release-notes/6.12.0#known-issues

     

    Also, if I'm reading your syslog correctly it looks like you have a Realtek RTL8168h/8111h NIC. You may benefit from these 3rd party drivers:

    https://forums.unraid.net/topic/141349-plugin-realtek-r8125-r8168-and-r8152-drivers/

     

  3. RE: transcoding in RAM...

     

    Oh yeah, I ran like that for a while.

     

    Normally Docker containers are isolated from the system so the container can't hurt the host. If you override that by giving the container access to a system folder like /tmp, there is the chance that the container can cause problems for the host when something goes wrong. That is essentially what happened here, a problem with Plex filled up the system's /tmp folder and caused problems for the OS.

  4. 4 minutes ago, blaine07 said:

    On 6.12.2 and 6.12.3 Everytime docker starts it stays like this a substantial amount of time. Do not have plex here; but Jellyfin. 

     

    My first question is does the system eventually recover? But this seems like a topic that will take a bit of back and forth, so I'd suggest creating your own thread and uploading diagnostics. It is very difficult to have a lot of back and forth in a release thread.

    • Like 1
  5. 19 minutes ago, Can0n said:

    Been having a lot of problems especially with Plex (using official container) and I have a lot of friends and family that use it. It's been going down several times a day where we started the container is necessary

     

    Plex is mentioned specifically in the release notes (which I know you read : ) ) so if you continue to have issues add --no-healthcheck as mentioned there

     

    20 minutes ago, Can0n said:

    Mover has a lot of problems on 6.12.2 as well, especially when trying to move shares from a ZFS pool to the array using xfs it will never finish completely because it can't delete the data sets from ZFS

     

    If you have a thread discussing this, be sure to add new diagnostics after upgrading to 6.12.3. If you don't have a thread, please create one specific to this issue.  It is very difficult to have a lot of back and forth in a release thread.

    • Like 1
  6. The 6.12.3 release includes a set of bug fixes for networking and Docker.  All users are encouraged to upgrade.

     

    Please refer also to the 6.12.0 Announcement post.

     

    Upgrade steps for this release

    1. As always, prior to upgrading, create a backup of your USB flash device:  "Main/Flash/Flash Device Settings" - click "Flash Backup".
    2. Update all of your plugins. This is critical for the NVIDIA and Realtek plugins in particular.
    3. If the system is currently running 6.12.0 - 6.12.2, we're going to suggest that you stop the array at this point. If it gets stuck on "Retry unmounting shares", open a web terminal and type:
      umount /var/lib/docker

      The array should now stop successfully (This issue is resolved with this release)

    4. Go to Tools -> Update OS. If the update doesn't show, click "Check for Updates"
    5. Wait for the update to download and install
    6. If you have any plugins that install 3rd party drivers (NVIDIA, Realtek, etc), wait for the notification that the new version of the driver has been downloaded. 
    7. Reboot

     

    This thread is perfect for quick questions or comments, but if you suspect there will be back and forth for your specific issue, please start a new topic. Be sure to include your diagnostics.zip.

    • Like 13
    • Thanks 4
  7. Looking at the diagnostics, I am unclear what network card you have. It might be based on the RTL8125 chip or it might be RTL8226/RTL8221. Either way, it is definitely not the RTL8168 so it makes sense that installing the wrong driver would cause issues. If you can figure out which network card you have and install the driver appropriate for that card you may have more success. Or if your system is working fine then you may not need a different driver for your hardware at all.

     

    Keep in mind that plugins are provided free of charge by other community members because they want to be helpful. You may want to consider editing the language on your earlier posts.

  8. 15 hours ago, jflad17 said:

    I can try doing this now. I had this issue on 6.11.5. I tried all suggestions and nothing seemed to work. I think the issue might be related to libvirt. I saw a log in that section of settings I think, where it kept throwing libvirt errors. All I was trying to do was get smb working properly for Synology after noticing files not having certain permissions. I'll reply back if this did indeed fix my issue. 

     

    The fix in 6.12.3-rc3 is specifically for the docker.img

     

    If you think libvirt.img is preventing a stop, please see this comment: https://forums.unraid.net/topic/141479-6122-array-stop-stuck-on-retry-unmounting-disk-shares/#comment-1281063

    Except you'll want to manually umount the libvirt.img rather than the docker.img

     

    Then please take diagnostics before rebooting so I can see the logs showing that libvirt.img was preventing the array from stopping. Thanks!

    • Like 1
  9. Thank you, I can see there was an error starting the tunnel, but that should have prevented the containers from getting access to the network.  In the short term, I'd recommend setting those containers to not auto-start.

     

    I see you are using IPv6, would you please upgrade to 6.12.3-rc3 as it has improvements related to IPv6:

    https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-6123-rc3-available-r2572/

     

    Once in rc3, make a dummy change to wg1 and hit save to make sure it has the latest PostUp/PostDown commands.

     

    Then try starting wg1. Whether it works or fails, please generate new diagnostics so I can see what changed.  If you are curious what I'm looking at, you can open the diagnostics zip file and look at logs/wg-quick.txt

  10. You are having a conflict between the built-in WireGuard and the WireGuard Easy Docker container.

     

    You should use either the built-in WireGuard or a Docker container, but not both.

     

    If you want to use the built-in WireGuard, delete the Docker container and see:

      https://forums.unraid.net/topic/84226-wireguard-quickstart/

     

     

    If you want to use a Docker container for WireGuard, go to Settings -> VPN Manager and make sure nothing there is running or set to autostart. Then *just* use the Docker container from here on out.   Support for the "WireGuard Easy" Docker container is here:
      https://forums.unraid.net/topic/117195-support-smartphonelover-wireguard-easy/

  11. Were these diagnostics taken while the problem was happening? It doesn't look like any errors were logged.

     

    Try bringing up the Javascript Console in your browser and see if there are errors. CTRL-SHIFT-I works on most browsers, or you can try right click -> Inspect -> Console

     

    Also, if you have browsers/tabs left open on phones/tablets/other computers, close them all. Some people have issues with tabs being backgrounded and not properly letting go of resources.

×
×
  • Create New...