danioj

No idea what happened. Had nothing to do with 6.9.2 as it was running fine after the upgrade. Plex just stopped responding and was dropping any connection being made to it. Nothing obvious in the Plex logs either. Life is too short to troubleshoot sometimes. I just deleted the whole thing, reinstalled, scanned the library again. All is up and working again. Easy. I seem to recall that sometimes Plex 'Databases'? can get corrupt? Who knows. Anyway, all is well again and family have their tv.

Evening all, Not sure if this issue is localised to me but this evening Plex became suddenly unresponsive. No changes or amendments. Im on unRAID OS 6.9.2. Version tag set to latest. Normal practice for me is to restart the container. Safari now complains that the connection to the server was "dropped". I get this in the log: ------------------------------------- _ () | | ___ _ __ | | / __| | | / \ | | \__ \ | | | () | |_| |___/ |_| \__/ Brought to you by linuxserver.io ------------------------------------- To support LSIO projects visit: https://www.linuxserver.io/donate/ ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 40-chown-files: executing... [cont-init.d] 40-chown-files: exited 0. [cont-init.d] 45-plex-claim: executing... [cont-init.d] 45-plex-claim: exited 0. [cont-init.d] 50-gid-video: executing... [cont-init.d] 50-gid-video: exited 0. [cont-init.d] 60-plex-update: executing... Atempting to upgrade to: wget: unable to resolve host address ‘downloads.plex.tv’ ######################################################## # Upgrade attempt failed, this could be because either # # plex update site is down, local network issues, or # # you were trying to get a version that simply doesn't # # exist, check over the VERSION variable thoroughly & # # correct it or try again later. # ######################################################## [cont-init.d] 60-plex-update: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Starting Plex Media Server. Trying to access downloads.plex.tv takes me to a redirect to: https://www.plex.tv/media-server-downloads/ Plex' uptime page shows that all services are running. Not sure how to troubleshoot this one? Is anyone else having issues? D

@comet424 here is my2c. Home assistant is in its purest sense is Home Assistant Core. This can typically be installed on any Linux OS (although the HA devs would love to stop supporting that method of installation AFAIK) but it seems to me that the most suggested installation is via Docker. Hass.io is an OS that comes pre packed with Home Assistant Core AND with Docker running as well as a Docker “Assistant” that can be accessed within Home Assistant Core to manage the containers. This allows you to install “Addons” like MQTT etc but in essence as it is a Docker implementation you can pretty much install any Docker on it, and people do. This is way Hass.io either is run on a machine (like a Pi or NUC) or a VM in unRAID. Most people who use unRAID that I know of, myself included, see running a VM, which has an OS and ANOTHER version of Docker (however simple it might be to use that Docker version via the Hass.io assistant) as an unneeded extra layer of virtualisation. Therefore I install my HA related Docker Containers (Hass.io Add-Ons) on unRAID directly and point Home Assistant at them. Yes, I don’t have the fancy Hass.io supervisor but I like the control and don’t mind the extra layer of “complexity” of doing so. By also running on unRAID I can have all the network goodies (like running a Docker container on its own IP etc). There is an argument to suggest that running Hass.io in a VM keeps the whole thing contained and all you have to do to keep your automation hub safe is back up the VM file but I back up everything anyway. Hope this helps.

https://youtu.be/qnEuHKdf7N0

I’d love the ability to assign multiple networks to a single Docker container. The simplest use case involves pihole. Currently I run seperate instances of a pihole container for each of my VLANS. It would be great if I could just attach one container to each network and configure pihole to listen on all assigned interfaces. I’m pretty sure you can do it via the cli using ‘docker network connect <network> <container>‘ or something but it would be excellent to be able to do it in the GUI.

Watching the thread via email updates and had to chime in. I like this one, good job!!

I currently have all my networks restricted to using pihole which is set to use unbound (locally hosted in pfsense) to resolve dns queries (where the request isn’t cached). I do not use any external dns service. What benefit would introducing this software into my setup give me?

As someone who uses VLANS in my setup I’d love the ability to choose which interface the management access features of unRAID (e.g. GUI / SSH etc is bound to). Select either / All etc. I’d like to have unRAID deployed to my management VLAN along with my other network gear and my main VLAN where all my file access occurs. I can do this of course but I’d like to be able to prevent clients on the main VLAN from accessing the GUI and SSH etc (not possible of course via FW rules as the traffic on that VLAN doesn’t go back to the router to trigger a block rule) and just have file sharing enabled. Right now I can deploy unRAID to X VLANS and on each IP (required to be assigned for file sharing) the GUI / SSH is accessible.

