hi2hello

Thank you very much! I wrote to privacy@… No answer so far, that is why I was asking for options. I tried your proposal and have two questions: 1. Should there be a response? Probably not on i curl command, right? 2. Related to the domains. Just the domain-name without TLD, right? Anyway, thanks again for your kind advice till now. I did not know how annoying it could get, to delete a duckdns entry. Edit: Seems your proposal did the trick. The URL is no longer reachable. Checking deposited IPs on the relevant addresses returned, that there is no longer any IP related to the URL. THANK YOU!

I would like to uninstall / get rid of duckdns completey but do fail. I deleted the container but as I do no longer have access to my account (although I have email and token, I get an login error that states "wrong email or token"; while I am able to use the exact same credentials for connectiong to duckdns over other ways than persona singin), the old address is still pointing to my server. Any idea, or contact address or any helpful hint on how I could get rid of the duckdns address pointing to my server? Thank you so much!

Nice tutorial though it seems I cannot get any certs from letsenrypt. Trying for a few hours now but I am stucked. Heres what the log says: Any suggestions?

Wow! That seems to be really bad news. I was assuming that any kind of data corruption would lead to an error notification by default. Would like to see that implemented as I think it is a must-have-feature.

The plugin works, till the next update of unraid … To me, this topic is all about a will for change or excuses for just keeping on. Matter of priority and state of mind.

I also would like to state that having a solid support for S3 sleep would be highly appreciated. Energy costs are still going through the roof, climate change is everywhere (over here, this year is, again, the hottest and driest since recording weather data - while our region is considered rather not to be affected by global warming) and my server is forced to run 24/7 just because there still is no official solution, even on the horizon (this topic yet alone was started one and a half years ago). Don’t get me wrong, I am aware of problems that might be caused by S3 but honestly, I just dont get into my head, that saving energy does still not seem to have the priority and awareness that it would need to actively change an irresponsible (and often quiet senseless) waste of ressources. Some day, our kids will ask us "why?" … In a nutshell: I would love to see unraid putting more effort in lowering energy consumption. I would like to see less discussion about the inevitable but more action. Thank you so much!

Still not 100% sure but I guess, I found the problem: seems that I "killed" the go-file (if so, than stupid me)

That is exactly what I initially did. I just deleted it because I managed to get back into the GUI with an quiet old backup of my stick. If you guys would like to know what happened (I would be very curious about it), here ist the diagnostics file again … Edit: Found solution. Deleted diagnostics

Ok, I managed to get back into the GUI. I was lucky and had an old backup of my stick from june. Copied the config to the stick and now have a connection to tha GUI again. Anyways: Very strange!

Hi there, I needed to restart my server running on latest 6.11.1 this morning. Unfortunately, I does not come back up again properly. The GUI is not showing up in the browser nor does any of the dockers start. I can connect to the server via SSH, while entering the IP-address in any browser (also with cache emptied) just brings up an error (page could not be loaded). (The server seems to reject requests to the IP-address. When it is shutdown, page loading takes a while before stating that the address is not reachable. Running the server, the message, that the page could not be loaded comes pretty much immediately). In the meantime I tried the following with no luck: deleted / deavtivated all plug-ins, reboot makes no difference booted into safemode GUI > firefox gives an error (localhost page not showing up) used USB flash creator from backup > no luck used fresh 6.11.1 image from usb flash creator and copied over config folder > no luck ckecked on network > nothing of special interest and no changes to the config that was always running smoothly Connecting a display to the server, it boots up and afterwards remains at the prompt command "LogIn" (which is supposed to be fine, I guess?) There are some minor error messages (such as the grep thingy from the webgui plugin), but to my knowledge, nothing special or a big deal (and as I stated, those errors go away when deactivating plugins folder, but webgui still does not come up). I have no idea what else to try. Maybe you guys have an idea. Please find diagnostics attached … Thank you in advance! Edit: diagnostics deleted

Done. After the disk preclear was finished, everything went just as intended. @JorgeB Thank you very much for your kind support and the helping hand! Very much appreciated!

