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.

darth_platypus

Members
  • Joined

  • Last visited

Everything posted by darth_platypus

  1. I'm new to this plugin, but I've got a MSI PRO Z690-A DDR4 motherboard on Unraid 7.3.1, with the Nuvoton NCT6687 Driver. The plugin keeps "forgetting" my PWM assignments. I was manually correcting that but then I noticed it was just creating duplicate profiles in the config file, so I had to clean those up by hand. Even though the plugin is set to sync every 2 minutes, there are no sync updates going to the log file, and the fans just stick at whatever % speed they were at the last time I ran a manual sync. I guess for now this is tolerable, as they are stuck at 100%. Sounds like the plugin is not actively maintained at the moment. Bummer.
  2. Just wanted to add a data point to this discussion. I have Time Machine working in Catalina, backing up to the current version of UnRAID. I don't remember doing anything outside the norm to get it working, but if someone needs me to check a setting, just mention me here and I'd be happy to. I used SpaceInvaderOne's guide, primarily.
  3. You sir, win a prize. I had the exact same situation. 😂 I never would have realized it was the honeypot on the UDM if you hadn't figured that out. Thank you @rickydg! I can access the web admin interface now.
  4. Thanks for sharing a solution that worked for you. I already had bridging enabled and could already see Custom: br0 in the template, so I skipped everything except "Host Access to Custom Networks", which I enabled. Still seem to have the same problems, though. Can't reach the admin interface.
  5. Here's a quick peek at my settings. https://www.dropbox.com/s/1q2xt9ge93mnvt2/PiHole Settings.pdf?dl=0 Here's my log file. [s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] 01-resolver-resolv: applying... [fix-attrs.d] 01-resolver-resolv: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 20-start.sh: executing... ::: Starting docker specific checks & setup for docker pihole/pihole WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11) nameserver 127.0.0.11 options ndots:0 [i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u7 [i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! chown: cannot access '': No such file or directory chmod: cannot access '': No such file or directory chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory ::: Pre existing WEBPASSWORD found Docker DNS variables not used Existing DNS servers used (8.8.8.8 & 8.8.4.4) DNSMasq binding to custom interface: br0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "192.168.1.2", "VIRTUAL_HOST" => "192.168.1.2", Using IPv4 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Docker start setup complete ::: Starting docker specific checks & setup for docker pihole/pihole WARNING Misconfigured DNS in /etc/resolv.conf: Two DNS servers are recommended, 127.0.0.1 and any backup server WARNING Misconfigured DNS in /etc/resolv.conf: Primary DNS should be 127.0.0.1 (found 127.0.0.11) nameserver 127.0.0.11 options ndots:0 [i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u7 [i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! chown: cannot access '': No such file or directory chmod: cannot access '': No such file or directory chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory ::: Pre existing WEBPASSWORD found Docker DNS variables not used Existing DNS servers used (8.8.8.8 & 8.8.4.4) DNSMasq binding to custom interface: br0 Added ENV to php: "PHP_ERROR_LOG" => "/var/log/lighttpd/error.log", "ServerIP" => "192.168.1.2", "VIRTUAL_HOST" => "192.168.1.2", Using IPv4 ::: Preexisting ad list /etc/pihole/adlists.list detected ((exiting setup_blocklists early)) https://raw.githubusercontent.com/StevenBlack/hosts/master/hosts https://mirror1.malwaredomains.com/files/justdomains https://s3.amazonaws.com/lists.disconnect.me/simple_tracking.txt https://s3.amazonaws.com/lists.disconnect.me/simple_ad.txt ::: Testing pihole-FTL DNS: FTL started! ::: Testing lighttpd config: Syntax OK ::: All config checks passed, cleared for startup ... ::: Docker start setup complete [✗] DNS resolution is currently unavailable
  6. I have the same issue. Been fussing with it all week trying to get it to work, to no avail. 🧐 Can't get the web admin interface to come up at all. The custom IP I made for the docker is active/pingable but doesn't seem to be listening on port 80, for web connections. Go figure. 🤷🏻‍♂️

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.