Leaderboard

Popular Content

Showing content with the highest reputation on 07/27/22 in all areas

  1. Just so we're all clear here... Jellyfin + Unraid 6.10 (or later) = Works Jellyfin + Unraid 6.10 (or later) + iGPU = Works Plex + Unraid 6.10 (or later) = Works Plex + Unraid 6.10 (or later) + iGPU = Does not work
    3 points
  2. Nerd pack needs to be updated. It keeps a database for each Unraid version. The database for 6.11 doesn't exist.
    3 points
  3. Correct. It's just a Plex issue at this point.
    2 points
  4. I have an i9-12900K and upgraded yesterday to 6.11-RC1 and so far no issues to report. I have enabled the iGPU in PLEX again but only did a very brief test and transcoding worked for me without crashing. I did have HDR Tone mapping set to off and did a basic test on a 1080p movie. I know its still hit and miss at the moment so have turned HW transcoding off for the moment until PLEX release their new version and some more fixes in PMS 1.28.1 or 1.28.2. At least we are moving forward and now we have the Linux Kernel updated to the version we need. Now we wait for PLEX to catch up 😞
    2 points
  5. unraid-diagnostics-20220726-2201.zip
    2 points
  6. The only discussion to the contrary are people who set it up and it initially seems to work (it will work, after all) right up till when the crashing starts. To be absolutely clear, *with the current Unraid 6.10 build*, Plex (and Jellyfin, and Emby) work fine, *so long as you don't pass them the iGPU and/or enable hardware transcoding.* This isn't debated at all.
    2 points
  7. I've just updated the My Servers plugin (2022.07.26.1609) and now get the following error: "The My Servers plugin is out-of-date and will not connect to Unraid's cloud services. Please update the plugin." My Servers section of unraid.net shows my server as offline. I uninstalled and then reinstall the plugin, no joy. I have no 0 byte files, and my server DNS was already set to cloudflare & google backup My webgui is on a different port for NPM (44300) In the interim is possible to manually rollback to previous release?
    1 point
  8. This release includes some bug fixes and update of base packages. Sorry no major new feature in this release, but instead we are paying some "technical debt" and laying the groundwork necessary to add better third-party driver and ZFS support. We anticipate a relatively short -rc series. Special thanks to @bonienl for implementation of background downloading, and @ich777 for working with us for better third-party driver integration, still a work-in-process. Please note: It would be extremely helpful to us to report issues by creating separate Reports here rather than creating a reply in this topic. As always, prior to updating, create a backup of your USB flash device: "Main/Flash/Flash Device Settings" - click "Flash Backup". Credits Special thanks to all our beta testers and especially: @bonienl for his continued refinement and updating of the Dynamix webGUI. @Squid for continued refinement of Community Apps and associated feed. @dlandon for continued refinement of Unassigned Devices plugin and patience as we change things under the hood. @ich777 for assistance and passing on knowledge of Linux kernel config changes to support third party drivers and other kernel-related functionality via plugins. @JorgeB for rigorous testing of storage subsystem Version 6.11.0-rc1 2022-07-25 Improvements With this release there have been many base package updates including several CVE mitigations. The Linux kernel update includes mitigation for Processor MMIO stale-data vulnerabilities. The plugin system has been refactored so that 'plugin install' can proceed in the background. This alleviates issue where a user may think installation has crashed and closes the window, when actually it has not crashed. Many other webGUI immprovements. Bug fixes Fixed issue in VM manager where VM log can not open when VM name has an embedded '#' character. Fixed issue where Parity check pause/resume on schedule was broken. Change Log vs. Unraid OS 6.10 Base distro: aaa_base: version 15.1 aaa_glibc-solibs: version 2.35 aaa_libraries: version 15.1 adwaita-icon-theme: version 42.0 appres: version 1.0.6 at-spi2-core: version 2.44.1 atk: version 2.38.0 bind: version 9.18.5 btrfs-progs: version 5.18.1 ca-certificates: version 20220622 cifs-utils: version 6.15 coreutils: version 9.1 curl: version 7.84.0 dbus: version 1.14.0 dmidecode: version 3.4 docker: version 20.10.17 (CVE-2022-29526 CVE-2022-30634 CVE-2022-30629 CVE-2022-30580 CVE-2022-29804 CVE-2022-29162 CVE-2022-31030) editres: version 1.0.8 ethtool: version 5.18 file: version 5.42 findutils: version 4.9.0 freeglut: version 3.2.2 freetype: version 2.12.1 fribidi: version 1.0.12 fuse3: version 3.11.0 gdbm: version 1.23 gdk-pixbuf2: version 2.42.8 git: version 2.37.1 glib2: version 2.72.3 glibc: version 2.35 gnutls: version 3.7.6 gptfdisk: version 1.0.9 harfbuzz: version 4.4.1 hdparm: version 9.64 htop: version 3.2.1 icu4c: version 71.1 inotify-tools: version 3.22.6.0 iproute2: version 5.18.0 iptables: version 1.8.8 json-c: version 0.16_20220414 kernel-firmware: version 20220705_f5f02da kernel-headers: version 5.18.9 kmod: version 30 libX11: version 1.8.1 libXcursor: version 1.2.1 libaio: version 0.3.113 libcap-ng: version 0.8.3 libdrm: version 2.4.110 libepoxy: version 1.5.10 libevdev: version 1.12.1 libgcrypt: version 1.10.1 libgpg-error: version 1.45 libidn: version 1.41 libjpeg-turbo: version 2.1.3 libmnl: version 1.0.5 libnetfilter_conntrack: version 1.0.9 libnfnetlink: version 1.0.2 libnftnl: 1.2.2 libnl3: version 3.6.0 libtiff: version 4.4.0 libtiff: version 4.4.0 liburcu: version 0.13.1 libusb: version 1.0.26 libxcb: version 1.15 libxkbcommon: version 1.4.1 libzip: version 1.9.2 libX11: version 1.8.1 listres: version 1.0.5 logrotate: version 3.20.1 lsof: version 4.95.0 lzip: version 1.23 mc: version 4.8.28 mcelog: version 184 mkfontscale: version 1.2.2 nano: version 6.3 nettle: version 3.8 nfs-utils: version 2.6.1 nghttp2: version 1.48.0 ntfs-3g: version 2022.5.17 oniguruma: version 6.9.8 openssh: version 9.0p1 openssl: version 1.1.1q (CVE-2022-1292 CVE-2022-2097 CVE-2022-2274) openssl-solibs: version 1.1.1q (CVE-2022-1292) pango: version 1.50.8 pciutils: version 3.8.0 pcre2: version 10.40 php: version 7.4.30 (CVE-2022-31625 CVE-2022-31626) rsync: version 3.2.4 samba: version 4.15.8 setxkbmap: version 1.3.3 shared-mime-info: version 2.2 sqlite: version 3.39.2 sudo: version 1.9.11p3 sysfsutils: version 2.1.1 tdb: version 1.4.7 tevent: version 0.12.1 tree: version 2.0.2 util-linux: version 2.38 wget: version 1.21.3 xauth: version 1.1.2 xclock: version 1.1.1 xdpyinfo: version 1.3.3 xfsprogs: version 5.18.0 xkeyboard-config: version 2.36 xload: version 1.1.4 xmodmap: version 1.0.11 xsm: version 1.0.5 xterm: version 372 xwud: version 1.0.6 Linux kernel: version 5.18.14 (CVE-2022-21123 (CVE-2022-21123 CVE-2022-21125 CVE-2022-21166) oot: md/unraid: version 2.9.23 CONFIG_IOMMU_DEFAULT_PASSTHROUGH: Passthrough CONFIG_VIRTIO_IOMMU: Virtio IOMMU driver CONFIG_X86_AMD_PSTATE: AMD Processor P-State driver CONFIG_FIREWIRE: FireWire driver stack CONFIG_FIREWIRE_OHCI: OHCI-1394 controllers CONFIG_FIREWIRE_SBP2: Storage devices (SBP-2 protocol) CONFIG_FIREWIRE_NET: IP networking over 1394 CONFIG_INPUT_UINPUT: User level driver support CONFIG_INPUT_JOYDEV: Joystick interface CONFIG_INPUT_JOYSTICK: Joysticks/Gamepads CONFIG_JOYSTICK_XPAD: X-Box gamepad support CONFIG_JOYSTICK_XPAD_FF: X-Box gamepad rumble support CONFIG_JOYSTICK_XPAD_LEDS: LED Support for Xbox360 controller 'BigX' LED Management: rc.nginx: enable OCSP stapling on certs which include an OCSP responder URL rc.wireguard: add better troubleshooting for WireGuard autostart rc.S: support early load of plugin driver modules upc: version v1.3.0 webgui: Plugin system update Detach frontend and backend operation Use nchan as communication channel Allow window to be closed while backend continues Use SWAL as window manager Added multi remove ability on Plugins page Added update all plugins with details webgui: docker: use docker label as primary source for WebUI This makes the 'net.unraid.docker.webui' docker label the primary source when parsing the web UI address. If the docker label is missing, the template value will be used instead. webgui: Update Credits.page webgui: VM manager: Fix VM log can not open when VM name has an embedded '#' webgui: Management Access page: add details for self-signed certs webgui: Parity check: fix regression error webgui: Remove session creation in scripts webgui: Update ssh key regex Add support for ed25519/sk-ed25519 Remove support for ecdsa (insecure) Use proper regex to check for valid key types webgui: misc. style updates
    1 point
  9. Works fine for me and has for 7 months now. Just because you can't figure out what YOU'RE doing wrong, doesn't mean it doesn't work. Don't be obtuse. The author is NOT your personal IT support. Figure out your own issues like everyone else.
    1 point
  10. No that diagnostics was the second thing I did with the server after the reboot. (the first thing was to start the VM "Daily-driver", via my mobile phone, wich is my "daily-use-computer")
    1 point
  11. I think I find some of the issue. I had a docker container called unraid-api which was causing error messages in my Home Assistant VM. Also causing high CPU usage. Once I turned it off errors stopped and usage became more normal. VM Errors CPU usage after turning of unraid-api docker
    1 point
  12. It sorts by newest movie files, yes. But it does not "run in the background". It runs whenever you start it.
    1 point
  13. Okay, it seems to have come back online but because it's yet another new flash drive my license key isn't valid and needs to be transferred over. I'll contact support and see if they can allow another transfer to a new drive within the year.
    1 point
  14. Not quite sure why it's not seeing the upgrade, but if you go to Settings - Notification Settings and disable (never check) for OS upgrades, then the Check For Updates button will appear
    1 point
  15. No worries. It just caught my eye and I went "huh?"
    1 point
  16. I just wish that had solved the issue for me. I've even done it twice with no success.
    1 point
  17. [email protected]:~# ls -al /usr/local/sbin/unraid-api lrwxrwxrwx 1 root root 36 Jul 27 17:38 /usr/local/sbin/unraid-api -> /usr/local/bin/unraid-api/unraid-api [email protected]:~# ls -al /usr/local/bin/unraid-api/ /bin/ls: cannot access '/usr/local/bin/unraid-api/': No such file or directory
    1 point
  18. Thank-you wgstarks - I did mean to add that I do intend to use that Docker in the meantime so I can get some backups running, so thanks for highlighting that option. I just wanted to make sure the Unraid team had visibility that it's affecting a number of people!
    1 point
  19. Again, I have had a great experience with the TimeMachine docker. It’s up to you if you want to wait to see if the issues that a few people are having with TM get resolved but if you decide to use the docker I wrote a how-to for configuring it for multiple machines. https://forums.unraid.net/topic/123985-timemachine-application-support-thread/?do=findComment&comment=1134386
    1 point
  20. Well it says the same for me, but if you check the logs I attached you can see that the installation was completed.
    1 point
  21. I had the same issue a few hours ago, also noticed the plugin install took an unusually long time to install, especially for the first lines to appear, windows was blank for a long time, though it appeared to install correctly, I now removed the plugin from the flash drive, rebooted, re-installed, install was quick and now it's working.
    1 point
  22. from your screenshot it looks like you defined the 'Name' of the port incorrectly, its not 'WEBUI PORT' its 'WEBUI_PORT' and the type is wrong, its a variable NOT a port. @Squid you are quite right, the user should not be redefining the container port - however qbittorrent is an exception to the case here, here are my notes from the qbittorrent README.md (geared more towards non unraid users, but you get the gist):- so for unraid users that means setting WEBUI_PORT to the port you want and then re-creating the port to match (host and container side being the same). i then have some code to pick up the env var WEBUI_PORT to set the port for the running application (qbittorrent in this case).
    1 point
  23. FYI just upgraded to v7.1.68 as it didn't seem to have many changes. No issues upgrading. Will report back if anything goes haywire.
    1 point
  24. so containers talking to each other in the SAME network can be done via localhost and the port the application uses, you should not be defining ports in VPN_OUTPUT_PORTS unless you want an application using the VPN network to communicate OUTSIDE of the VPN network to another application. see A24 note 1 for details about localhost:- https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md see A27 for details about correct usage of VPN_OUTPUT_PORTS https://github.com/binhex/documentation/blob/master/docker/faq/vpn.md you should be able to use a custom network - at least it did work in testing a long time ago!, what you cannot use is specific ip addresses for the vpn container, that will not work. p.s. i do not like the usage of VPN_OUTPUT_PORTS or VPN_INPUT_PORTS actually, its a little confusing for the average user, however its a necessary evil (havent found a better way) to guarantee zero ip leakage which of course is the most important thing, so for now thats how it is.
    1 point
  25. Please keep me updated when the new version is released so that I can test it on my own, I think/hope it should work with the existing container as it is currently implemented.
    1 point
  26. Error: [autovideoconverter] Skipping '/watch/TEST_MOVIE': not readable, check permissions. Unraid: 6.9.1 Handbrake 1.5.1 I'm new to using this HandBrake docker and am also having trouble with auto video conversion /watch. A manual conversion of the same folder is successful so the path(s) are read/writeable. Any ideas? Shares: /watch : /mnt/user/movies/TEST/ : (public) /output : /mnt/user/mkv/ : (public) Watch folder permissions: drwxrwxrwx 1 nobody users 32 Jul 26 21:22 TEST_MOVIE/
    1 point
  27. as a side note i just uninstalled unassigned devices and so far my speeds are around 150mb/s
    1 point
  28. Love to see these quick release series. Hope all goes smoothly.
    1 point
  29. Both come up with the same answer. Looks like a display issue. I'll have a look.
    1 point
  30. AFAIK yes. Two different concepts. The VPN_INPUT and OUTPUT ports are to punch holes in the delugevpn containers internal firewall. The container is sealed up pretty tight to keep the VPN connection secure from accidental real WAN IP exposure.
    1 point
  31. du solltest die Optionen für CPPC im BIOS aktivieren. Konnte ich bisher aber noch nicht verifizieren. Danke für den Einsatz @ich777 ! Ich hab mein System gerade erst wieder stabil bekommen, will es eigentlich ungern auf ein Prerelease loslassen.... aber neugierig was man messen kann bin ich schon ... vielleicht nächste Woche.
    1 point
  32. Both docker.img and cache are readonly due to corruption. You can recreate docker.img after you fix cache. You may have to copy what you can from cache and reformat it. Have you done memtest recently?
    1 point
  33. Du solltest diesen Thread mal lesen, weil das selbst in Windows nicht trivial ist: https://www.computerbase.de/forum/threads/renoir-und-b550-die-idle-kuenstler.1967755/ Hier auch mein Beitrag: https://www.computerbase.de/forum/threads/renoir-und-b550-die-idle-kuenstler.1967755/post-24812476 Es sollte in jedem Fall ASPM und ALPM forciert werden. Je nach Board hat die Deaktivierung von Komponenten wie zb LED Controller keinen oder einen großen Einfluss auf den Verbrauch. Da hilft nur durchprobieren und jede Änderung messen.
    1 point
  34. Top right corner (after you search).
    1 point
  35. Personally I would prefer a "G" type processor. UNRAID does not need the full power of the 5800X (which is overkill too if you do not plan to overclock). I've picked a 5700G for myself and am quite pleased with it. The "G" also comes handy if you plan to put in another graphics card to be passed thru to a VM (though I have no experience with this, but the forum here contains a lot of problems with passthru, so better search for them and look for solutions.) 4-5 VMs are no problem, unless you do evil things with them like DOWNLOADING. Unraid's QEMU is a snail when it comes to fast LAN transfers. The cores hit 100% usage rather easily and the temp goes up through the sky 😞 Even with one VM doing heavy downloading, you can kill the box already. Its really a shame. AMD CPUS and RAM is a delicate combination with UNRAID. If ECC or not, you need to run "memtest86" (download the newest version, the version that comes with unraid does not recognize modern CPUs/RAM) for some time and experiment with the BIOS settings if any problems show up. Even buying "3200" ram does not guarantee that your board/cpu/power supply combination allows you to use this speed safely. Some advice you to raise certain voltages (which will result in a fast wearout of the ramchips), I would personally say "don't go over 1,35V. instead lower the speed". My box for instance runs stable with 1,35V and 3000 Mhz only. (you dont need to wait for memtest to finish each time. Once an error shows up, cancel, change bios and restart memtest skipping the tests that have been successful before, After all tests have passed, play it even safer and rerun memtests from the beginning (all tests) once more) Instead putting money on ECC better spend a week on memtest. Unless you change ram sticks (or your values are too high), you will be safe for years.
    1 point
  36. @SpencerJ and the team worked hard through the 4th of July to bring a surprise, which awaits at:
    1 point
  37. can confirm that ich777 is the one of the best and fastest answers from him you can get for help if needed ...
    1 point
  38. Indeed, thank you both. The Community and Unraid will not be the same without the great work you do. 🤘
    1 point
  39. Is the build for today borked for anyone else? Seeing this over and over in the logs and can't reach the admin page:
    1 point
  40. here are my vm settings and my flash if you can see any different
    1 point
  41. the point is not actually to prepare the disk for unraid, that is just a nicety that this utility can/should do, the MAIN purpose is to exercise your drive and ensure it doesn't suffer from infant mortality.
    1 point
  42. 我解决了,反向代理都没有问题。比如用 https://c.b.com:1234 这个地址是不能访问到unraid上的需要后面加 login 变成https://c.b.com:1234/login 才能正确访问!!!!!
    1 point
  43. I finally found a fix, that works with my machine! I added the following code to the /flash/config/go file: #fix video for VM echo 0 > /sys/class/vtconsole/vtcon0/bind echo 0 > /sys/class/vtconsole/vtcon1/bind echo efi-framebuffer.0 > /sys/bus/platform/drivers/efi-framebuffer/unbind Those lines unbind the console & by adding it to /flash/config/go will execute this piece of code on every boot of the system.
    1 point
  44. I realize this is a serious necropost, but wanted to give @maciekish a huge thank you for sticking with this after the responses he got. I'm using a reverse proxy with Nginx and had the same problem and this lead me to the same solution. So for anybody getting here from Google you'll want to add the following to your Nginx config to get things working again. You could be clever and only apply it to the locations that are broken, but since my reverse proxy is not even exposed outside my network I just disabled gzip for the whole server definition: server { gzip off; ... } As an FYI to all the doubters above, if they still hold their positions. A reverse proxy is a very handy way to make it so you don't have to remember unique port numbers of all your internal services. http://unraid.home.local or http://sonarr.home.local are totally valid internal domains if your DNS is setup right and will hint the server to your password database tool of choice so you don't have it offering up 30 passwords because everything is on the same IP address of the server.
    1 point
  45. It's easy for us to get overwhelmed by new issues, especially coinciding with new features and new kernel releases. Our lack of immediate reply does not mean your report is being ignored. We very much appreciate all hints, testing results, etc. Remember, for very odd issues, please reboot in "Safe Mode" to ensure no strange interaction with a plugin.
    1 point
  46. It was actually complaining every eight minutes. Toggling Use SSL to Off (click Apply) and back to Auto (click Apply) seems to have stopped the messages.
    1 point
  47. KVM can handle vmdk files directly. The only caveat is that you have to enter the full path to the vmdk when creating the VM as the GUI does not provide a selector for that file type.
    1 point