Ok. Thanks for the info. One more question: Once the new disk is precleared, I assume that I can attach it to the array and it than will be marked "unformatted" after restarting the array? There would be a format command for the newly attached disk BUT, would this then automatically put xfs on it, or would I have a choice? In other words: I would like to use btrfs for the new disk and I am not sure on how to accomplish this (as i think that formatting the drive after attaching it to the array automatically will put xfs to it) I am aware, that there will be an option to format the precleard drive with unassigned devices, but I am not sure if the preclear infos will than be lost / wiped and I d had to start over again with preclearing / clearing. Thank your very much for your advice EDIT: I think I found it. Under Settings > Disk Settings > Standard Data Filesystem I assume, changing this from xfs to btrfs would than automatically format a new disk with btrfs? Can you confirm this?

Ok, so I am rebuilding parity now and as this takes about 1,5 days (honestly not too happy about it, as I was already doing this a few days ago), I am also precelaring the new disk. Takes pretty much the same amount of time. Once this is all done, am I getting it right, that with the following procedure: - stop array - change slots to "5" - select the new hdd under data disk 4 it should than be possible, to restart the array and having an array of an overall 6 disks? Am I getting this correct? Thank you very much.

Please find the diagnostics attached. 2 questions: 1. I was rebuilding the array under Tools / New Config, so there is actually no valid parity. Do I need to rebuild parity before I can add another drive? 2. Does the new drive must be precelared before adding it to the array or is it enough to format it?

Hello, i wanted to add a new HDD to my server which would be device number 6 (1 Parity, 4 Data Drives, 1 Cache).Currently, there are 5 devices attached (1 Parity, 3 Data Drives, 1 Cache). As far as i know, 6 devices are supported by the Unraid OS Basic Licence that i own. Unfortunately, it just does not work to set up the new HDD as Data Drive #4. As soon as I stop the array, unraid lets me add a second parity, which is not what i want, as I d like to use the new disk as data disk. The possibility to add a 4th data-drive is just appearing, when i switch the number of slots from 5 to 6 down at the bottom of the array-rider. Than i can add the HDD as 4th device but I am getting an error that says "too many devices" (7 devices are shown, so it seems that Parity 2, which is not assigned and should not be, is also counted.) Any idea what I am doing wrong? Thanks for your kind help. Very much appreciated.

Thank you for your feedback, much appreciated. So i have set up everything as it should be (call it early-morning-intuition ). Also thank you for providing the docker. Really awesome! By the way: Do you know a way I could do something like a "trace route", including the ips of my internal network? I would really love to see whats going on when submitting a web request. (That is probably nothing about your container, just generally asking.) Hi5, hi2hello

Hi, i have setup your doh-client. Maybe its already too late over here but i have a question on setting things up with pihole. Right now, i have set the doh-client docker to br0 with ip xxx.xxx.xx.30, pi-hole docker container runs on br0 with ip xxx.xxx.xx.20. I have set the DNS1 and DNS 2 in pihole to the ip-address of the doh-client (…30). Is this correct? And what IP do i need on my Router? The IP of the doh-client or the IP of pi-hole? Thanks a lot in advance for clearing things up.

Hi there, whenever i had an external disk mounted to my unraid server (6.8.2 DVB edition) via unassigned devices (letest version and plus), i keep getting errors via mail that do look like this: subject: cron for user *** /sbin/fstrim -a -v | logger &> /dev/null fstrim: /mnt/disks/nameofthedisk: the discard operation is not supported fstrim: /mnt/disks/nameofthesecondpartitioniwouldguess: the discard operation is not supported Is there a way of getting rid of these messages / warnings? They seem to be sent from SSD trim scheduler, though I dont even get why that is the case. The connected disks were no SSDs but classic hard drives, they were also removed / unmounted correctly. Why trim? If i disable the trim scheduler, my SSDs will no longer get trimmed - seems no solution to me. If i leave it on, the messages will continuing bothering me. Only thing that helps so far is a server reboot. Is this a bug or a feature? Because no matter how, once I mount and unmount a disk with the UD plugin - result is some kind of a daily warning (because trim is scheduled daily). Honestly, not the end of the world but still quiet annoying. Would it be possible to "disconnect" the UD plugin from trim scheduler? Editing cron jobs? Any suggestions that might help (to stop the polution)? Thanks in advance!

Thank you @Tyler: Except for a different Docker Hub URL (i was using the diginc Docker, so the one you find in Community Applications - which was renamed), there is no real difference to my settings. And as no surprise, still I get the same errors from the Pi-Hole Docker Logs 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 stty: 'standard input': Inappropriate ioctl for device [i] Existing PHP installation detected : PHP version 7.0.33-0+deb9u1 [i] Installing configs from /etc/.pihole... [i] Existing dnsmasq.conf found... it is not a Pi-hole file, leaving alone! chown: cannot access '/etc/pihole/dhcp.leases': No such file or directory You dont get these errors?

