ljm42

Administrators
  • Posts

    4374
  • Joined

  • Last visited

  • Days Won

    27

Everything posted by ljm42

  1. 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.
  2. When you are ready to try again, be sure to grab your diagnostics.zip (from Tools -> Diagnostics) while in the new version. Then start a new thread under General Support, describe the issue and upload the diagnostics.
  3. I'm confused about that first screenshot, did you actually see that or did you grab it from another post somewhere?
  4. This is correct. The certificate_bundle.pem cert is ONLY valid for *.myunraid.net urls. There is zero benefit to using it with other urls. If you access the server by IP address or by name then it will use a self-signed cert. It is fully setup. To use it, click the url starting with https://192-168... that you blanked out of the screenshot. For more information, see https://docs.unraid.net/unraid-os/manual/security/secure-webgui-ssl/
  5. Keep playing with this, it should do what you want. The only other option is to change the IP in the client config but as you said it is not exactly secure. If you can't get it to work, try hosting VPN on your Unifi device instead.
  6. This is not normal. Do you have the WG Docker container enabled at the same time? Maybe there is some sort of conflict. I'd suggest stopping the Docker container and following the guide here to set up the built in one: https://forums.unraid.net/topic/84226-wireguard-quickstart/ Get "Remote access to LAN" working before trying something else. Read the entirety of the first two posts in that thread, there are many helpful tips that may point out an issue in your network.
  7. Are you changing SSL settings? The only cause I know of for what you are describing happens when you disable SSL, it can confuse your browser. To help prevent confusion, the webgui shows this message: If you are sure that is not the cause, go to Settings > Syslog Server and temporarily enable "Mirror syslog to flash". The next time it happens: 1) clear your browser's cache to see if that helps 2) if not, reboot the server and upload your diagnostics (from Tools -> Diagnostics) here Note: once you past this issue be sure to disable "Mirror syslog to flash" as it adds wear and tear to the flash drive
  8. Think of Unraid as an appliance, not a general purpose operating system. If you need a place to perform "daily business" the recommendation would be to run a different OS in a VM.
  9. Manual upgrade instructions are in the docs: https://docs.unraid.net/unraid-os/manual/upgrade-instructions/#manual-upgrade-or-downgrade It sounds like you might have skipped this step: Move (not copy) bz* and changes.txt from the root of the flash drive to the "previous" directory, overwriting files as needed If so, when you replaced the files in the root of the flash you overwrote the running OS. There is no graceful recovery for this. Your best bet would be to turn the system off, put the flash drive in a different computer, and follow those manual instructions from the top
  10. Unraid 6.12.8 does not have proper support for Lifetime keys. Please upgrade to Unraid 6.12.10
  11. Yes, this release is intended to resolve the issue with your drive controller: https://forums.unraid.net/topic/160471-unraid-os-version-61210-available/
  12. Yes the update process isn't really setup for people to run in "pending restart" mode for an extended period. TBH this could confuse plugins and other things that aren't prepared for this as well, I would not recommend updating the OS until you are ready to restart. 6.12.9 does have an issue with certain Asmedia controllers, if you are at all concerned about that you can go to Settings -> Disk Settings and disable array autostart. Then when it boots into 6.12.9 there will be no problems and you can just run the update to 6.12.10 and reboot into that.
  13. This is suspect. Try manually stopping the container (reload the page and be sure it is really stopped) before doing the update and see if it makes a difference. Otherwise, I agree with the suggestion to recreate the docker image
  14. Unraid 6.12.10 is now available:
  15. Thanks, we got the feedback we needed and have published 6.12.10:
  16. This release reverts to an earlier version of the Linux kernel to resolve two issues being reported in 6.12.9. It also includes a 'curl' security update and corner case bug fix. All users are encouraged to read the release notes and upgrade. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, 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 If you have Unraid 6.12.8 or Unraid Connect installed: Open the dropdown in the top-right of the Unraid webgui and click Check for Update. More details in this blog post If you are on an earlier version: Go to Tools -> Update OS and switch to the "Stable" branch if needed. If the update doesn't show, click "Check for Updates" Wait for the update to download and install 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. 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.
  17. Thanks, this link is part of the Unraid Connect plugin. It will be fixed in an upcoming plugin release. In the meantime, this link should do the trick: https://discord.unraid.net/
  18. Hi, please install 6.12.10-rc.1 and confirm it resolves the issue: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-61210-rc1-available-r2941/
  19. This is resolved in 6.12.10-rc.1 if you would like to test and confirm: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-61210-rc1-available-r2941/
  20. If you are affected by this please install 6.12.10-rc.1 and confirm it resolves the issue: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-61210-rc1-available-r2941/
  21. Hi folks, if you are affected by this please install 6.12.10-rc.1 and confirm it resolves the issue: https://forums.unraid.net/bug-reports/prereleases/unraid-os-version-61210-rc1-available-r2941/ The problematic commits were added to kernel 6.1.80, so for this release we reverted from kernel 6.1.82 to 6.1.79.
  22. This release reverts to an earlier version of the Linux kernel to resolve two issues being reported in 6.12.9. It also includes a 'curl' security update and corner case bug fix. We'd appreciate your feedback before releasing it as 6.12.10 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. Upgrade steps for this release As always, prior to upgrading, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Update all of your plugins. This is critical for the Connect, NVIDIA and Realtek plugins in particular. If the system is currently running 6.12.0 - 6.12.6, 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. If you have a recent release or Unraid Connect installed: Open the dropdown in the top-right of the Unraid webgui and click Check for Update, then press More options and switch to the Next branch. You may be prompted to sign in to access the Next branch. Select the appropriate version and choose "View changelog to Start Update". More details in this blog post If you are on an earlier version: Go to Tools -> Update OS and switch to the "Next" branch. If the update doesn't show, click "Check for Updates" Wait for the update to download and install 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. 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. Upgrade notes This release reverts to an earlier version of the Linux kernel to resolve two issues being reported in 6.12.9. It also includes a 'curl' security update and corner case bug fix. Known issues Out of date plugins Out of date plugins can cause problems, we recommend they be kept current. Call traces and crashes related to macvlan If you are getting call traces related to macvlan (or any unexplained crashes, really), as a first step we recommend navigating to Settings > Docker, switching to advanced view, and changing the Docker custom network type from macvlan to ipvlan. This is the default configuration that Unraid has shipped with since version 6.11.5 and should work for most systems. Note that some users have reported issues with port forwarding from certain routers (Fritzbox) and reduced functionality with advanced network management tools (Ubiquity) when in ipvlan mode. If this affects you, see the alternate solution available since Unraid 6.12.4. Network problems due to jumbo frames If you are having network issues of any kind, confirm that you have not enabled jumbo frames. Navigate to Settings > Network Settings > eth0 and confirm the Desired MTU is 1500. For more information see the Fix Common Problems warning for jumbo frames. Problems due to Realtek network cards Upgraded kernel fixes the deadlock issue with jumbo frames and the in-tree Realtek 8125 driver. However, we still recommend following the advice above regarding jumbo frames. If you continue to have network stability issues and Tools > System Devices shows that you have a Realtek ethernet controller, grab the part number shown and search Community Apps to see if there is a Realtek vendor-supplied driver plugin for that device. For more information, see the support page for Realtek driver plugins. Other issues? We highly recommend installing the Fix Common Problems plugin as it will warn you of common configuration problems. If you are having other crashes or stability issues, navigate to Settings > Syslog Server and enable Mirror syslog to flash. This will cause additional wear and tear on you USB flash boot device but is useful in the short term for gathering logs after a crash. After the next reboot, navigate to Tools > Diagnostics and download your anonymized diagnostics (as of 6.12.5, diagnostics automatically include logs that were mirrored to the flash drive). Finally, start a new topic and provide all the details of the issue. Once the issue is resolved, be sure to disable Mirror syslog to flash. Rolling back Be aware that rolling back to an earlier release will make your system vulnerable to the Docker security issues and potential data loss scenario mentioned in Upgrade notes. If rolling back earlier than 6.12.9, also see the 6.12.9 release notes. Changes vs. 6.12.9 Bug fixes and improvements Resolve issues mounting remote SMB shares via the Unassigned Devices plugin. Resolve issues with certain Asmedia controllers not seeing all the attached devices. nfs: (revert) NFSv4 mounts by default zfs: Detect if insufficient pools slots are defined for an imported pool with a missing device. Fix translations issue with SystemDrivers Base Distro curl: version: 8.7.1 (CVE-2024-2466 CVE-2024-2398 CVE-2024-2379 CVE-2024-2004) Linux kernel version 6.1.79 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.
  23. The 6.12 branch of the Unraid webgui repo is here if you would like to submit a PR: https://github.com/unraid/webgui/tree/6.12 The exact file is: https://github.com/unraid/webgui/blob/6.12/emhttp/plugins/dynamix/scripts/monitor Nice troubleshooting. This is not my area of expertise, but your research helps a lot. Do you think this: grep -c 'missing' should be changed to: grep -c 'ERROR' Or should it check for both? grep -Ec 'missing|ERROR' Would you mind testing locally by adding '- x' near the end of line 196: exec("$notify -l '/Main' -e ".escapeshellarg("Unraid $text message")." -s ".escapeshellarg("Warning [$server] - Cache pool BTRFS missing device(s)")." -d ".escapeshellarg("$info")." -i \"warning\" -x 2>/dev/null"); That will give you one notification for this subject per reboot (or until you go to Tools -> Archived Notifications and delete the notification)