norp90

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

norp90's Achievements

Noob

Noob (1/14)

15

Reputation

  1. As of last night, on 6.10.3, fix common problems is alerting me that: The plugin ca.backup2.plg is not known to Community Applications and is possibly incompatible with your server. What's changed and what now?
  2. I am now having this same problem having upgraded to 6.10.2 "stable" from 6.9. Dell R710II. What's the fix? Edit: This seems to work for most people:
  3. +1 Same issue with these Plex and Swag files and mover saying No such file or directory, 6.9.2. What's the fix here?
  4. Could you setup your network so that one of the piholes is the DHCP server, have it set itself and teh 2nd as the DNS servers? Not perfect, if first fails network will still work but DHCP would be down.
  5. There might be something here: On your DHCP server, you could put the address of pihole 1 as DNS 1 and pihole 2 as DNS 2. The way DNS works on LAN, DNS 1 and DNS 2 are both active, your clients will use both of them at random in parallel, it's not the case that they use 1 and only 2 if 1 fails. So that would give you an active/active HA setup.
  6. Having issues getting latest release working? - If pihole running but status in UI/API is not shoiwn active, add env. variable 'DNSMASQ_USER' with value = 'root'. This should be fixed soon in a new release, they are working on it, so remove this variable again once new update released and see if it's no longer required. - Other issues? Do a review of all of your docker template env. variables vs. the current recommend and optional ones here https://github.com/pi-hole/docker-pi-hole. There have been a lot of changes recently that haven't been reflected in Unraid automatically. I suggest removing old ones no longer in use or only optional and see if that fixes issues, then add back any you know you need. The changes in the DNS ones to a single PIHOLE_DNS one was a big change recently to watch for.
  7. Hi all, This container stopped working/DNS on network not working as well as before lately? NOTE: There has been a recent change with PiHole's docker usage of ENV variable DNS1 and DNS2 that caused me issues. These two Docker env. variables now need to be replaced with a single env. variable called PIHOLE_DNS_ and the value of your external DNS servers input in the format e.g. 1.1.1.1;1.0.0.1. The container seems to fail to start or will start but only resolve IP's from cache if using the old DNS1 & DNS2 env variables still. Hope this helps someone else.