Without some specific errors I’m not sure I can help. When I was running Core in Docker in unRAID mine never dropped off or stopped working. I had morning, daytime, evening and night automations and all worked every day. I did have an issue with some of my TP-Link switches - configured so HA saw them as lights not “reconnecting” each day. This was because I had my dockers set to be backed up at 3am each morning and there is a bug in the TP-Link FW when you have them running local instead of via the cloud. Other than that (which really had nothing to do with HA) my setup was solid. Sent from my iPhone using Tapatalk

Yes, I did (until recently) and it worked flawlessly for months. When you say unstable, what do you mean? Now I run it in a VM on a dedicated NUC running Ubuntu. Taking the server down for maintenance, tweaking or WhateverTF was not very wife or family proof. One machine to do it all doesn’t really work for me these days. Sent from my iPhone using Tapatalk

Hi Mate, The script I wrote ended up being more of a Proof of Concept that, while a good foundation, was something I didn’t have the time to take forward into something more functional and stable. It appears that it has been taken over by the community (got to love open source code) and has since morphed into a vastly more functional plugin that I am happy to have inspired but can neither take credit for nor know much about. I think the name of the unRAID community member now maintaining the resulting plugin is called Jtok. See above posts. I’d suggest searching for this plugin in Community Applications (from which there will no doubt be a support thread linked where you can ask functional questions) and start there. Ta Daniel Sent from my iPhone using Tapatalk

No issue with v5.0 for me. The upgrade happened at some point over the last week and didn’t notice. Logs are clean of errors and all my settings are intact.

I don’t know about the specifics of your 2 guys’ setup but I have 2 DNS servers (Googles) in both my unraid config and also in Pihole. Then I have all my network pointing to pihole at the direction of my DHCP server which is my router (which also forces all DNS queries through pihole Even if the client specifies it’s own). I also think it’s best to run the docker with it’s own IP so you can point clients at it. Not sure about any other config. As for the interface not coming up, I’d imagine this is because there is something wrong with the config preventing the application from starting. Then again, if that was the case, not sure the IP would be pingable as the docker wouldn’t start. What does the log say?

Sure, but there is nothing novel I have done to expand on. I followed the @SpaceInvaderOne guides (noting what I have posted above) almost to the letter for a setup with my own domain name and using Cloudflare dns. The only issue I had is when I used the Cloudflare proxy service - which I ended up turning off - but that had nothing to do with Pihole. I also used LAN IP addresses in my config rather than local dns (e.g. x.x.x.x rather than mariadb.local.tld) so that resolution was not required. Router provides DHCP and reserves IP addys. I assume you had Nextcloud working perfectly using the Letsencrypt docker before you installed Pihole?

Ah, bugger. Still, Id love a button on there which would allow me to raise it with one click no matter where I am in the GUI rather than having to click through the menus. Saying that, not exactly a big issue.

Hey @dlandon I hope you're well. Not surprised that this thread isn't the most active as it is a rock solid piece of work and (barring only CA - which makes installing this very easy) is pretty much the first plugin I think someone should install. Following that same train of thought.... would it be a difficult enhancement to the plugin to allow the option to replace the current syslog link with the enhanced syslog view? Much like what is done with the terminal link and the command line plugin by @dmacias??

For those, like me, who run Asuswrt-Merlin, I found (and successfully followed) this guide from a Reddit user to setup Pihole on your network utilising this specific FW's function called "DNSFilter". Paraphrased from a section of the post: It will force all LAN DNS requests back to the router's settings in LAN, with your Pi-hole (and unRAID in my case so as to not prevent unRAID making a successful DNS request before the container starts) as a no-filtering exception meaning any device on your network, whether it is trying to use its own DNS or not, will be forced upstream to your Pi-hole because of the DNSFilter rule.

