Newbie - can't setup on Mac

Help Community Help
1

Please follow the below template, it will help us to help you!

Expected Behaviour:

I was able to get Pi-hole up and running on my Mac with the latest version of Docker using a script from ChatGPT

Actual Behaviour:

I accidentally deleted that container and I can't get it up and running again I can get into the localhost dashboard but it seems there is an issue with the ports or the DNS I really do not know - and ChatGPT just goes around in circles. I guess I am looking for the easiest way to scratch everything and start fresh with a simple terminal script or something like that. Thanks in advance!

Debug Token:

Replace this text with the debug token provided from running pihole -d

3

What a surprise, ChatGPT had you, or itself going in circles. Anyhow.

Have a look here https://pi-hole.net/. Notice that pretty much at the top of the page is a button related to installing Pi-hole in Docker. Give that a go, thinking instead of crossing your fingers and relying on likely incorrect/useless information.

My assumption is that the Pi-hole folks have better things to do than baby sitting a mess create by “AI”. Yeah, you might be correct in thinking I am not a fan.

2 Likes
4

For sure I am definitely not proud of it but for some simple things its worked...

How do I install it from pi-hole.net? I have docker compose but I don't know how to use it :slight_smile:

5

See this section of our Github:

As the other commenter noted, ChatGPT is not your best resource. Always go to the source documents first.

7

Thanks again for the tips - lesson learned for sure.

I installed pi-hole from a .yml based on the one on Github that I was directed to by jfb (but cannot use @ to quote because I am a new user) to and I received the following error in terminal as well as when I tried to start pi-hole:

(HTTP code 500) server error - ports are not available: exposing port UDP 0.0.0.0:5353 -> 127.0.0.1:0: listen udp 0.0.0.0:5353: bind: address already in use

Again, I am using a Mac if that makes a difference.

Thanks in advance!

8

I looked in the log in docker for when it loads and I keep getting this:

fatal: unable to access 'https://github.com/pi-hole/pi-hole/': Could not resolve host: github.com
9

@jfb Last time through I didn't have any issues with the install or the startup but its still not showing me any activity.

10

and now I'm seeing this in the dashboard and in the logs:
dnsmasq warning:

ignoring query from non-local network 192.168.65.1

11

I think I have it up and running it boots up no problems and I can access the dashboard but no DNS setting that I have tried has been successful in any blocks or queries - I tried my computer, the router, 127.0.0.1 to no avail. What am I missing? I feel like we are so close.

12

Please upload a debug log and post just the token URL that is generated after the log is uploaded by running the following command from the Pi-hole host terminal:

pihole -d

or if you run your Pi-hole as a Docker container:

docker exec -it <pihole-container-name-or-id> pihole -d

where you substitute <pihole-container-name-or-id> as required.

13

https://tricorder.pi-hole.net/JXUvMLq5/

And thank you @rdwebdesign for showing me how to get that debug log as well!

14

Still nothing doing - once in a while when I reset it I will see one or two queries but then radio silence.

15

Looking back it seems that when it did work one time it had something to do with using dnsmasq but I do not remember how or what I did with that. does this help in solving the problem?

16

The general fault-finding approach is to set Pi-hole up and test it can resolve domains itself.

Then check from a client, which you believe should be using Pi-hole, that it is indeed using Pi-hole as standard. And also check that the client is able to use Pi-hole when you explicitly ask it to, and that Pi-hole returns the expected response and shows the Query.

Much of the time Pi-hole can be sitting there working perfectly, but the rest of the local network is not telling anything to use it, and so that becomes a separate networking problem and technically nothing to do with Pi-hole. Often that's caused by the DHCP server giving out multiple DNS servers for clients to use and they are able to work around it, hence that "check from a client" part above.

The previous debug log has expired (they are deleted after 48 hours), can you create a new one please and post the token URL.

17

Here is the latest debug log:

https://tricorder.pi-hole.net/sgt6hmfy/

18

Your debug log shows the container is running, but logs generated inside a container can't tell of it wrong on the host.

Please post here the compose file used to start your container.

Note:

Yes, it does.

Usually is a lot easier to run Pi-hole (or any other docker container) on a Linux machine.

Docker on Mac/Windows (actually "Docker Desktop") runs inside a special Virtual Machine and that VM runs inside your MacOS. This creates an extra network layer, making the settings a lot more complex. Also, some docker options only work on Linux.

19

Pretty sure I just used the one from GitHub with a few additional ports

20

You used the Pi-hole compose file, but I was explaining the difference between Linux and MacOS docker versions.

You asked:

And I explained there are a few differences between Linux (docker) and MacOS (Docker Desktop).

Running Pi-hole compose file in a Linux machine will be probably different than running the same compose file in a MacOS machine, specially the network configuration.

I'm not sure what the issue is, as far as I know, the IP 192.168.65.1 is the IP of the Docker Desktop VM.

I think you will need to wait for someone with Docker Desktop expertise to help you with the network settings.

21

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.