werfsd

Members
  • Posts

    8
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

werfsd's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Upgrade will not work with existing config folder. What I did was take a screen shot of all my settings, set up a new container from the app store with different name and config folder, and just went through the screen shots and copied all my settings across. Took less than 10 min. You will also need to import a new ovpn file.
  2. So I ran killall dnsmasq then was able to start Pihole just fine. Not sure if this will persist after a reboot, no idea if I have broken anything else but things seem to be working at the moment.
  3. Should dnsmasq be running by default on unraid? I think this may be the issue and am wondering if there will be any adverse affects if I remove it.
  4. No, I did run through all my dockers and did not see any conflicts, unless there are some settings I don't know about. My list of dockers just in case: - CouchPotato, DDClient, deluge, Dolphin, muximux, openvpn-as, plex, plexpy, sabnzbd, Sonarr. Try a reboot... worked for me when I was having a similar problem. Sent from my iPhone using Tapatalk Rebooted and disabled autostart of all dockers and VM's. Still no luck. Am I able to switch port 53 to 54 or will this break how pihole works?
  5. No, I did run through all my dockers and did not see any conflicts, unless there are some settings I don't know about. My list of dockers just in case: - CouchPotato, DDClient, deluge, Dolphin, muximux, openvpn-as, plex, plexpy, sabnzbd, Sonarr.
  6. I have also run into the port 53 issue: docker: Error response from daemon: failed to create endpoint pihole on network bridge: Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use. If I run 'lsof -Pni | grep 53' the only thing that comes up with port 53 is: dnsmasq 15316 nobody 5u IPv4 26575 0t0 UDP 192.168.122.1:53 dnsmasq 15316 nobody 6u IPv4 26576 0t0 TCP 192.168.122.1:53 (LISTEN) Any ideas how to fix this one?