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.

sjaak

Members
  • Joined

  1. i know, dangit, just test another nic with a static ip, i can access the gui... ssh is only listening to eth0 nginx is indeed listening on 0.0.0.0 and ::: so it is open on the other networks. i don't have enabled unraid to use ipv6, only some dockers and VM are using ipv6...
  2. i cant connect with ssh to unRAID on the second NIC, bind_mgt works fine for me... also nginx is only listening on eth0. i don't have ssl enabled so no listening on port 443 SMB/NFS is not affected with this setting, its not a management thing...
  3. so, if i understand correctly, i can't use this container to enable access to my services on IPv6? :(
  4. is here someone who got SWAG fully working on IPv6? i trying to get it working but after view weeks of trail and error i'm out of idea's... Docker is fully working on IPv6, can confirm this. i have a tor relay running on unraid/docker and it external accessible through IPv6... SWAG does have an working IPv6 address. but Cloudflare won't get connection to SWAG on IPv6, resulting many times with error 522 i did some research on nginx with ipv6, its needs '--with-ipv6'? when checking on SWAG with the command: nginx -V it gives me the following configure arguments: no --with-ipv6 in there... anyone have in idea what i can do???
  5. i had problems with unraid when IPv6 was enabled, when its enabled the vm's and docker container wont work with ipv6, so i disabled it and using the second NIC with IPv6 enabled only for the docker containers what need ipv6, and this solution works for me. the vm's got an ipv6 address and docker will work on ipv6. but sometimes unraid itself will try to use that nic to download stuff by using the ipv6 address and this will fail of course because unraid isn't setup for ipv6... i changed the firewall rule by only blocking 8.8.8.8 on port 53 (i want to prevent any device on my network to use googledns)
  6. yeah, i think i found the problem, the driver installer is trying to use IPv6, and unraid itself isn't setup for that. i'm going to temporary disable the second NIC by unplug the fiber (which is setup for IPv6) and then try again. the files are there where they belong, i uploaded it to unraid and 8.8.8.8 is banned on my network (i did found some reference to 8.8.8.8 in this plugin) jup, found the problem, disabled the second NIC and tried again, its finished and its report me to reboot the server
  7. yeah, i have Pi-hole, but unRAID is excluded from it. manual download did work. will trying a second time download.
  8. 6.9.2
  9. unRAID was trying to download the new driver but it fails, no idea to troubleshot this, can't find anything in the logbook:
  10. i trying to disable some SMART attribute notifications on 2 cache devices but it's not disabled en my telegram bot is still spamming me with smart notifications... to reproduce: 1. under main > device (in my cage "cache") > SMART Settings > SMART attribute notifications: 2. disable one or more of the attribute 3. hit apply, and the page is refreshing. after refresh the attribute is disabled. 4. go to "cache 2" 5. disable the same thing (or something else) as "cache" 6. hit apply and after page refresh its disabled. 7. go back to "cache" (not using the backward key!) and now the notifications on "cache" are back to default, "cache 2" are set fine, but when i edit the notifications on "cache" the settings on "Cache 2" are reset to default.... my telegramBot can confirm this... syslog is showing noting of this... i tried this on my desktop running Kubuntu 20.04 with firefox 87.0 and did use the GUI boot of unraid and tried it from there, no luck...
  11. check if you don't have any space " " at front and back of the Nvidia Visible Devices ID, this will happen when you did copy the ID
  12. well... this was a painful update... at reboot i got surprised with "Boot error", put an backup on flash drive still give this error. so recreate a new flashdrive and put the config back on it fixed the problem. then i got problems with the network card (mellanox connectX-3 pro) its a dual NIC but unraid was showing 3 NIC's🤔 found out that its detecting the second nic double, GIU wasn't helping so i edit the network.cfg manually. rebooted, not fixed... found network-rules.cfg and edit this. rebooted and this got fixed. (network-rules.cfg is after reboot gone)
  13. my VM and unRAID itself use a mouse/keyboard of the unRAID GUI. but i search on the Plex forum on that error message and its from the Plex tuner services, i don't use DVR on this server anymore? why is this still trowing errors and instability?? i found this topic where they kill the plex tuner service, i just tried this out and will monitor the logs for any other errors/instability... edit: server still crashing, but now i got this message: Jobs: Exec of /usr/lib/plexmediaserver/Plex Tuner Service failed. (13) no more "Critical: libusb_init failed". but still an unstable server
  14. last weekend i found out that maybe the problem was the DVR, so i remove this from my main server and created an second server for this, but my problem still exist: Starting Plex Media Server. ****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.21.4.4079-1b7748a7b/PLEX MEDIA SERVER/6507dcb9-aeb8-178e-763c213c-306a3ee2.dmp Starting Plex Media Server. Critical: libusb_init failed Mar 1 14:25:39 LMFSv3 kernel: Plex Media Serv[121438]: segfault at b8 ip 0000000000b456af sp 0000148a6a86e920 error 4 in Plex Media Server[a0c000+f23000] Mar 1 14:25:39 LMFSv3 kernel: Code: 46 04 00 48 8d 05 51 ee de 00 49 89 46 08 89 6c 24 08 eb 0d 89 6c 24 08 83 fd ff 0f 84 54 02 00 00 4c 89 64 24 60 4d 8b 67 08 <41> 80 bc 24 b8 00 00 00 00 74 15 49 8d bc 24 90 00 00 00 e8 89 4d Mar 1 14:26:19 LMFSv3 kernel: Plex Media Serv[122854]: segfault at 30 ip 0000000000bbaf9f sp 000014e9e8ffa980 error 4 in Plex Media Server[a0c000+f23000] Mar 1 14:26:19 LMFSv3 kernel: Code: cc cc cc cc cc cc cc cc cc cc cc 55 41 57 41 56 41 55 41 54 53 50 49 89 d5 49 89 f6 8b 36 83 fe ff 0f 84 5b 01 00 00 49 89 fc <48> 8b 7f 08 4d 8d 7e 08 31 c9 41 f6 46 04 40 0f 94 c1 4c 89 fa e8 Mar 1 14:27:00 LMFSv3 kernel: Plex Media Serv[124369]: segfault at b8 ip 0000000000b456af sp 000014840a892920 error 4 in Plex Media Server[a0c000+f23000] Mar 1 14:27:00 LMFSv3 kernel: Code: 46 04 00 48 8d 05 51 ee de 00 49 89 46 08 89 6c 24 08 eb 0d 89 6c 24 08 83 fd ff 0f 84 54 02 00 00 4c 89 64 24 60 4d 8b 67 08 <41> 80 bc 24 b8 00 00 00 00 74 15 49 8d bc 24 90 00 00 00 e8 89 4d the second server is stable, no crash at all. does this mean my main server is corrupted???? WHAT CAN I DO WITHOUT RECREATING MY LIBRARY? its pretty big and recreate this means hours of work and probably some temp ip bans from the metadata sites... i tried this already on the plex forum, the suggested to downgrade to unraid 6.8.3. with is NOT possible for me, i lose HW transcode and the Multi cache pool (where all my VM are running on...)
  15. i checked every .log file in the /logs folder, non of them are showing me anything about a crash only those .dmp files what are in the "Crash Reports" folder inside plex appdata are showing something, but its not possible to past the info here on the forum because it only past some symbols of it, not possible the post the hole .dmp file here...

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.