Jump to content

westsola

Members
  • Posts

    9
  • Joined

  • Last visited

Posts posted by westsola

  1. Thanks OP for creating this. I just installed it to test it.. and encountered a couple of error messages. Hopefully they are helpful for your troubleshooting. 

    Upon initial login/setup of user account, I receive the following error when trying to start a scan.
    image.png.be8b0c3bbf37cda63b8c20f25c3efedb.png

    Then upon logging in again I get this error

    image.png.d3fe691e8633f75f201c8ffe37728089.png

  2. I hadn't seen this project before but after finding it in the community apps store, I wanted to try it out. Depolying the docker took no time at all - I've got a few documents uploaded now and like this a lot - much more easy to organize than documents in Google Drive for example. The OCR and tagging is awesome. I'm now considering purchasing a used scanner with the scan to ftp feature..  

    Thank you T0a!!

  3. On 5/16/2018 at 12:28 PM, bonienl said:

    Internally pi-hole only knows interface "eth0".

    image.png.ba7c6d102a5c06f40aa8097965dc6f3c.png

     

    Update the corresponding template setting.

    image.png.6e04795a2abcbf7d90e09a24736a2176.png

     

    And pi-hole itself

    image.png.4aa41d63d1871ecdc463f73a0ba4d47d.png


    Thank you for the reply. I changed my interface variable to eth0. I'm wondering if I need to change the 'Network Type' from Custom Network- br0? Options area Bridge, Host, or None.. If I leave it as Custom Network -br0, I can set the ip address. Should I leave this as is?

  4. Ah, I was following the spaceinvaderone tutorial where iirc the variable INTERFACE as br0. Maybe that's where my trouble began. It's working for now.. so I'm tempted to leave it. Though I'm planning to take my 4 NICs out of bonded mode soon and just use eth0.. going to try pfsense or sophos on eth3/4. 

  5. 6 hours ago, spants said:

     

    Have you set DNS1 and DNS2 variable to point to 8.8.8.8 or 1.1.1.1 ? If pihole doesnt need to block it, uses DNS1 and DNS2 to do the look up.

    Try posting a screenshot of your settings if not. 

    Yep, am using 9.9.9.9 and 8.8.8.8. 

    It looks like I fixed my issue. I went to grab a screenshot of my settings and found the below setting. My pihole wasn't working at all. Running on a Dell R710 with a bonded and bridged interface. I had to change it from Listen only on interface br0 to Listen on all interfaces. Works great now. Hope this helps someone else. 

    Interface listening behavior

    Listen on all interfaces 
    Allows only queries from devices that are at most one hop away (local devices)
    Listen only on interface br0
    Listen on all interfaces, permit all origins

    Thanks spants!
  6. On 5/10/2018 at 5:49 AM, nuhll said:

    From my point, if query[a] is shown, its working.

     

    Its just not updating GUI (but i might bewrong)


    I also have this br0 "error" in log...


    After further testing.. my pihole doesn't appear to be working at all. Which additional logs should I provide? This is a brand new install following the spaceinvaderone video, same settings. 

  7. 20 hours ago, nuhll said:

    I use this docker since some weeks/months. No problems so far.

     

    But since some days i noticed that if i login to the admin, it doesnt show any information.. 

     

    Hows that possible? Seems to work just fine?

     

    Ive read somewhere that it might be that the logs are full, but where are they? If i "console" into pi hole, i cant "move" into directorys or use vim or tail or anything.

     

    Incase anyoen wonders, b efore pi hole i have another dns cache (for serving windows updates/steam and so on)

     

    Is the block list too big?

    1.jpg

    2.jpg


    I believe that I'm having the same problem. I was recently ready to burn my new unraid install because I couldn't figure this out. I previously had the stats updating but pihole itself wasn't able to update the blocklists. I deleted the docker and recreated it, now everything seems to work.. I.e. ads are being blocked, but the query #s aren't updating. i thought it was broken until I saw your post and decided to double check. At first I thought I was having network issues.. 

    dnsmasq: warning: interface br0 does not currently exist

    ^^ Is this a problem? I'm pretty sure br0 does exist.. it's in my routing table in unraid.. Maybe the docker doesn't see it as br0?


    dnsmasq: 26 127.0.0.1/51118 query[A] pi.hole from 127.0.0.1
    dnsmasq: 26 127.0.0.1/51118 /etc/pihole/local.list pi.hole is 192.168.1.2

×
×
  • Create New...