Gokux

Members
  • Posts

    11
  • Joined

  • Last visited

Posts posted by Gokux

  1. On 12/18/2021 at 12:48 PM, spants said:

    The template just uses the official PiHole docker - it seems that there is a discussion here that may help https://github.com/pi-hole/docker-pi-hole/issues/922 .

     

    Yes, I found that too. I have also adapted the template accordingly with the new "FTLCONF_ " variables. They also work, but in the end it had no effect on the crash problem.

     

    On 12/18/2021 at 12:48 PM, spants said:

    You could also change the docker tag to load a specific version: see here https://hub.docker.com/r/pihole/pihole/tags

     

    I didn't want to downgrade yet. But it might help; this Docker ran for years without any problems.

    Let's see what else I can find this weekend :)

  2. On 12/15/2021 at 8:20 PM, zaker said:

    I'm seeing that the most recent upgrade sends my docker image into a continual fail and reboot cycle:

     

    I can confirm that. After starting, the container runs for a few hours and then suddenly hangs in the reboot cycle.
    Funnily enough, if it was switched off for a few hours, I can start it again, but then it only runs again for a few hours.

  3. 1 hour ago, limetech said:

    Saw that earlier, last change was almost 3 years ago, also no license specified, which might be problematic for us.

    It is LGPL 2.1

    Quote

    numad is free software; you can redistribute it and/or modify it under the

    terms of the GNU Lesser General Public License as published by the Free

    Software Foundation; version 2.1.

     

  4. I believe so. Basically, every user's connection is proxied through the letsencrypt container and so emby thinks that all the requests are coming from that container. And the container ip is that 172.x.x.x one.
    I was a little bit surprised, because on Apache virtual hosts, it was never a "problem".

     

    If it's an issue you'd like to fix, there may be a way to do it through the options in proxy.conf but I don't know which. You'd have to search online.

    I have searched around and found this. So I took just the first part in my site-confs

     

    [...]
    location / {
        	proxy_pass https://192.168.0.100:8920/;
        	proxy_set_header  Host $host;
    proxy_set_header  X-Real-IP $remote_addr;
    proxy_set_header  X-Forwarded-For $remote_addr;
    }
    [...]
    

     

    and it seems to work. ;D

  5. I know they're supposed to => but click on Spin Down and then check the power -- just in case there's an issue with the timed spindowns.
    I clicked it, but it makes no difference.

    After a while it is now more between 32-48 watts (~40 watts). I disabled also my Dockers (Apache and Emby), but that makes no difference.

    Maybe I should just make a reboot?

  6. It sounds like you have some disks spinning that weren't spinning before.  Click on "Spin Down" and then see what the power consumption looks like.
    My disks spin automatically down after 15 minutes. So they mostly greyed. Only Cache (SSD) is always on.

     

    Also, do you have any disks in the system that aren't assigned to UnRAID ??
    Nope, all in the array :).