This is what I did. I am sure there is a better way but these are the steps I took. - Removed the current App (and image) from within the docker tab (this doesn't touch the folder with all the current app settings in the appdata folder). - Installed the new App from within the Apps tab (CA) with the same network and path settings as the old App. - Stopped the new App in the docker tab. - Deleted all config files within the new folder created in appdata for the new App (no need to backup as they are fresh and can be pulled anytime). - Copied all files from the old appdata folder to the new one. - Started the App within the docker tab. - Once confirmed that the App is working, deleted the old appdata folder. All working fine.

Just had a notice that there was a new version of Nextcloud v 18.0.4. Successfully upgraded utilising the Nextcloud web gui updater. Had one hitch that I thought I would share. The upgrade steps check that the right files are in the appropriate dir before upgrading and won't proceed if there are unexpected files found. Fine for most right? OSX: Hold my beer!! As I had previously browsed those folders, you guessed it, .DS_Store files were present and this stopped the updater from proceeding. In fact the exact error was: "Check for expected files // The following extra files have been found // .DS_Store" You cant set Nextcloud to ignore these files so i had to manually get rid of them. Didn't want to mess around with finder and turning on show hidden files, so did this: root@unraid:~# cd /mnt/user/appdata/nextcloud/ root@unraid:/mnt/user/appdata/nextcloud# find -name ".DS*" ./www/.DS_Store root@unraid:/mnt/user/appdata/nextcloud# cd www/ root@unraid:/mnt/user/appdata/nextcloud/www# rm .DS_Store root@unraid:/mnt/user/appdata/nextcloud/www# I was able to click try again in the Nextcloud updater web gui and now he file had gone, it proceeded on and completed without an issue.

What would be the easiest way to migrate to the new image without losing any settings or data. Is it as simple as deleting the image and renaming the app data folder to match the new name and then installing the app again?

What an excellent little app. Time was well invested in setting things up inside the app once installed. Have a newly pregnant partner here who is relishing being able to transparently build the shopping list for me to fulfil (as this is my job while COVID-19 is here) without the usual txts etc. Sigh. LOL! Anyway, thanks for making this into a docker boys. Special thanks for also including a default proxy.conf file in the letsencrypt docker too. Made setting it up for external access via https a doddle.

Just out of curiosity, what advancement do you think unRAID could make that would impact the ability for SaBNZBD to send you a notification email? unRAID has the ability to input email smtp details for notifications and it works just fine. As I understand it (and I acknowledge that I have not set this up or tested it) SAB all has the ability to do this to? I have many containers setup to send emails so if SAB doesn't do it I would have thought that is with the developer of SAB and not unRAID to fix.

I am not sure on your setup BUT I have pihole setup with the default blocklists as well as a great deal more. I have just tried to update a plugin and it worked fine. If you have setup pihole with its own IP AND you don't have the advanced docker option checked which allows for the "Host to communicate with custom networks" then I am going to guess that your issue relates to your unRAID server not being able to use pihole as a DNS server and therefore resolve the address that is used for updates. Assuming I am right, you should add DNS servers - say Googles (1.1.1.1 and 1.0.0.1) - to your network config, meaning independent to your pihole setup, unRAID can always resolve addresses it needs to resolve whether the container is started or not. To me that is a no brainer as there is nothing unRAID does you would wan to block. In fact, you should do this anyway otherwise when you go to restart unRAID (when the container is not started) then it is not going to be able to do its network call home thing that it does (assuming it still does that) meaning you might not even be able to start the server.

Another guide followed and another successful and easy installation. Thanks to @SpaceInvaderOne and @spants for helping to make that happen. I did do a few extra things which made the setup a bit more seamless: - Decided to set static DNS entries for unRAID to Google DNS to avoid issues with boot up and the unRAID call home "feature" (this works great for my setup as most of my dockers have their own IP and therefore get their DNS set automatically by the router (which is Pihole) - the only exceptions to that are the services which run on either host, proxynet, or br0 - which are few. - Set unRAID to have a static IP as apposed to DHCP reserved to try and prepare to avoid any future DHCP / DNS complications. - Set 'Use Conditional Forwarding' in the Advanced DNS settings of Pihole to my router as my router is still the DHCP server and also stores the local domain, reserved ip assignments and hostname settings. Works great - all my LAN hosts still resolve. - Updated the blocklist with everything here (https://firebog.net) with a "tick" so as to not interrupt the browsing experience as well as updating the whitelist with the suggestions at that link too. What a great piece of software. P.S. I did find that I had to change my nextcloud settings (and will have to with any other services which run on unRAID that don't have their own IP) of my mariadb hostname to the IP address of the docker as unRAID was no longer getting its dns from the router and couldn't resolve the local dns hostname.