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.

Ambrotos

Members
  • Joined

  • Last visited

Everything posted by Ambrotos

  1. I know this thread is a bit stale, but for anyone else landing here after searching for the same issue, I also initially saw "bad gateway" on a fresh install. In my case, the problem was because I didn't notice that the necessary seafile-mc environment variable is "DB_ROOT_PASSWD", not "DB_ROOT_PASSWORD". (notice the missing "OR"!)
  2. Since upgrading to 6.7.0 a couple days ago, I have started seeing the following message in my system log. May 16 07:00:02 nas kernel: DMAR: [DMA Read] Request device [03:00.0] fault addr ffabc000 [fault reason 06] PTE Read access is not set Some quick Googling suggests that this is related somehow to IOMMU, though I don't use hardware passthrough for any of my VMs and anyway I've confirmed that IOMMU is reported as enabled by unRAID. The error message is similar to one raised during the 6.7RC. Maybe the patch that was included to fix the previous issue had an unintended side effect? Unlike the issue reported by Duggie264, I am not using any HP240 controllers. Mine are all IT reflashed m1015s or H310s. Also, note that the PCI device that it's complaining about is my Intel nVME drive that's currently not part of the array and is mounted by UA. Maybe that's related? Attached are my diagnostics. Does anyone have any thoughts on this? Cheers, -A P.S. - I should mention that I upgraded direct from 6.6.7. I don't play with RCs on this server, I have a test server for that. nas-diagnostics-20190516-1634.zip
  3. Yup, I noticed that there was an update to the plugin this morning. Looks good! Thanks. -A
  4. Is it just my system, or has anyone else noticed that the Settings icon for NUT doesn’t display anymore since the January 24th update to fa font? I initially thought it was just a browser cache thing, but I’ve since tried multiple browsers, multiple computers, etc. The NUT icon in the plugins page loads fine, but I’m assuming that’s because it hasn’t been changed to be “awesome” (Running 6.6.6 if that matters. I haven’t had a chance to try out the 6.7RC yet) -A
  5. Ah yes, I do see the mlx4_core reference in the second trace message there. I must have made a typo when I searched the first time and didn't find anything. So alright, is Mellanox a common element of this issue? @AcidReign, what drivers are you using? @Hoopster? -A
  6. I reported a similar issue a while ago which at the time I suspected might have been related to the 10G Mellanox drivers I was using not playing nicely with macvlan. I don't see any reference to the Mellanox drivers in your stack trace though; it looks like you're using Intel drivers. So maybe this is a more common issue than I'd assumed. I haven't really been following it since I last saw it in August. I can confirm at least that it was present in version 6.5.3. Is it safe to assume that you're running 6.6.3? If so, that begins to put a range on the affected software versions... Anyway, as I mentioned in my post linked above, I just avoided the issue by removing VLANs and using multiple hardware NICs. I'm just chiming in here to report that I've seen this issue as well. Cheers, -A
  7. Ambrotos replied to fc0712's topic in General Support
    As Frank said above, feel free to use Preclear plugin for convenience if you like, but since its original purpose (minimizing downtime required to insert new drives) has been integrated into unRAID itself, I've stopped using it. A lot of people (myself included) continued to use it for a while to detect "infant mortality" in newly installed hard drives, but since the plugin doesn't seem to be supported anymore (regardless of whether it technically runs or not) we probably shouldn't even be doing that much. Myself, to address the need to detect flaky drives on install I've been opening up the handy new web-based terminal window, starting a "screen" session, and issuing a badblocks command. This does much the same thing as the preclear plugin did; read/write the entire disk and compare with expected contents. badblocks -nvs /dev/sdx will do a non-destructive test of the entire disk. If you don't care about the data on the disk you can do badblocks -wvs /dev/sdx. Just my $0.02 -A
  8. Works like a charm. Thanks for taking a look at this so quickly. Cheers, -A
  9. Thanks for the updated plugin! I've been running without integration w/ my UPS since development of the v1 plugin was stalled a couple years ago. Much appreciated! One bit of feedback: you seem to have put a constraint on the length of the text field for "port". I have a networked TrippLite SMART5000RT, which can be polled via SNMP. However, the allowed length of the port field when the snmp-ups driver is selected is too short to enter "192.168.0.31". I got it to work by configuring the plugin for "manual only" mode and putting the following into the ups.conf file: [ups] driver = snmp-ups port = 192.168.0.31 community = public snmp_version = v2c pollfreq = 15 If you increased the allowed length of the port text box I'd be able to use auto config as well Thanks again, -A
  10. Success! Thank you very much! Cheers, -A
  11. Quick followup, I was able to get the plugin to start correctly by simply adding the following to the docker image: docker exec -it LogitechMediaServer apt-get install libcrypt-openssl-bignum-perl libcrypt-openssl-random-perl libcrypt-openssl-rsa-perl
  12. That's what I'm trying to confirm. Right now, it appears that the only things missing are the following modules: Bignum.pm RSA.pm Random.pm ...but I'm trying to make sure that if I provide these modules manually then it starts properly. I don't want to ask for a list of modules that winds up being incomplete. The current error message only lists RSA.pm, but that's just because that's where it currently fails. I can't be sure that it won't fail on some dependency further down the list until I try it for myself. Hopefully I'll have an opportunity to dig a bit more after work this evening. I'll keep you posted. Cheers, -A
  13. Hm, unfortunately that didn't resolve the startup exception. But, digging into it a bit I think I know why. The log reports the error in the file Plugin.pm, line 33. If you open that file, it's trying to load Crypt::OpenSSL::RSA, a Perl module. If you check earlier in that same file, you see the line use lib catdir($Bin, 'Plugins', 'ShairTunes2W', 'lib'); ... so the module is expecting the ./Plugins/ShairTunes2W/lib folder to contain the library of Perl modules for loading. The lib folder seems to contain OpenSSL module files for each of several recent versions of Perl; 5.12, 5.14, 5.18, and 5.20. Unfortunately, if you run docker exec -it perl -v in the latest LMS docker, you can see what we're running Perl v5.22. Just on a whim, I tried copying the 5.20 directory to a new directory called 5.22, but upon restart that resulted in a different error regarding undefined symbols etc. Anyway, it seems that the ShairTunes2 plugin is looking for OpenSSL Perl modules in the config/cache/InstalledPlugins/Plugins/ShairTunes2W/lib folder, not the OpenSSL executable in /usr/bin. I'm going to see if I can download the OpenSSL modules specifically for Perl 5.22 from CPAN and load them into the correct library folder. I'll let you know how it goes. Cheers, -A
  14. I'm really sorry to do this to you again, but now I'm trying to load up the latest ShairTunes2 (fork) plugin in order to enable my LMS as an AirPlay receiver, and I'm getting a "Plugin Failed to load" error. If you check the LMS docker log file, it's pretty clear why: [17-07-11 11:44:17.8246] Slim::bootstrap::tryModuleLoad (286) Warning: Module [Plugins::ShairTunes2W::Plugin] failed to load: Can't locate Crypt/OpenSSL/RSA.pm in @INC (you may need to install the Crypt::OpenSSL::RSA module) (@INC contains: /usr/sbin/Plugins/ShairTunes2W/lib /config/cache/InstalledPlugins/Plugins/ShairTunes2W/lib /config/cache/InstalledPlugins /usr/share/squeezeboxserver/CPAN/arch/5.22/x86_64-linux-thread-multi /usr/share/squeezeboxserver/CPAN/arch/5.22/x86_64-linux-thread-multi/auto /usr/share/squeezeboxserver/CPAN/arch/5.22.1/x86_64-linux-gnu-thread-multi /usr/share/squeezeboxserver/CPAN/arch/5.22.1/x86_64-linux-gnu-thread-multi/auto /usr/share/squeezeboxserver/CPAN/arch/5.22/x86_64-linux-gnu-thread-multi /usr/share/squeezeboxserver/CPAN/arch/5.22/x86_64-linux-gnu-thread-multi/auto /usr/share/squeezeboxserver/CPAN/arch/x86_64-linux-gnu-thread-multi /usr/share/squeezeboxserver/CPAN/arch/5.22 /usr/share/squeezeboxserver/lib /usr/share/squeezeboxserver/CPAN /usr/share/squeezeboxserver /usr/sbin /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.22.1 /usr/local/share/perl/5.22.1 /usr/lib/x86_64-linux-gnu/perl5/5.22 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.22 /usr/share/perl/5.22 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base .) at /config/cache/InstalledPlugins/Plugins/ShairTunes2W/Plugin.pm line 33. BEGIN failed--compilation aborted at /config/cache/InstalledPlugins/Plugins/ShairTunes2W/Plugin.pm line 33. Any chance you could add OpenSSL to the Docker OS when you get a chance? Cheers, -A
  15. Awesome. Thanks! Seems to have addressed the issue. After updating the server's Web UI can now properly load the feed.xml and show the tracklist. I'll have to wait until I'm home tonight in order to test actually playing the feed, but I'm assuming that won't be a problem. Cheers, -A
  16. Could you consider adding IO::Socket::SSL to the docker? I'm trying to use the Podcast plugin to listen to a Podcast that's available via an HTTPS feed, and I keep getting the error: There was an error loading the remote feed for : (Can't connect to https URL lack of IO::Socket::SSL Thanks!
  17. I'd also love to see NUT support built in. I'm using a Tripp Lite SMART5000RT3U which obviously isn't supported by APC. Also, since Macester didn't get a chance to include SNMP support before he stopped developing the plugin, I've had to fork his repository and make my own hacks. It works, but I would obviously prefer to be using a supported solution for something as important as UPS monitoring and safe shutdown. There used to be a similar feature request for baked in NUT back in the unRAID v5 days. If I remember correctly, the talk was of moving away from APC and onto NUT. Last I checked it was still in the "Unscheduled" sub-forum, though I can't seem to find the topic anymore. Anyway, +1 from me on this. -A
  18. Hm. Odd. I just deleted the container (and its resulting orphan from Advanced view) and then recreated from the my-syncthing template. Didn't even modify configuration. Now it's upgraded to 0.13.10. Sorry, I guess I should have tried that before posting. Just didn't occur to me that that would do anything -A
  19. It appears that my install of syncthing is stuck at v0.12.22 while all of my desktop-based peers have upgraded automatically to the latest stable version of v0.13.10. I've restarted the docker, checked the appdata/syncthing folder to make sure it's writeable, verified that <autoUpgradeIntervalH> is set to 12 in the config.xml. Generally I would expect to be able to trigger an upgrade by logging into the syncthing webUI and clicking the "Upgrade" button in the banner when one is available. For my docker-based syncthing peer this has never appeared. Everything looks good environment-wise as far as I can tell. One thing I noticed in the logs is that on startup the docker appears to be checking for a new version of syncthing at the following URL, which returns a 404 error: http://apt.syncthing.net syncthing/release Has this URL changed recently? Is this something that should be updated? Has anyone else successfully upgraded their Linuxserver.io based syncthing docker to v0.13.10? Thanks, -A

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.