You are right, with docker set to host, nameserver is set as intended. BUT than i get the following error message: dnsmasq: failed to create listening socket for port 53: Address already in use and the docker terminates itself. Furthermore, within the install process, there is a warning WARNING: Localhost DNS setting (--dns=127.0.0.1) may fail in containers. and it obviously really does fail. I dont know how to implement a stronger argument in the unRaid Docker settings such as mentioned earlier $ echo -e "nameserver 127.0.0.1\nnameserver 1.1.1.1" > overwrite_resolv.conf $ docker run -it -v $(pwd)/overwrite_resolv.conf:/etc/resolv.conf debian cat /etc/resolv.conf Please, could anyone help out with working settings for an unRaid Docker? Right now, this is just not running properly and for sure no longer as shown in the video in the very first post of this thread. Thanks so much!

I would guess so to, but does that imply, that I’d have to change or overwrite my resolv.conf everytime manually? So far that did not work with nano, neither did the docker write the mandatory IPs into the resolv.conf. The entries are not 127.0.0.1 and 1.1.1.1 as they are supposed to. So is there a way in UnRaid to have a docker that is doing required steps on startup without the need for manual changes? Besides the nameserver issue I also get some other messages, that do not seem to be correct, such as "inappropriate ioctl", "dnsmasq.conf is not a Pi-hole file" and a chown error. Please see the attached log file … I am just using the current docker template where I did not changes except IP. Would be awesome if somebody could explain what kind of additions or changes would be needed to fix my pi-hole. Please see the attached screenshot of my docker.conf settings Thanks a lot! log.txt

Hi there, since the last update of the pihole-docker I am kind of insecure concerning a few things. I am also not quiet sure if everything runs as intended. Because I was not really confident about the recent template changes, I reinstalled the docker with the new template (including extra parameters containing --cap-add=NET_ADMIN --dns 127.0.0.1 --dns 1.1.1.1 --restart=unless-stopped) Pihole has a static IP, I can login, seems to run but still i get some weird infos from the logs that I cant asses. Could somebody maybe have a look and explain, how I could get rid of the messages / errors and how to get DNS resolution running? From the logs (just a few snippets that matter): Pi-hole blocking is enabled DNS resolution is currently unavailable DNS service is running Stopping pihole-FTL Starting pihole-FTL (no-daemon) Stopping pihole-FTL Starting pihole-FTL (no-daemon) 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 My questions: - concerning docker config: As DNS is already set in extra parameters, what should be entered in the docker config under Key 5 (Container Variable: DNS 1) and Key 6 (Container Variable: DNS 2)? Right now, there is 127.0.0.1 for DNS 1 and 1.1.1.1 for DNS 2, so basically the same as in extra parameters. Is that right? - concerning nameserver: although there is 127.0.0.1 setup in the config, the logs spit out 127.0.0.11. Does that matter? AFAIK it is the docker localhost. Modifying /etc/resolv.conf does not help or change anything. Any suggestions? - concerning pihole-docker itself: As soon as i am restarting the docker, the service does no longer start but loops between quits and restart trials (extra parameter: --restart=unless-stopped). Starting the docker from the docker-config (click into name for docker-config, change and rechange a parameter, click apply) on the other hand, succeeds and runs the docker without any certain errors. Weird??? Is that a bug or am I missing something? Thanks for your help

No, I didn t even know that something like this exists. I ve also been adviced to try something pretty close to your suggestion --restart unless-stopped I entered this into extra parameters and hope it will work. Thank you for your kind reply - much appreciated!

Hi there, although this is all based on the fact that Emby currently shuts down several times a day, my question is more of a general matter as it could work for all kind of services running on unRAID … Does anyone know if there is a plugin, Docker-Container … similar to a Watchdog? Something that could watch for services and in case of a crash, shutdown etc. than would be able to restart this service, plug-in, Docker-Container automatically? Thanks for any hints on that matter, hi2hello PS: Happy Easter

You re propably right. readme might be indeed a good idea. Cheers and thanks again for your work and the container. Really much appreciated!